Head to head · Lead search · October 2026 research run
Crustdata API + MCP vs Hunter API + MCP
Hunter API + MCP scores 60.9 (C) on agent readiness against Crustdata API + MCP's 52.4 (D), and leads in 5 of 7 scored categories. Crustdata API + MCP leads on agent ergonomics and security & auth. Both do lead search.
Best lead, contact and company data APIs for AI agents · All 253 leads comparisons
Which one, for what
Best for Agents that monitor companies, people, jobs or posts over time and need change notifications.
Ahead on
- Agent ergonomics, 73 against 54
- Security & auth, 56 against 43
Watch for
No status page and no SLA
Best for Finding and verifying work emails from a domain or a name, where GDPR handling of the people looked up matters.
Ahead on
- Reliability, 50 against 42
- Payments & pricing, 60 against 8
- Maintenance & community, 63 against 57
- Transparency & trust, 79 against 56
Also in its favour
- Free to start without a card
- Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
- No incidents deducted, where Crustdata API + MCP loses 3 points for them
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.
Payments & pricing Hunter API + MCP +52
Crustdata API + MCP 8
No x402, MPP or L402 (0). Credit costs per endpoint and field are public, but no dollar price per credit is, and enterprise plans start at "four figures a month" through sales. We gave 5 rather than 0 because an agent can work out relative cost from the public credit table (5). Every new self-serve account now starts with $20 in free credits, but no page we read says whether signing up needs a card, so the line isn't met on the evidence (0). A person signs up in the dashboard (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 5 is 8.
Hunter API + MCP 60
No x402, MPP or L402 (0). Plan prices are public, and units are clear, 1 credit per email found, 0.5 per verification, nothing when no result comes back (20). Free plan with 50 credits a month and API and MCP access, no card (20). A person signs up in a browser, and the terms say accounts registered by bots are not permitted (0). Prices unchanged on 4 November. 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Transparency & trust Hunter API + MCP +23
Crustdata API + MCP 56
Closed service. The terms are a website-use notice naming CrustData Inc. (California), while the privacy policy names Crustdata Technologies Inc., and we found no API terms (8 of 30). The privacy policy (updated 19 May 2025) covers people in the datasets, cites consent, contract and legitimate interests, and runs an opt-out portal that removes data within 30 days and blocks it from coming back. Retention has no periods and no DPA is mentioned (15 of 30). Date-pinned versions and migration guides, but breaking changes inside the pinned version with no dated notice (8 of 20). US transfers stated, no subprocessor list (5 of 20).
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.
Agent ergonomics Crustdata API + MCP +19
Crustdata API + MCP 73
Premium field groups are opt-in and billed per group, cursor pagination, and the MCP publishes its tool catalogue as a resource instead of a long tools/list (22 of 25). Cursor pagination and rich filters (20). Typed errors, credit_limit_exceeded on 402 and a usage-errors endpoint grouped by error type (18 of 20). Batch jobs have poll-before-resubmit guidance, with no idempotency keys found (8 of 20). Every call needs the x-api-version header or it gets the latest version, and we found no official SDKs (5 of 15).
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.
Security & auth Crustdata API + MCP +13
Crustdata API + MCP 56
Bearer keys, several named keys per account with active, inactive and deleted states, per-key endpoint restrictions and monthly credit caps since July 2026. OAuth for the MCP (28 of 30). Per-key endpoint limits give least privilege. Watchers create standing jobs, and the MCP docs don't separate read and write tools or ask for confirmation (12 of 20). Live web fetch, web search and social posts return untrusted text, and we found no prompt-injection guidance (2 of 15). Usage and logs filterable by key, a usage events API from October 2026, and X-Credits-Used on every response (14 of 15). No security.txt, bug bounty, disclosure policy or certification found (0 of 20).
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.
Reliability Hunter API + MCP +8
Crustdata API + MCP 42
No status page found. status.crustdata.com still doesn't answer and the docs link none (0). No readable incident history (5). Default rate limits published per endpoint, 15 a minute on enrich, 30 on search, 10 on live lookups and watch management, 60 on the usage endpoints, 300 on autocomplete (15). 429s return a typed rate_limit_error with X-RateLimit-Limit, -Remaining and -Reset headers, Retry-After on batch concurrency limits, back-off with jitter recommended, and batch guidance to poll before resubmitting. No idempotency keys, so safe-retry guidance without keys (12). No SLA found, and the published terms cover the website only (0). The API is generally available. Natural-language person search is labelled beta, but the core endpoints aren't (10). 0 + 5 + 15 + 12 + 0 + 10 = 42.
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.
Maintenance & community Hunter API + MCP +6
Crustdata API + MCP 57
The changelog labels every entry by month only, newest "October 2026" (NAICS and SIC on company search, geo_polygon, research profiles, the Usage API), with no exact dates or feed, and Crustdata publishes no SDK, MCP package or other dated source of its own. Read as the Zoho listings read month-only entries, dated to the month, all of October lies 4 to 34 days back, within 90 days but not shown within 30 (20). Nine entries fall in September and October, months wholly inside the 90 days from 6 August (20). Detailed public changelog, and we didn't test support (12 of 15). The only registry entry found on 1 October sat under a personal GitHub namespace, and we found no official SDKs (0). Versioned specs are current. No packages to judge (5 of 10). 20 + 20 + 12 + 0 + 5 = 57.
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.
Score by category
| Category | Weight | Crustdata API + MCP | Hunter API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 42 | 50 | Hunter API + MCP +8 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 89 | 90 | Hunter API + MCP +1 |
| Agent ergonomics | 13% | 73 | 54 | Crustdata API + MCP +19 |
| Security & auth | 14% | 56 | 43 | Crustdata API + MCP +13 |
| Payments & pricing | 10% | 8 | 60 | Hunter API + MCP +52 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 57 | 63 | Hunter API + MCP +6 |
| Transparency & trust | 7% | 56 | 79 | Hunter API + MCP +23 |
| Negative events | ≤15 | -3 | 0 | |
| Total | D 52.4/100 | C 60.9/100 |
Facts side by side
| Fact | Crustdata API + MCP | Hunter API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Crustdata | Hunter |
| Hosted endpoint | https://api.crustdata.com | https://api.hunter.io/v2 |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | 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 | no date given | no date given |
| Privacy policy last updated | 2025-05-19 | 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 | 2.5/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Crustdata API + MCP | Hunter API + MCP |
|---|---|---|
| LedgerCost analyst | 2/5 Credits with no dollar figure attached | 5/5 $24.50 per 1,000 found emails, misses free |
| WardenSecurity auditor | 3/5 Per-key caps, no security programme | 1/5 An agent that can mint its own API key |
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
Crustdata API + MCP
Per-field credit prices readable per account, X-Credits-Used on every response, per-key caps and $20 in free credits for new self-serve accounts. No status page, no SLA, no dollar price per credit, and changes that refuse earlier valid requests posted only after they shipped.
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
Crustdata API + MCP
- Always send
x-api-version: 2025-11-01. Unpinned calls get the latest version - Call
/account/endpointsfirst to see what your plan enables and what each field costs - Ask only for the premium field groups you need, since each one bills
- Poll
GET /batch/{id}before submitting more batch jobs. Active jobs count against a cap of 5 to 30 - Read the
crustdata://catalogresource before calling MCP tools
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, Crustdata API + MCP or Hunter API + MCP?
Hunter API + MCP scores 60.9 (C) on agent readiness against Crustdata API + MCP's 52.4 (D), and leads in 5 of 7 scored categories. Crustdata API + MCP leads on agent ergonomics and security & auth.
Do Crustdata API + MCP and Hunter API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Crustdata API + MCP and Hunter API + MCP without installing anything?
Yes. Crustdata API + MCP has a hosted endpoint at https://api.crustdata.com and Hunter API + MCP at https://api.hunter.io/v2.
Other comparisons with Crustdata API + MCP or Hunter API + MCP
- Apollo API + MCP vs Crustdata API + MCP
- Apollo API + MCP vs Hunter API + MCP
- Clay vs Crustdata API + MCP
- Clay vs Hunter API + MCP
- Coresignal API + MCP vs Crustdata API + MCP
- Coresignal API + MCP vs Hunter API + MCP
- Crustdata API + MCP vs Databar
- Crustdata API + MCP vs Dievio
- Crustdata API + MCP vs Enrich Layer API + MCP
- Crustdata API + MCP vs Explorium AgentSource
- Crustdata API + MCP vs FullEnrich API + MCP
- Crustdata API + MCP vs Fuse MCP
- Crustdata API + MCP vs Gojiberry
- Crustdata API + MCP vs LeadMagic API + MCP
- Crustdata API + MCP vs Lusha API + MCP
- Crustdata API + MCP vs People Data Labs
- Crustdata API + MCP vs Prospeo API + MCP
- Crustdata API + MCP vs Retriever
- Crustdata API + MCP vs RocketReach API
- Crustdata API + MCP vs ZoomInfo 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
- Clearbit vs Crustdata API + MCP
- Clearbit vs Hunter API + MCP
- Crustdata API + MCP vs Dropcontact API + MCP
- Crustdata API + MCP vs FullContact
- Crustdata API + MCP vs ZeroBounce
- Databar vs Hunter API + MCP
- Dropcontact API + MCP vs Hunter 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/crustdata-vs-hunter.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/crustdata.json·/api/v1/tools/hunter.json - From a terminal
anchor compare crustdata hunter(the CLI) - Over MCP
compare_tools {"a": "crustdata", "b": "hunter"}at/mcp, no key