Head to head · Lead enrichment · October 2026 research run
Dropcontact API + MCP vs LeadMagic API + MCP
LeadMagic API + MCP scores 64.5 (B) on agent readiness against Dropcontact API + MCP's 61.6 (C), and leads in 4 of 7 scored categories. Dropcontact API + MCP leads on reliability, payments & pricing 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 52
- Payments & pricing, 60 against 30
- Transparency & trust, 72 against 65
Also in its favour
- Free to start without a card
Watch for
No OpenAPI file or changelog
Best for Verification and email or mobile finding in automated pipelines, especially at volume on the plans with credit-free search.
Ahead on
- Schema & documentation, 93 against 54
- Agent ergonomics, 71 against 64
- Maintenance & community, 80 against 15
Watch for
No free credits, and payments are non-refundable; plans from $99 a month
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 LeadMagic API + MCP +65
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.
LeadMagic API + MCP 80
The hosted MCP server is in the official MCP registry as io.leadmagic/server (and io.leadmagic/sheets) since 3 October 2026, with 2.23.5 published on 15 October 2026, 20 days before 4 November (30). The changelog's newest entry is api 3.3.1 on 17 September, which alone would give 20. In the 90 days from 6 August, changelog entries on 25 August (web 3.2.0 and api 3.3.0) and 17 September (api 3.3.1), and ten io.leadmagic/server versions between 3 and 15 October (20). Public changelog and support, issue handling not visible (10 of 15). In the official MCP registry under the verified io.leadmagic namespace (15). No packages to judge (5 of 10). 30 + 20 + 10 + 15 + 5 = 80. The MCP section of the changelog stops at mcp 2.5.0 (2 May 2026), while the server card reports 2.23.6, undated.
Schema & documentation LeadMagic API + MCP +39
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.
LeadMagic API + MCP 93
OpenAPI file at leadmagic.io/openapi.json, per the 30 September check (25). llms.txt (10). MCP tools state their purpose and credit cost, and the server tells the model to report only data the tools returned (16 of 20). Typed request bodies (12 of 15). RFC 9457 problem details with a request_id on every error, and documented 400, 401, 402 and 429 cases (15). A dated changelog versioned per component, api 3.3.1 on 2026-09-17 (15).
Reliability Dropcontact API + MCP +33
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.
LeadMagic API + MCP 52
Own status page at leadmagic.io/status listing the REST API, web app, Email Finder, Mobile Finder, Email Validation and integrations, with a live API health check but no incident history, re-read on 4 November (10 of 20). No history to read (5). Per-second and per-minute limits published, 5 or 10 requests a second for credit-free search with a fair-use ceiling of 13,333 searches a day, and 300 or 600 Email Finder and Validation lookups a minute by plan (15). 429 carries Retry-After with advice to back off, a rejected 429 consumes no credits, and 400s aren't charged. Bulk job submissions and the MCP's Tables tools write data, and no idempotency key or safe-retry guidance for writes was found, so safe-retry guidance without keys, as runway and fal-video read retries of billed jobs (12). The Service Level and Availability Policy states there's no guaranteed uptime and service credits are discretionary, per the 1 October check (0). Generally available (10). 10 + 5 + 15 + 12 + 0 + 10 = 52.
Payments & pricing Dropcontact API + MCP +30
Dropcontact API + MCP 60
No x402, MPP or L402 (0). Plan prices and credit allowances are public in euros (Starter €79 and Growth €120 a month for 500 credits, 20 per cent off yearly), and a credit is one verified email found (given back when none is) or one email checked (20). 50 free credits at signup with no card (20). A person signs up in a browser and creates the key in the app (0). 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.
LeadMagic API + MCP 30
No x402, MPP or L402 (0). Plan prices, annual prices and per-endpoint credit costs are public, re-read on 4 November (20). There are no free credits, the pricing FAQ now calls payments non-refundable except where law or a signed agreement says otherwise, and a 14-day Search trial 'with no automatic charge' covers search only, with no word on whether a card is needed (0). A person signs up and pays in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Agent ergonomics LeadMagic API + MCP +7
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.
LeadMagic API + MCP 71
The full hosted MCP connection carries every tool, which the docs now split into four focused connections (Tables 22, Tables setup 22, Data enrichment 27, Bulk and signals 48 tools) so a client loads only one group. More than 30 tools on the full connection (5), plus 10 back for the focused connections, plus a free preview_cost tool and browse pages of up to 25 rows (3), so 18 of 25. Search filters and pages (16 of 20). Problem-details errors with request_id, 402 for credits and Retry-After on 429 (20). Unknown validation results and 400s are free, and preview_cost estimates before spending. No idempotency keys or tool annotations found (10 of 20). No official SDKs found. A terminal client, LeadMagic CLI (lm), shares the credits (7 of 15). 18 + 16 + 20 + 10 + 7 = 71.
Transparency & trust Dropcontact 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.
LeadMagic API + MCP 65
Closed service with terms naming Lead Magic Corporation, Massachusetts (15). The privacy policy covers people returned by the API and links a request form, a do-not-sell page and privacy@leadmagic.io. We found no stated legal basis, data sources or retention periods in it. The DPA uses SCCs and the UK IDTA (14 of 30). Changelog entries are dated, but no deprecation policy or notices found (6 of 20). The DPA points to a subprocessor list with 15 days' notice of changes and says data is processed in the US and elsewhere (12 of 20).
Score by category
| Category | Weight | Dropcontact API + MCP | LeadMagic API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 85 | 52 | Dropcontact API + MCP +33 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 54 | 93 | LeadMagic API + MCP +39 |
| Agent ergonomics | 13% | 64 | 71 | LeadMagic API + MCP +7 |
| Security & auth | 14% | 59 | 63 | LeadMagic API + MCP +4 |
| Payments & pricing | 10% | 60 | 30 | Dropcontact API + MCP +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 15 | 80 | LeadMagic API + MCP +65 |
| Transparency & trust | 7% | 72 | 65 | Dropcontact API + MCP +7 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61.6/100 | B 64.5/100 |
Facts side by side
| Fact | Dropcontact API + MCP | LeadMagic API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Dropcontact | LeadMagic |
| Hosted endpoint | https://api.dropcontact.com/v1 | https://api.leadmagic.io |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Tools exposed | none | 48 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.leadmagic/server |
| Last release | none | 2026-10-15 |
| Terms last updated | 2025-08-01 | 2026-08-31 |
| Privacy policy last updated | 2020-06-04 | 2026-09-20 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| 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 | yes |
| 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 | LeadMagic API + MCP |
|---|---|---|
| LedgerCost analyst | 3/5 €158 per 1,000 verified emails, found ones only | 4/5 $99 to start, then every response shows its cost |
| WardenSecurity auditor | 4/5 Small blast radius, one unscoped key | 3/5 No deletes, no read-only mode either |
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.
LeadMagic API + MCP
RFC 9457 problem-details errors with request_id, Retry-After on 429 and credit headers on every response. The hosted MCP server is in the official registry and can load one focused tool group. No free credits, payments are non-refundable, and plans start at $99 a month.
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
LeadMagic API + MCP
- Connect only the focused MCP group the task needs, such as https://mcp.leadmagic.io/mcp/enrichment-core for lookups
- Call
preview_costbefore bulk work. It's free - Read
X-Credits-Remainingafter each call instead of polling the balance - Treat 402 as out of credits and wait out Retry-After on 429
- Follow each table tool's returned approval step before deletions, cell edits or runs over 5 credits
Questions
Which is better for AI agents, Dropcontact API + MCP or LeadMagic API + MCP?
LeadMagic API + MCP scores 64.5 (B) on agent readiness against Dropcontact API + MCP's 61.6 (C), and leads in 4 of 7 scored categories. Dropcontact API + MCP leads on reliability, payments & pricing and transparency & trust.
Do Dropcontact API + MCP and LeadMagic API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Dropcontact API + MCP and LeadMagic API + MCP without installing anything?
Yes. Dropcontact API + MCP has a hosted endpoint at https://api.dropcontact.com/v1 and LeadMagic API + MCP at https://api.leadmagic.io.
Other comparisons with Dropcontact API + MCP or LeadMagic API + MCP
- Apollo API + MCP vs LeadMagic API + MCP
- Clay vs LeadMagic API + MCP
- Coresignal API + MCP vs LeadMagic API + MCP
- Crustdata API + MCP vs LeadMagic API + MCP
- Dievio vs LeadMagic API + MCP
- Enrich Layer API + MCP vs LeadMagic API + MCP
- Explorium AgentSource vs LeadMagic API + MCP
- FullEnrich API + MCP vs LeadMagic API + MCP
- Fuse MCP vs LeadMagic API + MCP
- Gojiberry vs LeadMagic API + MCP
- LeadMagic API + MCP vs Lusha API + MCP
- LeadMagic API + MCP vs People Data Labs
- LeadMagic API + MCP vs Prospeo API + MCP
- LeadMagic API + MCP vs Retriever
- LeadMagic API + MCP vs RocketReach API
- LeadMagic 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 LeadMagic API + MCP
- Coresignal API + MCP vs Dropcontact API + MCP
- Crustdata API + MCP vs Dropcontact API + MCP
- Databar vs Dropcontact API + MCP
- Databar vs LeadMagic 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 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 LeadMagic API + MCP
- Hunter API + MCP vs LeadMagic API + MCP
- LeadMagic API + MCP vs ZeroBounce
Machine-readable
- This page as Markdown
/compare/dropcontact-vs-leadmagic.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/dropcontact.json·/api/v1/tools/leadmagic.json - From a terminal
anchor compare dropcontact leadmagic(the CLI) - Over MCP
compare_tools {"a": "dropcontact", "b": "leadmagic"}at/mcp, no key