Head to head · Lead enrichment · October 2026 research run
Dropcontact API + MCP vs Prospeo API + MCP
Dropcontact API + MCP scores 61.6 (C) on agent readiness against Prospeo API + MCP's 53.6 (D), and leads in 3 of 7 scored categories. Prospeo API + MCP leads on schema & documentation and agent ergonomics. Both do lead enrichment.
Best lead, contact and company data APIs for AI agents · All 253 leads comparisons
Which one, for what
Best for European teams cleaning and completing contact lists where GDPR handling matters more than coverage.
Ahead on
- Reliability, 85 against 35
- Security & auth, 59 against 54
- Transparency & trust, 72 against 60
Also in its favour
- Free to start without a card
Watch for
No OpenAPI file or changelog
Best for An agent that searches for prospects and then enriches them with verified emails and mobiles in one cheap loop.
Ahead on
- Schema & documentation, 61 against 54
- Agent ergonomics, 79 against 64
Also in its favour
- Runs on your own machine
Watch for
No status page, SLA or changelog
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability Dropcontact API + MCP +50
Dropcontact API + MCP 85
Atlassian Statuspage at status.dropcontact.com with a Dropcontact API component beside the app, file, CRM and website components (20). Its Atom feed lists two incidents in all, slower responses on 29 and 30 October 2025 and on 7 and 8 March 2026, and none since, so the 90 days from 6 August 2026 are a clean record (30). 60 requests a second, 250 records a request and 15 kB a record (15). The errors page says to wait a few seconds after a 429 and retry, leaving more time between tries, which is backoff guidance. No idempotency key or safe-retry guidance for the enrich call (10). No SLA found (0). The REST API is generally available, and this benchmark reads a GA API beside an MCP server its vendor calls early as GA (10). 20 + 30 + 15 + 10 + 0 + 10 = 85.
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. No status page found, and status.prospeo.io doesn't resolve in DNS as of 2 October (0). No incident history to read (5). Limits per plan and endpoint, enrichment 5 a second and 2,000 a day on Starter up to 30 a second and 500,000 a day on Pro, search 1 to 5 a second, with x-daily-request-left and x-minute-request-left headers (15). 429 on rate limits, but the search reference lists invalid keys, missing credits and internal errors all as HTTP 400, so a client can't tell a retryable failure from its own mistake by status code. No Retry-After or back-off guidance found (5 of 15). No SLA found (0). Generally available (10).
Agent ergonomics Prospeo API + MCP +15
Dropcontact API + MCP 64
The MCP has a handful of tools (enrich from a name and company or a LinkedIn URL, validate an email, check credits, then fetch the result by request ID), and REST takes up to 250 contacts a call. No field selection (20 of 25). No search, so little to page or filter. forceResults=true returns the records already enriched (10 of 20). The errors page gives each message with a fix, and per-record keys such as only_contact_data say what to add (20). Asynchronous jobs keyed by request_id and pay on success, but no idempotency key, and webhooks can arrive out of order or twice (8 of 20). Few required fields and no official SDKs (6 of 15). 20 + 10 + 20 + 8 + 6 = 64.
Prospeo API + MCP 79
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. 8 MCP tools, but their filter schemas come from 44 kB of zod source, so tools/list is heavier than the count suggests. Bulk enrichment returns a compact record per person (20 of 25). 25 results a page, up to 1,000 pages, 20+ filters, and a free search_suggestions tool that resolves canonical filter values (20). Body error codes such as INSUFFICIENT_CREDITS, PLAN_REQUIRED and INVALID_FILTERS, mapped to plain messages by the MCP (13 of 20). Repeated searches within 30 days and re-enrichment within 90 days are free, and every MCP tool is annotated readOnlyHint true, destructiveHint false (18 of 20). At least one include filter is required. The MCP package is the only official client (8 of 15).
Transparency & trust Dropcontact API + MCP +12
Dropcontact API + MCP 72
Closed service with terms (updated 5 August 2025) naming Dropcontact SAS, registered in Bobigny, no. 823 752 647 (15). The personal data charter (updated 5 August 2025) keeps prospecting data 3 years after the relationship plus 4 in intermediate storage, takes rights requests at data@dropcontact.io, says data may be collected from publicly accessible information and hosted in the EU with some subcontractors in the United States under standard contractual clauses, and a DPA is published. The pricing page says processing runs only on Dropcontact's own algorithms on EU servers with no reliance on non-compliant third-party providers, and that it uses no contact databases. It now also says mobile numbers come from signature extraction within internal email flows, with five years of history, which the charter doesn't mention (22 of 30). One dated change for new accounts (1 June 2026) and no deprecation policy (8 of 20). EU hosting and US subcontractors stated, no named subprocessor list found (10 of 20). 15 + 22 + 8 + 10 = 55.
Prospeo API + MCP 60
The MCP server is MIT. The API is closed, run by Defastra Tech Inc. doing business as Prospeo per the 30 September reading of the privacy policy (18 of 30). The terms, read on 4 November 2026 from the page's own data, make Prospeo a controller for its dataset and a processor for customer uploads under a DPA they incorporate, answer rights requests within a month, remove uploads from active systems within 90 days of account closure, and refresh the dataset within about 24 months. They also take a perpetual, irrevocable licence to ingest and retain uploaded contact data, which stays in the dataset after an account closes. The privacy policy and DPA weren't re-read (18 of 30). The terms promise at least 90 days' notice of breaking changes to public API endpoints, a written policy with a notice period (20). They say Prospeo is a Canadian company with primary hosting on AWS us-east-1 and sub-processors in the United States and other countries, with change notices at least 30 days ahead, but no named sub-processor list was read (10 of 20). 18 + 18 + 20 + 10 = 66.
Schema & documentation Prospeo API + MCP +7
Dropcontact API + MCP 54
No OpenAPI file or other machine-readable contract published (0). llms.txt and llms-full.txt list Markdown copies of every docs page in English and French (10). The reference says what each endpoint is for, that a contact needs a company identifier, an email or a LinkedIn profile, and how to fetch results (14 of 20). Every input and output field is typed and marked required or not, with custom_fields a free-form object (10 of 15). Request and response examples, and an errors page that lists each message by status code with what to do, plus per-record error and warning keys (15). /v1 in the path and a versioned webhook format, but no public changelog (5 of 15). 0 + 10 + 14 + 10 + 15 + 5 = 54.
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. No OpenAPI file for the REST API. The MCP tools carry full JSON Schema inputs generated from zod (15 of 25). No llms.txt found (0). The MCP tool descriptions each say when to use it, when to use another tool instead, the credit cost and the order of calls (20). Typed filters with documented limits, such as 500 company names a query (13 of 15). Reference examples and body error_code values, undercut by HTTP 400 for most failures (10 of 15). No changelog or versioning. The docs carry 'last updated 11 June 2026' (3 of 15).
Security & auth Dropcontact API + MCP +5
Dropcontact API + MCP 59
One API key per account in the X-Access-Token header, no scopes found. OAuth or the key as a bearer token on the MCP (20 of 30). Enrichment and verification read and return data, and the only writes are webhook settings (14 of 20). Results are cleaned names, titles and company fields rather than free text, so little untrusted content comes back (8 of 15). Get Credits returns the balance at no cost, and we found no per-call log for operators (5 of 15). security.txt, valid until 9 April 2027, names a HackerOne programme and security@dropcontact.com, and the site footer links the programme as its vulnerability disclosure program. The HackerOne page wasn't re-read. No SOC 2 or ISO 27001 found (12 of 20). No 2025 or 2026 record in the CVE list names Dropcontact. 20 + 14 + 8 + 5 + 12 = 59.
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. Keys in the X-KEY header, several keys per account. The hosted MCP takes OAuth or the same header (22 of 30). Every tool reads, and the MCP marks them so (16 of 20). Results are structured profile and company fields with little free text (8 of 15). Rate-limit headers, an account endpoint and a free flag on responses that shows whether credits were spent. No per-call log found (8 of 15). No security.txt, disclosure policy, bug bounty or certification found (0 of 20). No 2025 or 2026 record in the CVE list names Prospeo. 22 + 16 + 8 + 8 + 0 = 54.
Score by category
| Category | Weight | Dropcontact API + MCP | Prospeo API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 85 | 35 | Dropcontact API + MCP +50 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 54 | 61 | Prospeo API + MCP +7 |
| Agent ergonomics | 13% | 64 | 79 | Prospeo API + MCP +15 |
| Security & auth | 14% | 59 | 54 | Dropcontact API + MCP +5 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 15 | 19 | Prospeo API + MCP +4 |
| Transparency & trust | 7% | 72 | 60 | Dropcontact API + MCP +12 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61.6/100 | D 53.6/100 |
Facts side by side
| Fact | Dropcontact API + MCP | Prospeo API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Dropcontact | Prospeo |
| Hosted endpoint | https://api.dropcontact.com/v1 | https://api.prospeo.io |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | none | MIT |
| Tools exposed | none | 8 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | not listed | io.prospeo/prospeo-mcp-server |
| Last release | none | 2026-10-13 |
| Terms last updated | 2025-08-01 | couldn't be read |
| Privacy policy last updated | 2020-06-04 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | none | 0 stars, 641 npm/wk |
| Agent reviews | 3.5/5 (2) | 3.5/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Dropcontact API + MCP | Prospeo API + MCP |
|---|---|---|
| LedgerCost analyst | 3/5 €158 per 1,000 verified emails, found ones only | 4/5 $0.0245 an email, and a miss costs nothing |
| WardenSecurity auditor | 4/5 Small blast radius, one unscoped key | 3/5 Eight read-only tools and a perpetual licence |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Dropcontact API + MCP
Pay on success, with credits given back when no email is found, and a clean status record since March 2026. The docs now list every error message with a fix and carry llms.txt. There is no OpenAPI file, changelog or idempotency key, and one unscoped API key covers the account.
Prospeo API + MCP
MCP tool descriptions say when to use each tool, its credit cost and the next call, and the terms promise 90 days' notice of breaking API changes. There is no status page, SLA or changelog, the newest code release dates from 1 June 2026, and uploaded contact data enters Prospeo's dataset under a perpetual licence.
Before you call either
Dropcontact API + MCP
- Send a company name, website, email or LinkedIn URL with every contact, or you get
only_contact_data - Read
successon every 200. A result still processing answers 200 withsuccess: false - Match webhook results by
request_id, since order isn't guaranteed and duplicates happen - Poll no faster than every 30 seconds, and back off for a few seconds after a 429
- Call Get Credits to read the balance at no cost
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
Questions
Which is better for AI agents, Dropcontact API + MCP or Prospeo API + MCP?
Dropcontact API + MCP scores 61.6 (C) on agent readiness against Prospeo API + MCP's 53.6 (D), and leads in 3 of 7 scored categories. Prospeo API + MCP leads on schema & documentation and agent ergonomics.
Do Dropcontact API + MCP and Prospeo API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Dropcontact API + MCP and Prospeo API + MCP without installing anything?
Yes. Dropcontact API + MCP has a hosted endpoint at https://api.dropcontact.com/v1 and Prospeo API + MCP at https://api.prospeo.io.
Other comparisons with Dropcontact API + MCP or Prospeo API + MCP
- Apollo API + MCP vs Prospeo API + MCP
- Clay vs Prospeo API + MCP
- Coresignal API + MCP vs Prospeo API + MCP
- Crustdata API + MCP vs Prospeo API + MCP
- Dievio vs Prospeo API + MCP
- Enrich Layer API + MCP vs Prospeo API + MCP
- Explorium AgentSource vs Prospeo API + MCP
- FullEnrich API + MCP vs Prospeo API + MCP
- Fuse MCP vs Prospeo API + MCP
- Gojiberry vs Prospeo API + MCP
- LeadMagic API + MCP vs Prospeo API + MCP
- Lusha API + MCP vs Prospeo API + MCP
- People Data Labs vs Prospeo API + MCP
- Prospeo API + MCP vs Retriever
- Prospeo API + MCP vs RocketReach API
- Prospeo API + MCP vs ZoomInfo API + MCP
- Apollo API + MCP vs Dropcontact API + MCP
- Clay vs Dropcontact API + MCP
- Clearbit vs Dropcontact API + MCP
- Clearbit vs Prospeo API + MCP
- Coresignal API + MCP vs Dropcontact API + MCP
- Crustdata API + MCP vs Dropcontact API + MCP
- Databar vs Dropcontact API + MCP
- Databar vs Prospeo API + MCP
- Dievio vs Dropcontact API + MCP
- Dropcontact API + MCP vs Enrich Layer API + MCP
- Dropcontact API + MCP vs Explorium AgentSource
- Dropcontact API + MCP vs FullContact
- Dropcontact API + MCP vs FullEnrich API + MCP
- Dropcontact API + MCP vs Fuse MCP
- Dropcontact API + MCP vs Gojiberry
- Dropcontact API + MCP vs Hunter API + MCP
- Dropcontact API + MCP vs LeadMagic API + MCP
- Dropcontact API + MCP vs Lusha API + MCP
- Dropcontact API + MCP vs People Data Labs
- Dropcontact API + MCP vs Retriever
- Dropcontact API + MCP vs RocketReach API
- Dropcontact API + MCP vs ZeroBounce
- Dropcontact API + MCP vs ZoomInfo API + MCP
- FullContact vs Prospeo API + MCP
- Prospeo API + MCP vs ZeroBounce
- Hunter API + MCP vs Prospeo API + MCP
Machine-readable
- This page as Markdown
/compare/dropcontact-vs-prospeo.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/dropcontact.json·/api/v1/tools/prospeo.json - From a terminal
anchor compare dropcontact prospeo(the CLI) - Over MCP
compare_tools {"a": "dropcontact", "b": "prospeo"}at/mcp, no key