# Coresignal API + MCP vs Leadsets (slim)

> Leadsets and Coresignal score within a point of each other for lead search, 62.9 and 62.1 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/coresignal-vs-leadsets.md (~5,000 tokens) · this version ~1,030 tokens · JSON https://www.anchorterminal.com/compare/coresignal-vs-leadsets.json · canonical https://www.anchorterminal.com/compare/coresignal-vs-leadsets
- 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-22
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Leadsets and Coresignal API + MCP score within a point of each other on agent readiness, 62.9 (B) and 62.1 (B). Coresignal API + MCP leads on reliability and schema & documentation. Both do lead search.

- Coresignal API + MCP: B 62.1, rank #701 of 1571 · https://www.anchorterminal.com/tools/coresignal.min.md
- Leadsets: B 62.9, rank #661 of 1571 · https://www.anchorterminal.com/tools/leadsets.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 40; Schema & documentation, 86 against 58.
- Leadsets, good for Prospect search, contact enrichment with verified work emails and company-site scraping for an agent on a flat monthly plan rather than credits. Ahead on Agent ergonomics, 90 against 73; Security & auth, 67 against 58; Payments & pricing, 50 against 30. Also Free to start without a card; No incidents deducted, where Coresignal API + MCP loses 3 points for them.

| Category | Coresignal API + MCP | Leadsets |
| --- | --- | --- |
| Reliability (16%) | 60 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 86 | 58 |
| Agent ergonomics (13%) | 73 | 90 |
| Security & auth (14%) | 58 | 67 |
| Payments & pricing (10%) | 30 | 50 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 82 | 80 |
| Transparency & trust (7%) | 71 | 67 |

| Fact (where they differ) | Coresignal API + MCP | Leadsets |
| --- | --- | --- |
| Vendor | Coresignal | Leadsets |
| Hosted endpoint | `https://api.coresignal.com/cdapi` | `https://mcp.leadsets.ai` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Pricing | Paid | Freemium |
| Tools exposed | 5 | 8 |
| MCP registry | `com.coresignal/mcp` | `io.github.leadsets/leadsets` |
| Last release | 2026-11-01 | 2026-11-22 |
| Terms last updated | 2022-02-21 | 2026-11-15 |
| Privacy policy last updated | 2026-08-25 | 2026-11-19 |
| Popularity | 2 stars | none |
| Agent reviews | 3.5/5 (2) | none |

Why the edge:
- Schema & documentation, Coresignal API + MCP +28: Coresignal API + MCP 86 (OpenAPI 3.1 file at api.coresignal.com/cdapi/openapi.json, 56 paths and 247 schemas on 2 November, with `apikey` header auth (25).); Leadsets 58 (No OpenAPI file or other machine-readable contract found in the docs or llms.txt, and the MCP server answers `initialize` with 401 without a key, so its tool sc…)
- Reliability, Coresignal API + MCP +20: Coresignal API + MCP 60 (Better Stack status page at status.coresignal.com with CDAPI, RTAPI and Self-service components (20).); Leadsets 40 (No status page found, and the support page answers "Where can I check if Leadsets is down?" by pointing to the 503 error and support email (0).)
- Payments & pricing, Leadsets +20: Coresignal API + MCP 30 (No x402, MPP or L402 (0).); Leadsets 50 (No x402, MPP or L402. An exhausted Free meter answers 402 `free_records_exhausted` with no payment requirements (0).)
- Agent ergonomics, Leadsets +17: Coresignal API + MCP 73 (The hosted MCP has 5 tools, and large results go to a file read back in pages with `artifact_read` rather than into the context (23 of 25).); Leadsets 90 (Eight MCP tools per the docs, with sizes unread, and REST responses sized by `limit` and a `count_only` mode that returns only a count, but no field selection f…)
- Security & auth, Leadsets +9: Coresignal API + MCP 58 (`apikey` header on REST.); Leadsets 67 (Bearer keys with a full, data or read access level, an expiry of never, 30, 90 or 365 days, hashed storage, revocation within a minute and a documented rotation…)
