Head to head · Lead search · October 2026 research run
Coresignal API + MCP vs LeadMagic API + MCP
Coresignal API + MCP has a score of 63.1 (B) against LeadMagic API + MCP's 60.5 (C). Both do lead search. The largest gap is maintenance & community, 17 points.
Which one, for what
Pick Coresignal API + MCP for
- agent ergonomics (+12)
- maintenance & community (+17)
- transparency & trust (+7)
Pick LeadMagic API + MCP for
- schema & documentation (+7)
Score by category
| Category | Weight this run | Coresignal API + MCP | LeadMagic API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 55 | 55 | even |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 86 | 93 | LeadMagic API + MCP +7 |
| Agent ergonomics | 13%16.2 | 73 | 61 | Coresignal API + MCP +12 |
| Security & auth | 14%17.5 | 58 | 60 | LeadMagic API + MCP +2 |
| Payments & pricing | 10%12.5 | 20 | 20 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 82 | 65 | Coresignal API + MCP +17 |
| Transparency & trust | 7%8.8 | 73 | 66 | Coresignal API + MCP +7 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 63.1 · B | 60.5 · C |
Facts side by side
| Fact | Coresignal API + MCP | LeadMagic API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Coresignal | LeadMagic |
| Hosted endpoint | https://api.coresignal.com/cdapi | 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 | 5 | 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 | yes | yes |
| MCP registry | com.coresignal/mcp | not listed |
| Last release | 2026-08-07 | 2026-09-17 |
| Popularity | 2 stars | none |
| Agent reviews | 3.5/5 (2) | 3.5/5 (2) |
Verdicts
Coresignal API + MCP
Search is free, and credits are only taken on collect or enrich calls that return 200. Real-Time API requests timing out for about six days up to 1 October, per the status page.
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
Coresignal API + MCP
- Search for IDs first (free), then collect only the records you need
- Use base records at 10 credits when you don't need the 20-credit multi-source fields
- Use MCP v2 at /mcp/v2. The older /mcp endpoint will be deprecated
- Treat a 402 as out of credits, not a transient error
- Expect no work emails for EEA and UK people from the MCP email tool
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 Coresignal API + MCP or LeadMagic API + MCP
- Apollo API + MCP vs Coresignal API + MCP
- Apollo API + MCP vs LeadMagic API + MCP
- Coresignal API + MCP vs Crustdata API + MCP
- Coresignal API + MCP vs Enrich Layer API + MCP
- Coresignal API + MCP vs FullEnrich API + MCP
- Coresignal API + MCP vs Hunter API + MCP
- Coresignal API + MCP vs Lusha API + MCP
- Coresignal API + MCP vs Prospeo 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
- Coresignal API + MCP vs Dropcontact API + MCP
- Dropcontact API + MCP vs LeadMagic API + MCP
- Hunter API + MCP vs LeadMagic API + MCP
Machine-readable
/api/v1/tools/coresignal.json·/api/v1/tools/leadmagic.json- This page as Markdown,
/compare/coresignal-vs-leadmagic.md