# Coresignal API + MCP vs Prospeo API + MCP

> Coresignal API + MCP has a score of 63.1 (B) against Prospeo API + MCP's 51.1 (D). Both do lead search. The largest gap is maintenance & community, 48 points. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/coresignal-vs-prospeo
- Markdown: https://www.anchorterminal.com/compare/coresignal-vs-prospeo.md (~1,600 tokens)
- Slim: https://www.anchorterminal.com/compare/coresignal-vs-prospeo.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/coresignal-vs-prospeo.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-04

Coresignal API + MCP has a score of 63.1 (B) against Prospeo API + MCP's 51.1 (D). Both do lead search. The largest gap is maintenance & community, 48 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
- Prospeo API + MCP: grade D, 51.1/100, rank #356 of 452. Markdown https://www.anchorterminal.com/tools/prospeo.md · JSON https://www.anchorterminal.com/api/v1/tools/prospeo.json

## Which one, for what

Pick Coresignal API + MCP for reliability (+20), schema & documentation (+25), maintenance & community (+48), transparency & trust (+28).

Pick Prospeo API + MCP for agent ergonomics (+6), payments & pricing (+20).

## Score by category

| Category | Weight | Coresignal API + MCP | Prospeo API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 55 | 35 | Coresignal API + MCP +20 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 86 | 61 | Coresignal API + MCP +25 |
| Agent ergonomics | 13% (16.2 this run) | 73 | 79 | Prospeo API + MCP +6 |
| Security & auth | 14% (17.5 this run) | 58 | 54 | Coresignal API + MCP +4 |
| Payments & pricing | 10% (12.5 this run) | 20 | 40 | Prospeo API + MCP +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 82 | 34 | Coresignal API + MCP +48 |
| Transparency & trust | 7% (8.8 this run) | 73 | 45 | Coresignal API + MCP +28 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **63.1 · B** | **51.1 · D** | |

## Facts side by side

| Fact | Coresignal API + MCP | Prospeo API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Coresignal | Prospeo |
| Hosted endpoint | `https://api.coresignal.com/cdapi` | `https://api.prospeo.io` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | none | MIT |
| Tools exposed | 5 | 8 |
| 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 | no |
| MCP registry | `com.coresignal/mcp` | `io.prospeo/prospeo-mcp-server` |
| Last release | 2026-08-07 | 2026-06-01 |
| Popularity | 2 stars | 0 stars, 641 npm/wk |
| 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.

**Prospeo API + MCP.** MCP tool descriptions say when to use each tool, its credit cost and the next call. No status page, SLA or changelog.

## 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

### Prospeo API + MCP

1. Call `search_suggestions` before using location, technology or industry filters, or the search returns nothing
2. Pass `person_id` values from search into `bulk_enrich_person`, 25 at a time
3. Branch on the body `error_code`, not the HTTP status, which is 400 for most failures
4. Set `enrich_mobile` only when needed. A mobile costs 10 credits against 1 for an email
5. Use Enrich Person. The old Email Finder endpoint was removed in March 2026

## Other comparisons with Coresignal API + MCP or Prospeo API + MCP

- [Apollo API + MCP vs Coresignal API + MCP](https://www.anchorterminal.com/compare/apollo-vs-coresignal.md)
- [Apollo API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/apollo-vs-prospeo.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 FullEnrich API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-fullenrich.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)
- [Crustdata API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-prospeo.md)
- [Enrich Layer API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/enrich-layer-vs-prospeo.md)
- [FullEnrich API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-prospeo.md)
- [LeadMagic API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/leadmagic-vs-prospeo.md)
- [Lusha API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/lusha-vs-prospeo.md)
- [Coresignal API + MCP vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-dropcontact.md)
- [Dropcontact API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-prospeo.md)
- [Hunter API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/hunter-vs-prospeo.md)