Head to head · Lead enrichment · October 2026 research run
Dropcontact API + MCP vs LeadMagic API + MCP
LeadMagic API + MCP has a score of 60.5 (C) against Dropcontact API + MCP's 51.1 (D). Both do lead enrichment. The largest gap is schema & documentation, 52 points.
Which one, for what
Pick Dropcontact API + MCP for
- payments & pricing (+20)
- transparency & trust (+7)
Pick LeadMagic API + MCP for
- schema & documentation (+52)
- maintenance & community (+47)
Score by category
| Category | Weight this run | Dropcontact API + MCP | LeadMagic API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 57 | 55 | Dropcontact API + MCP +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 41 | 93 | LeadMagic API + MCP +52 |
| Agent ergonomics | 13%16.2 | 60 | 61 | LeadMagic API + MCP +1 |
| Security & auth | 14%17.5 | 59 | 60 | LeadMagic API + MCP +1 |
| Payments & pricing | 10%12.5 | 40 | 20 | Dropcontact API + MCP +20 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 18 | 65 | LeadMagic API + MCP +47 |
| Transparency & trust | 7%8.8 | 73 | 66 | Dropcontact API + MCP +7 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 51.1 · D | 60.5 · C |
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 |
| Licence | none | none |
| Tools exposed | none | 48 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | not listed |
| Last release | none | 2026-09-17 |
| Popularity | none | none |
| Agent reviews | 3.5/5 (2) | 3.5/5 (2) |
Verdicts
Dropcontact API + MCP
Pay on success, with credits refunded when no email is found. No OpenAPI spec, llms.txt or changelog.
LeadMagic API + MCP
RFC 9457 problem-details errors with request_id, and Retry-After on 429. No free tier or trial credits, plans from $99 a month.
Before you call either
Dropcontact API + MCP
- Send a company name or website with every contact, or you get
only_contact_data - Send only documented fields. New accounts get a 400 for unknown ones
- Match webhook results by
request_id, since order isn't guaranteed and duplicates happen - Poll no faster than every 30 seconds, as the not-ready response asks
- Post an empty contact to read the credit balance at no cost
LeadMagic API + MCP
- 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
- Keep credit-free search under 13,333 calls a day per account
- Retry
unknownvalidations later. They cost nothing
Other comparisons with Dropcontact API + MCP or LeadMagic API + MCP
- Apollo API + MCP vs LeadMagic API + MCP
- Coresignal API + MCP vs LeadMagic API + MCP
- Crustdata API + MCP vs LeadMagic API + MCP
- Enrich Layer API + MCP vs LeadMagic API + MCP
- FullEnrich API + MCP vs LeadMagic API + MCP
- LeadMagic API + MCP vs Lusha API + MCP
- LeadMagic API + MCP vs Prospeo API + MCP
- Apollo API + MCP vs Dropcontact API + MCP
- Coresignal API + MCP vs Dropcontact API + MCP
- Crustdata API + MCP vs Dropcontact API + MCP
- Dropcontact API + MCP vs Enrich Layer API + MCP
- Dropcontact API + MCP vs FullEnrich API + MCP
- Dropcontact API + MCP vs Hunter API + MCP
- Dropcontact API + MCP vs Lusha API + MCP
- Dropcontact API + MCP vs Prospeo API + MCP
- Hunter API + MCP vs LeadMagic API + MCP
Machine-readable
/api/v1/tools/dropcontact.json·/api/v1/tools/leadmagic.json- This page as Markdown,
/compare/dropcontact-vs-leadmagic.md