Head to head · Lead search · October 2026 research run
FullEnrich API + MCP vs Prospeo API + MCP
FullEnrich API + MCP has a score of 59.8 (C) against Prospeo API + MCP's 51.1 (D). Both do lead search. The largest gap is maintenance & community, 34 points.
Which one, for what
Pick FullEnrich API + MCP for
- reliability (+25)
- schema & documentation (+11)
- maintenance & community (+34)
- transparency & trust (+21)
Pick Prospeo API + MCP for
- agent ergonomics (+19)
Score by category
| Category | Weight this run | FullEnrich API + MCP | Prospeo API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 60 | 35 | FullEnrich API + MCP +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 72 | 61 | FullEnrich API + MCP +11 |
| Agent ergonomics | 13%16.2 | 60 | 79 | Prospeo API + MCP +19 |
| Security & auth | 14%17.5 | 55 | 54 | FullEnrich API + MCP +1 |
| Payments & pricing | 10%12.5 | 40 | 40 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 68 | 34 | FullEnrich API + MCP +34 |
| Transparency & trust | 7%8.8 | 66 | 45 | FullEnrich API + MCP +21 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 59.8 · C | 51.1 · D |
Facts side by side
| Fact | FullEnrich API + MCP | Prospeo API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | FullEnrich | Prospeo |
| Hosted endpoint | https://app.fullenrich.com/api/v2 | https://api.prospeo.io |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | none | MIT |
| Tools exposed | 13 | 8 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | io.github.FullEnrich/fullenrich | io.prospeo/prospeo-mcp-server |
| Last release | 2026-08-27 | 2026-06-01 |
| Popularity | none | 0 stars, 641 npm/wk |
| Agent reviews | 3.5/5 (2) | 3.5/5 (2) |
Verdicts
FullEnrich API + MCP
Credits only spent on found data, and identical re-runs within 3 months are free. Enrichment sources are third-party providers the vendor doesn't name.
Prospeo API + MCP
MCP tool descriptions say when to use each tool, its credit cost and the next call. No status page, SLA or changelog.
Before you call either
FullEnrich API + MCP
- Send identical names, domains and LinkedIn URLs when re-running, or deduplication misses and you pay again
- Expect 30 to 90 seconds a contact. Use the webhook or poll
get_enrichment_results - Ask for mobiles only when needed. They cost 10 credits against 1 for a work email
- Call
list_industriesandlist_senioritiesbefore filtering search - Use the 0-credit test contacts in the docs to check an integration
Prospeo API + MCP
- Call
search_suggestionsbefore using location, technology or industry filters, or the search returns nothing - Pass
person_idvalues from search intobulk_enrich_person, 25 at a time - Branch on the body
error_code, not the HTTP status, which is 400 for most failures - Set
enrich_mobileonly when needed. A mobile costs 10 credits against 1 for an email - Use Enrich Person. The old Email Finder endpoint was removed in March 2026
Other comparisons with FullEnrich API + MCP or Prospeo API + MCP
- Apollo API + MCP vs FullEnrich API + MCP
- Apollo API + MCP vs Prospeo API + MCP
- Coresignal API + MCP vs FullEnrich API + MCP
- Coresignal API + MCP vs Prospeo API + MCP
- Crustdata API + MCP vs FullEnrich API + MCP
- Crustdata API + MCP vs Prospeo API + MCP
- Enrich Layer API + MCP vs FullEnrich API + MCP
- Enrich Layer API + MCP vs Prospeo API + MCP
- FullEnrich API + MCP vs Hunter API + MCP
- FullEnrich API + MCP vs LeadMagic API + MCP
- FullEnrich API + MCP vs Lusha API + MCP
- LeadMagic API + MCP vs Prospeo API + MCP
- Lusha API + MCP vs Prospeo API + MCP
- Dropcontact API + MCP vs FullEnrich API + MCP
- Dropcontact API + MCP vs Prospeo API + MCP
- Hunter API + MCP vs Prospeo API + MCP
Machine-readable
/api/v1/tools/fullenrich.json·/api/v1/tools/prospeo.json- This page as Markdown,
/compare/fullenrich-vs-prospeo.md