# Coresignal API + MCP vs FullEnrich API + MCP > Coresignal API + MCP has a score of 63.1 (B) against FullEnrich API + MCP's 59.8 (C). Both do lead search. The largest gap is payments & pricing, 20 points. Category scores, facts, verdicts and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/coresignal-vs-fullenrich - Markdown: https://www.anchorterminal.com/compare/coresignal-vs-fullenrich.md (~1,600 tokens) - Slim: https://www.anchorterminal.com/compare/coresignal-vs-fullenrich.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/compare/coresignal-vs-fullenrich.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-05 Coresignal API + MCP has a score of 63.1 (B) against FullEnrich API + MCP's 59.8 (C). Both do lead search. The largest gap is payments & pricing, 20 points. - Coresignal API + MCP: grade B, 63.1/100, rank #208 of 452. Markdown https://www.anchorterminal.com/tools/coresignal.md · JSON https://www.anchorterminal.com/api/v1/tools/coresignal.json - FullEnrich API + MCP: grade C, 59.8/100, rank #258 of 452. Markdown https://www.anchorterminal.com/tools/fullenrich.md · JSON https://www.anchorterminal.com/api/v1/tools/fullenrich.json ## Which one, for what Pick Coresignal API + MCP for schema & documentation (+14), agent ergonomics (+13), maintenance & community (+14), transparency & trust (+7). Pick FullEnrich API + MCP for reliability (+5), payments & pricing (+20). ## Score by category | Category | Weight | Coresignal API + MCP | FullEnrich API + MCP | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 55 | 60 | FullEnrich API + MCP +5 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 86 | 72 | Coresignal API + MCP +14 | | Agent ergonomics | 13% (16.2 this run) | 73 | 60 | Coresignal API + MCP +13 | | Security & auth | 14% (17.5 this run) | 58 | 55 | Coresignal API + MCP +3 | | Payments & pricing | 10% (12.5 this run) | 20 | 40 | FullEnrich API + MCP +20 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 82 | 68 | Coresignal API + MCP +14 | | Transparency & trust | 7% (8.8 this run) | 73 | 66 | Coresignal API + MCP +7 | | Negative events | ≤15 | 0 | 0 | | | **Total** | | **63.1 · B** | **59.8 · C** | | ## Facts side by side | Fact | Coresignal API + MCP | FullEnrich API + MCP | | --- | --- | --- | | Kind | HTTP API | HTTP API | | Vendor | Coresignal | FullEnrich | | Hosted endpoint | `https://api.coresignal.com/cdapi` | `https://app.fullenrich.com/api/v2` | | Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP | | Auth | OAuth or key | OAuth or key | | Pricing | Paid | Freemium | | x402 | no | no | | Licence | none | none | | Tools exposed | 5 | 13 | | 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` | `io.github.FullEnrich/fullenrich` | | Last release | 2026-08-07 | 2026-08-27 | | 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. **FullEnrich API + MCP.** Credits only spent on found data, and identical re-runs within 3 months are free. Enrichment sources are third-party providers the vendor doesn't name. ## Before you call either ### Coresignal API + MCP 1. Search for IDs first (free), then collect only the records you need 2. Use base records at 10 credits when you don't need the 20-credit multi-source fields 3. Use MCP v2 at /mcp/v2. The older /mcp endpoint will be deprecated 4. Treat a 402 as out of credits, not a transient error 5. Expect no work emails for EEA and UK people from the MCP email tool ### FullEnrich API + MCP 1. Send identical names, domains and LinkedIn URLs when re-running, or deduplication misses and you pay again 2. Expect 30 to 90 seconds a contact. Use the webhook or poll `get_enrichment_results` 3. Ask for mobiles only when needed. They cost 10 credits against 1 for a work email 4. Call `list_industries` and `list_seniorities` before filtering search 5. Use the 0-credit test contacts in the docs to check an integration ## Other comparisons with Coresignal API + MCP or FullEnrich API + MCP - [Apollo API + MCP vs Coresignal API + MCP](https://www.anchorterminal.com/compare/apollo-vs-coresignal.md) - [Apollo API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/apollo-vs-fullenrich.md) - [Coresignal API + MCP vs Crustdata API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-crustdata.md) - [Coresignal API + MCP vs Enrich Layer API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-enrich-layer.md) - [Coresignal API + MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-hunter.md) - [Coresignal API + MCP vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-leadmagic.md) - [Coresignal API + MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-lusha.md) - [Coresignal API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-prospeo.md) - [Crustdata API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-fullenrich.md) - [Enrich Layer API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/enrich-layer-vs-fullenrich.md) - [FullEnrich API + MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-hunter.md) - [FullEnrich API + MCP vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-leadmagic.md) - [FullEnrich API + MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-lusha.md) - [FullEnrich API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-prospeo.md) - [Coresignal API + MCP vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-dropcontact.md) - [Dropcontact API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-fullenrich.md)