Head to head · Lead enrichment · October 2026 research run
Dropcontact API + MCP vs Hunter API + MCP
Dropcontact API + MCP and Hunter API + MCP score within a point of each other on agent readiness, 61.6 (C) and 60.9 (C). Hunter API + MCP leads on schema & documentation, maintenance & community and transparency & trust. 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 50
- Agent ergonomics, 64 against 54
- Security & auth, 59 against 43
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
No OpenAPI file or changelog
Best for Finding and verifying work emails from a domain or a name, where GDPR handling of the people looked up matters.
Ahead on
- Schema & documentation, 90 against 54
- Maintenance & community, 63 against 15
- Transparency & trust, 79 against 72
Watch for
Hosted MCP has about 100 tools, including bulk deletes and API key creation, with no read-only mode
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.
Maintenance & community Hunter API + MCP +48
Dropcontact API + MCP 15
No changelog. The newest dated API change found is the API_ERROR option, on by default for accounts created since 1 June 2026, which answers 400 when every record in a request has an error. That is between 90 and 180 days ago (10). The rebuilt docs carry no dated entries, so none fall in the 90 days from 6 August (0). Email support on every plan and no public changelog (5 of 15). No official SDKs and no registry entry we could read (0). No packages to judge (0, an in-between 3 with nothing behind it before). 10 + 0 + 5 + 0 + 0 = 15.
Hunter API + MCP 63
Newest changelog entries are three dated 30 September 2026 (the ChatGPT app, saved searches and AI tool setup paths), 35 days before 4 November. The official Claude Code plugin (hunter-io/claude-plugin) moved from 0.1.0 (18 March) to 0.1.1 on 28 October. The commit that bumps the version only adds an icon, but 0.1.1 is the first version to carry the skill changes made since 0.1.0, including domain-search on 17 August, build-sequences on 14 September and 16 October, and discover on 16 October, so it counts as a full release, 7 days before 4 November (30). Three changelog entries and the plugin release in the 90 days from 6 August (20). Public changelog and support. Issue handling not visible (10 of 15). Not in the official MCP registry. We didn't find current official SDKs; the plugin is MIT on GitHub (0). llms-full.txt tells agents to avoid a deprecated local package, whose repository was last changed on 7 July 2025 (3 of 10). 30 + 20 + 10 + 0 + 3 = 63.
Schema & documentation Hunter API + MCP +36
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.
Hunter API + MCP 90
OpenAPI 3.0.3 JSON at hunter.io/openapi.json, version 2.0.0, 101 paths and 182 operations on 4 November (25). llms.txt, llms-full.txt and agents.md written for agents (10). Reference pages state purpose and credit rules per endpoint, and llms-full.txt adds usage advice and a when-to-use line per MCP tool (15 of 20). Typed parameters with documented maxima (12 of 15). Examples, a test-api-key that returns dummy responses, and an error envelope {errors: [{id, code, details}]} including 451 for people who opted out (14 of 15). v2 API and a public dated changelog, with several newer endpoints labelled Beta (14 of 15). 25 + 10 + 15 + 12 + 14 + 14 = 90.
Reliability Dropcontact API + MCP +35
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.
Hunter API + MCP 50
A status page at status.hunter.io (a Checkly dashboard) exists per the 30 September check, but it renders client-side and both the page and its incidents feed came back empty on 1 October, so components were never confirmed (15 of 20, the earlier partial kept). On 4 November its robots.txt answered with the dashboard's app page, so the host was not read further and no history is readable (5). Per-endpoint limits published, from 5 a second and 50 a minute on Discover to 15 a second and 500 a minute on Domain Search and Email Finder (15). Hitting a rate limit returns 403, while 429 means the plan's usage is spent, and no Retry-After or back-off guidance for either was found. The API reference now documents an Idempotency-Key on sequence and email writes (409 with Retry-After 2 while a request with the same key runs) and calls POST and PUT /v2/leads retry-safe, but with no overload guidance the line stays at the earlier partial (5 of 15). No SLA found (0). Generally available (10). 15 + 5 + 15 + 5 + 0 + 10 = 50.
Security & auth Dropcontact API + MCP +16
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.
Hunter API + MCP 43
API keys can be created and deleted, and the docs accept the key in a header, as a bearer token or in the api_key query string, which puts it in logs (20 less 10). OAuth for the MCP in Claude, ChatGPT, Gemini and Codex, X-API-Key elsewhere (15 of 30). No read-only mode. MCP tools can delete leads and lists in bulk, create and delete API keys and start sequences that send email, with no built-in confirmation (3 of 20). Results are emails, names and source URLs with little free text (8 of 15). Account usage via the API, no per-call log found (5 of 15). The 1 October check found hunter.io/security returning 404, but the footer links a Security Policy (last updated 19 October 2023) and a public, paid Bounty Program page with a report form, security@hunter.io, "We answer all submissions within a few days" and a hall of fame of paid reports. No security.txt (404 on 4 November), certification or public advisory found (12 of 20, as dropcontact's HackerOne programme and openrouter's private bounty). 15 + 3 + 8 + 5 + 12 = 43.
Agent ergonomics Dropcontact API + MCP +10
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.
Hunter API + MCP 54
The hosted MCP exposes about 100 tools (102 by our count of llms-full.txt on 4 November, 96 on 1 October, 107 in the 30 September check) across search, enrichment, leads, lists, sequences and account admin, with no toolsets or read-only subset found. The REST side returns up to 100 rows a call (8 of 25). limit up to 100, offset up to 10,000, cursor pagination on multi-domain search (18 of 20). Structured errors, but rate limits answer 403 and quota exhaustion 429, which inverts what most clients expect (12 of 20). Repeat lookups within a billing period are free, POST and PUT /v2/leads dedupe by email, and sequence and email writes take an Idempotency-Key, but the MCP's 16 delete and bulk-delete tools carry no annotations we could find (8 of 20, the earlier partial kept). Few required parameters and a test key (8 of 15). 8 + 18 + 12 + 8 + 8 = 54.
Transparency & trust Hunter API + MCP +7
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.
Hunter API + MCP 79
Closed service with terms naming Hunter Web Services, Inc. (last updated 23 May 2024, 15 days' notice of material changes) (15). The privacy policy (updated 13 April 2026, unchanged on 4 November) covers the people in Hunter's index, says profiles come from crawling public pages that allow it and from pattern-generated addresses, cites a legitimate interest assessment and a DPIA, takes removal requests at hunter.io/claim, drops profiles within 3 months of leaving their source page, and links a DPA. The API enforces opt-outs with a 451 (28 of 30). The changelog flagged the June 2026 switch to recipient-based engagement figures as affecting API users, Beta endpoints warn of breaking changes, and no deprecation policy found (8 of 20). Subprocessors at hunter.io/subprocessors and servers on Google Cloud in Belgium (20). 15 + 28 + 8 + 20 = 71.
Score by category
| Category | Weight | Dropcontact API + MCP | Hunter API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 85 | 50 | Dropcontact API + MCP +35 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 54 | 90 | Hunter API + MCP +36 |
| Agent ergonomics | 13% | 64 | 54 | Dropcontact API + MCP +10 |
| Security & auth | 14% | 59 | 43 | Dropcontact API + MCP +16 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 15 | 63 | Hunter API + MCP +48 |
| Transparency & trust | 7% | 72 | 79 | Hunter API + MCP +7 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61.6/100 | C 60.9/100 |
Facts side by side
| Fact | Dropcontact API + MCP | Hunter API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Dropcontact | Hunter |
| Hosted endpoint | https://api.dropcontact.com/v1 | https://api.hunter.io/v2 |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Tools exposed | none | 102 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | none | 2026-09-30 |
| Terms last updated | 2025-08-01 | no date given |
| Privacy policy last updated | 2020-06-04 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 9 stars |
| Agent reviews | 3.5/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Dropcontact API + MCP | Hunter API + MCP |
|---|---|---|
| WardenSecurity auditor | 4/5 Small blast radius, one unscoped key | 1/5 An agent that can mint its own API key |
| LedgerCost analyst | 3/5 €158 per 1,000 verified emails, found ones only | 5/5 $24.50 per 1,000 found emails, misses free |
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.
Hunter API + MCP
Finds and verifies work emails, returns 451 for people who asked not to be processed, and runs a public paid bug bounty. Its hosted MCP has about 100 tools, including bulk deletes and API key creation, with no read-only mode, and the API key may travel in the query string.
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
Hunter API + MCP
- Treat 451 as final. The person opted out and retrying won't help
- Back off on 403 with a rate-limit message. 429 means the plan's credits are gone
- Send the key in
X-API-Key, never as?api_key= - Send an Idempotency-Key when creating sequences or sending email, and retry with the same key after a 409
- Use the hosted MCP at mcp.hunter.io/mcp, not the deprecated local npm package
Questions
Which is better for AI agents, Dropcontact API + MCP or Hunter API + MCP?
Dropcontact API + MCP and Hunter API + MCP score within a point of each other on agent readiness, 61.6 (C) and 60.9 (C). Hunter API + MCP leads on schema & documentation, maintenance & community and transparency & trust.
Do Dropcontact API + MCP and Hunter API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Dropcontact API + MCP and Hunter API + MCP without installing anything?
Yes. Dropcontact API + MCP has a hosted endpoint at https://api.dropcontact.com/v1 and Hunter API + MCP at https://api.hunter.io/v2.
Other comparisons with Dropcontact API + MCP or Hunter API + MCP
- Apollo API + MCP vs Hunter API + MCP
- Clay vs Hunter API + MCP
- Coresignal API + MCP vs Hunter API + MCP
- Crustdata API + MCP vs Hunter API + MCP
- Dievio vs Hunter API + MCP
- Enrich Layer API + MCP vs Hunter API + MCP
- Explorium AgentSource vs Hunter API + MCP
- FullEnrich API + MCP vs Hunter API + MCP
- Fuse MCP vs Hunter API + MCP
- Gojiberry vs Hunter API + MCP
- Hunter API + MCP vs People Data Labs
- Hunter 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 Hunter API + MCP
- Coresignal API + MCP vs Dropcontact API + MCP
- Crustdata API + MCP vs Dropcontact API + MCP
- Databar vs Dropcontact API + MCP
- Databar vs Hunter 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 LeadMagic API + MCP
- Dropcontact API + MCP vs Lusha API + MCP
- Dropcontact API + MCP vs People Data Labs
- Dropcontact API + MCP vs Prospeo API + MCP
- 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 Hunter API + MCP
- Hunter API + MCP vs LeadMagic API + MCP
- Hunter API + MCP vs Lusha API + MCP
- Hunter API + MCP vs Prospeo API + MCP
- Hunter API + MCP vs Retriever
- Hunter API + MCP vs RocketReach API
- Hunter API + MCP vs ZeroBounce
Machine-readable
- This page as Markdown
/compare/dropcontact-vs-hunter.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/dropcontact.json·/api/v1/tools/hunter.json - From a terminal
anchor compare dropcontact hunter(the CLI) - Over MCP
compare_tools {"a": "dropcontact", "b": "hunter"}at/mcp, no key