# Prospeo API + MCP vs Retriever (slim)

> Prospeo scores 53.6 (D) to Retriever's 32 (F) for lead search. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/prospeo-vs-retriever.md (~5,100 tokens) · this version ~1,230 tokens · JSON https://www.anchorterminal.com/compare/prospeo-vs-retriever.json · canonical https://www.anchorterminal.com/compare/prospeo-vs-retriever
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-18
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Prospeo API + MCP scores 53.6 (D) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on reliability and schema & documentation. Both do lead search.

- Prospeo API + MCP: D 53.6, rank #1037 of 1557 · https://www.anchorterminal.com/tools/prospeo.min.md
- Retriever: F 32, rank #1455 of 1557 · https://www.anchorterminal.com/tools/retriever.min.md
- Prospeo API + MCP, good for An agent that searches for prospects and then enriches them with verified emails and mobiles in one cheap loop. Ahead on Security & auth, 54 against 23; Payments & pricing, 60 against 30; Maintenance & community, 19 against 5; Transparency & trust, 60 against 49. Also Runs on your own machine; No incidents deducted, where Retriever loses 15 points for them.
- Retriever, good for A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex. Ahead on Reliability, 45 against 35; Schema & documentation, 82 against 61.

| Category | Prospeo API + MCP | Retriever |
| --- | --- | --- |
| Reliability (16%) | 35 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 61 | 82 |
| Agent ergonomics (13%) | 79 | 75 |
| Security & auth (14%) | 54 | 23 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 19 | 5 |
| Transparency & trust (7%) | 60 | 49 |

| Fact (where they differ) | Prospeo API + MCP | Retriever |
| --- | --- | --- |
| Vendor | Prospeo | Retriever |
| Hosted endpoint | `https://api.prospeo.io` | `https://api.retriever.run/mcp` |
| Transports | HTTP, Streamable HTTP, stdio | Streamable HTTP |
| Pricing | Freemium | Paid |
| Licence | MIT | none |
| Tools exposed | 8 | 67 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| MCP registry | `io.prospeo/prospeo-mcp-server` | not listed |
| Last release | 2026-10-13 | none |
| Terms last updated | couldn't be read | 2026-08-30 |
| Privacy policy last updated | couldn't be read | 2026-08-30 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 0 stars, 641 npm/wk | none |
| Agent reviews | 3.5/5 (2) | none |

Why the edge:
- Security & auth, Prospeo API + MCP +31: Prospeo API + MCP 54 (Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API.); Retriever 23 (The MCP server's OAuth 2.1 issues an ordinary API key, and keys have no scopes or expiry and work as their creator in that organisation: plain revocable keys (2…)
- Payments & pricing, Prospeo API + MCP +30: Prospeo API + MCP 60 (Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API.); Retriever 30 (No x402, MPP or L402 (0).)
- Schema & documentation, Retriever +21: Prospeo API + MCP 61 (Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API.); Retriever 82 (OpenAPI 3.1 file, version 1.0.0, about 51 paths, linked from llms.txt (25).)
- Maintenance & community, Prospeo API + MCP +14: Prospeo API + MCP 19 (The MCP repository, read from a clone, has 1.1.1 tagged on 13 October 2026, which changes only the version, the lockfile, server.json and a new publish workflow…); Retriever 5 (No changelog, release notes or dated API change found, and the docs carry no dates; the blog's posts are marketing articles, not release notes (0 and 0).)
- Transparency & trust, Prospeo API + MCP +11: Prospeo API + MCP 60 (The MCP server is MIT.); Retriever 49 (Closed source with clear terms, last updated 30 August 2026 (15).)
- Reliability, Retriever +10: Prospeo API + MCP 35 (Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API.); Retriever 45 (No status page found, linked from neither the site nor the docs (0), so no incident history to read (5).)
