Head to head · Email finding · October 2026 research run
Hunter API + MCP vs Lusha API + MCP
Lusha API + MCP scores 64.8 (B) on agent readiness against Hunter API + MCP's 60.9 (C), and leads in 4 of 7 scored categories. Hunter API + MCP leads on schema & documentation. Both do email finding.
Best lead, contact and company data APIs for AI agents · All 253 leads comparisons
Which one, for what
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 83
Also in its favour
- Free to start without a card
- No incidents deducted, where Lusha API + MCP loses 6 points for them
Watch for
Hosted MCP has about 100 tools, including bulk deletes and API key creation, with no read-only mode
Best for Sales teams that want contact and company enrichment, signals and prospecting from one vendor, with a free plan to start.
Ahead on
- Reliability, 85 against 50
- Security & auth, 59 against 43
- Maintenance & community, 82 against 63
Watch for
At least 1 credit per request even when nothing matches
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 Lusha API + MCP +35
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.
Lusha API + MCP 85
Atlassian Statuspage at status.lusha.com with a Lusha API component and AWS us-east-1 components (20). The history feed (history.atom) lists one incident from 4 August to 2 November 2026, errors and incomplete results in Prospecting company search for some users on 7 August (20:44 to 21:33 IDT), partial and so minor; the 3 August API error incident falls just outside the window (20). Limits per plan, from 40 a minute and 100 a day on Free to 300 a minute and 50,000 a day on Scale (15). 429 documented with advice to back off exponentially, no Retry-After mentioned (10 of 15). The trust centre states a 99.95 per cent uptime SLA (10). Generally available (10). 20+20+15+10+10+10 = 85.
Maintenance & community Lusha API + MCP +19
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.
Lusha API + MCP 82
Version 2.20.1 on 2026-10-29 (30). Fourteen dated versions from 2.7.0 on 5 August to 2.20.1 on 29 October 2026 (20). Detailed public changelog and support, issue handling not visible (12 of 15). Listed in the official MCP registry as com.lusha.mcp/mcp 1.0.0, a domain-verified namespace, active since 18 June 2026 (15). No packages to judge (5 of 10). 30+20+12+15+5 = 82.
Security & auth Lusha API + MCP +16
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.
Lusha API + MCP 59
REST takes an api_key header. Every user gets a key, admins can mint more and cap each one's monthly credits, and a key a user makes for themselves has no cap of its own. OAuth for the MCP in Claude, ChatGPT and Codex, x-api-key elsewhere. No endpoint scopes found (22 of 30). Credit caps limit damage, but the MCP isn't read-only and writes to workspace tables and CRM exports (8 of 20). Signals and conversation data carry some free text, no injection guidance found (5 of 15). Usage endpoint, no per-call log found (8 of 15). SOC 2 Type II and five ISO certifications claimed in the trust centre, ISO 27701 named in the privacy notice, security.txt valid (Expires 1 May 2027, read on 2 November), no bug bounty found (16 of 20).
Schema & documentation Hunter API + MCP +7
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.
Lusha API + MCP 83
OpenAPI files per the 30 September check (25). llms.txt (10). Reference pages explain credit use per call with worked examples (15 of 20). Typed inputs (12 of 15). Standard HTTP codes and examples, no error catalogue found (10 of 15). Semantic versioning with a support matrix and a dated changelog. Version numbers run out of order (2.8.0 dated after 2.12.0), and breaking changes shipped in minor versions (11 of 15).
Score by category
| Category | Weight | Hunter API + MCP | Lusha API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 50 | 85 | Lusha API + MCP +35 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 83 | Hunter API + MCP +7 |
| Agent ergonomics | 13% | 54 | 51 | Hunter API + MCP +3 |
| Security & auth | 14% | 43 | 59 | Lusha API + MCP +16 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 63 | 82 | Lusha API + MCP +19 |
| Transparency & trust | 7% | 79 | 80 | Lusha API + MCP +1 |
| Negative events | ≤15 | 0 | -6 | |
| Total | C 60.9/100 | B 64.8/100 |
Facts side by side
| Fact | Hunter API + MCP | Lusha API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Hunter | Lusha |
| Hosted endpoint | https://api.hunter.io/v2 | https://api.lusha.com |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Tools exposed | 102 | 50 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | com.lusha.mcp/mcp |
| Last release | 2026-09-30 | 2026-10-29 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | 2026-09-01 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 9 stars | none |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Hunter API + MCP | Lusha API + MCP |
|---|---|---|
| LedgerCost analyst | 5/5 $24.50 per 1,000 found emails, misses free | 3/5 Seven credits for one contact, and a miss still costs one |
| WardenSecurity auditor | 1/5 An agent that can mint its own API key | 3/5 Credit caps on admin keys, none on the rest |
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
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.
Lusha API + MCP
API key on every plan, including Free with 40 credits a month, and a semantic-versioned changelog with frequent dated releases. At least 1 credit is charged per request even when nothing matches, and since 5 October 2026 Enrich Contacts can return partial waterfall results with a job to poll, a change announced the day it shipped.
Before you call either
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
Lusha API + MCP
- Batch up to 25 contacts a request. A single bulk request costs 1 credit, not 1 per contact
- Ask for phones only when needed. A phone is 5 credits against 1 for an email
- Use the Buying Group endpoint. Decision Makers was retired on 2026-09-04
- When Enrich Contacts returns a
job, pollGET /v3/contacts/jobs/{jobId}everyretryAfterseconds untilcomplete,expiredorfailed. Polling costs no credits - Back off exponentially on 429. Free keys stop at 100 requests a day
Questions
Which is better for AI agents, Hunter API + MCP or Lusha API + MCP?
Lusha API + MCP scores 64.8 (B) on agent readiness against Hunter API + MCP's 60.9 (C), and leads in 4 of 7 scored categories. Hunter API + MCP leads on schema & documentation.
Do Hunter API + MCP and Lusha API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Hunter API + MCP and Lusha API + MCP without installing anything?
Yes. Hunter API + MCP has a hosted endpoint at https://api.hunter.io/v2 and Lusha API + MCP at https://api.lusha.com.
Other comparisons with Hunter API + MCP or Lusha API + MCP
- Apollo API + MCP vs Hunter API + MCP
- Apollo API + MCP vs Lusha API + MCP
- Clay vs Hunter API + MCP
- Clay vs Lusha API + MCP
- Coresignal API + MCP vs Hunter API + MCP
- Coresignal API + MCP vs Lusha API + MCP
- Crustdata API + MCP vs Hunter API + MCP
- Crustdata API + MCP vs Lusha API + MCP
- Dievio vs Hunter API + MCP
- Dievio vs Lusha API + MCP
- Enrich Layer API + MCP vs Hunter API + MCP
- Enrich Layer API + MCP vs Lusha API + MCP
- Explorium AgentSource vs Hunter API + MCP
- Explorium AgentSource vs Lusha API + MCP
- FullEnrich API + MCP vs Hunter API + MCP
- FullEnrich API + MCP vs Lusha API + MCP
- Fuse MCP vs Hunter API + MCP
- Fuse MCP vs Lusha API + MCP
- Gojiberry vs Hunter API + MCP
- Gojiberry vs Lusha API + MCP
- Hunter API + MCP vs People Data Labs
- Hunter API + MCP vs ZoomInfo API + MCP
- LeadMagic API + MCP vs Lusha API + MCP
- Lusha API + MCP vs People Data Labs
- Lusha API + MCP vs Prospeo API + MCP
- Lusha API + MCP vs Retriever
- Lusha API + MCP vs RocketReach API
- Lusha API + MCP vs ZoomInfo API + MCP
- Clearbit vs Hunter API + MCP
- Clearbit vs Lusha API + MCP
- Databar vs Hunter API + MCP
- Databar vs Lusha API + MCP
- Dropcontact API + MCP vs Hunter API + MCP
- Dropcontact API + MCP vs Lusha API + MCP
- FullContact vs Hunter API + MCP
- FullContact vs Lusha API + MCP
- Lusha API + MCP vs ZeroBounce
- Hunter API + MCP vs LeadMagic 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/hunter-vs-lusha.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hunter.json·/api/v1/tools/lusha.json - From a terminal
anchor compare hunter lusha(the CLI) - Over MCP
compare_tools {"a": "hunter", "b": "lusha"}at/mcp, no key