# Coresignal API + MCP vs Retriever (slim)

> Coresignal scores 62.1 (B) to Retriever's 32 (F) for lead search. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/coresignal-vs-retriever.md (~4,450 tokens) · this version ~880 tokens · JSON https://www.anchorterminal.com/compare/coresignal-vs-retriever.json · canonical https://www.anchorterminal.com/compare/coresignal-vs-retriever
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-18
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Coresignal API + MCP scores 62.1 (B) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Both do lead search.

- Coresignal API + MCP: B 62.1, rank #696 of 1557 · https://www.anchorterminal.com/tools/coresignal.min.md
- Retriever: F 32, rank #1455 of 1557 · https://www.anchorterminal.com/tools/retriever.min.md
- Coresignal API + MCP, good for Company and workforce research, headcount history and hiring signals at volume, and for pipelines that want raw records. Ahead on Reliability, 60 against 45; Security & auth, 58 against 23; Maintenance & community, 82 against 5; Transparency & trust, 71 against 49.
- Retriever, good for A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.

| Category | Coresignal API + MCP | Retriever |
| --- | --- | --- |
| Reliability (16%) | 60 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 86 | 82 |
| Agent ergonomics (13%) | 73 | 75 |
| Security & auth (14%) | 58 | 23 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 82 | 5 |
| Transparency & trust (7%) | 71 | 49 |

| Fact (where they differ) | Coresignal API + MCP | Retriever |
| --- | --- | --- |
| Vendor | Coresignal | Retriever |
| Hosted endpoint | `https://api.coresignal.com/cdapi` | `https://api.retriever.run/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Tools exposed | 5 | 67 |
| Read-only variant documented | no | yes |
| MCP registry | `com.coresignal/mcp` | not listed |
| Last release | 2026-11-01 | none |
| Terms last updated | 2022-02-21 | 2026-08-30 |
| Privacy policy last updated | 2026-08-25 | 2026-08-30 |
| Terms restrict automated access | not found in the text | yes |
| Popularity | 2 stars | none |
| Agent reviews | 3.5/5 (2) | none |

Why the edge:
- Maintenance & community, Coresignal API + MCP +77: Coresignal API + MCP 82 (Release notes have dated entries to 1 November 2026 (30).); Retriever 5 (No changelog, release notes or dated API change found, and the docs carry no dates; the blog's posts are marketing articles, not release notes (0 and 0).)
- Security & auth, Coresignal API + MCP +35: Coresignal API + MCP 58 (`apikey` header on REST.); Retriever 23 (The MCP server's OAuth 2.1 issues an ordinary API key, and keys have no scopes or expiry and work as their creator in that organisation: plain revocable keys (2…)
- Transparency & trust, Coresignal API + MCP +22: Coresignal API + MCP 71 (Closed service with published terms, but the terms (last updated 21 February 2022) name Deeptrace Inc.); Retriever 49 (Closed source with clear terms, last updated 30 August 2026 (15).)
- Reliability, Coresignal API + MCP +15: Coresignal API + MCP 60 (Better Stack status page at status.coresignal.com with CDAPI, RTAPI and Self-service components (20).); Retriever 45 (No status page found, linked from neither the site nor the docs (0), so no incident history to read (5).)
