# Coresignal API + MCP vs ZoomInfo API + MCP

> ZoomInfo API + MCP scores 72.2 (BB) on agent readiness against Coresignal API + MCP's 62.9 (B), and leads in 4 of 7 scored categories. Coresignal API + MCP leads on maintenance & community. Both do lead search. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/coresignal-vs-zoominfo
- Markdown: https://www.anchorterminal.com/compare/coresignal-vs-zoominfo.md (~2,500 tokens)
- Slim: https://www.anchorterminal.com/compare/coresignal-vs-zoominfo.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/coresignal-vs-zoominfo.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-09

ZoomInfo API + MCP scores 72.2 (BB) on agent readiness against Coresignal API + MCP's 62.9 (B), and leads in 4 of 7 scored categories. Coresignal API + MCP leads on maintenance & community. Both do lead search.

- Coresignal API + MCP: grade B, 62.9/100, rank #373 of 842. Markdown https://www.anchorterminal.com/tools/coresignal.md · JSON https://www.anchorterminal.com/api/v1/tools/coresignal.json
- ZoomInfo API + MCP: grade BB, 72.2/100, rank #106 of 842. Markdown https://www.anchorterminal.com/tools/zoominfo.md · JSON https://www.anchorterminal.com/api/v1/tools/zoominfo.json

## Which one, for what

### Coresignal API + MCP (B)

Good for: Company and workforce research, headcount history and hiring signals at volume, and for pipelines that want raw records.

Ahead on:
- Maintenance & community, 82 against 76

Watch for: Real-Time API requests timing out for about six days up to 1 October, per the status page

### ZoomInfo API + MCP (BB)

Good for: Sales and marketing agents that need company, contact, intent and business-event data from one vendor, with free search before paid enrichment.

Ahead on:
- Reliability, 87 against 55
- Security & auth, 65 against 58
- Payments & pricing, 40 against 20

Also in its favour:
- Agent-ready, a grade of BB or better

Watch for: The Licence Terms and Conditions bar disclosing benchmark results and automated access outside ZoomInfo's own tools without written approval


## Score by category

| Category | Weight | Coresignal API + MCP | ZoomInfo API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 55 | 87 | ZoomInfo API + MCP +32 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 86 | 84 | Coresignal API + MCP +2 |
| Agent ergonomics | 13% (16.2 this run) | 73 | 71 | Coresignal API + MCP +2 |
| Security & auth | 14% (17.5 this run) | 58 | 65 | ZoomInfo API + MCP +7 |
| Payments & pricing | 10% (12.5 this run) | 20 | 40 | ZoomInfo API + MCP +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 82 | 76 | Coresignal API + MCP +6 |
| Transparency & trust | 7% (8.8 this run) | 71 | 75 | ZoomInfo API + MCP +4 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **62.9 · B** | **72.2 · BB** | |

## Facts side by side

| Fact | Coresignal API + MCP | ZoomInfo API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Coresignal | ZoomInfo Technologies LLC |
| Hosted endpoint | `https://api.coresignal.com/cdapi` | `https://api.zoominfo.com/gtm` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | none | Proprietary service under ZoomInfo's Licence Terms and Conditions. The GTM CLI on GitHub is MIT |
| Tools exposed | 5 | 26 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `com.coresignal/mcp` | not listed |
| Last release | 2026-08-07 | 2026-10-02 |
| Terms last updated | 2022-02-21 | no date given |
| Privacy policy last updated | 2026-08-25 | 2025-10-13 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 2 stars | 534 npm/wk |
| Agent reviews | 3.5/5 (2) | none |

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

**ZoomInfo API + MCP.** Search, lookup and similar-record calls cost no credits, and a free account with 1,000 data and 1,000 AI credits needs no card. OAuth carries 20 scopes and limits are published per package. The Licence Terms and Conditions bar disclosing benchmark results, and the two documentation sites disagree on batch sizes and rate-limit headers.

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

### ZoomInfo API + MCP

1. Call Lookup first and pass the returned IDs to Search. Unknown industry, metro or topic strings are rejected with a 422
2. Search before Enrich. Search is free, and each newly enriched record costs one data credit
3. Request only the scopes the task needs in the `scope` parameter of the token call. Omitting it grants every scope configured on the app
4. On 429 read `X-RateLimit-Rejected-Bucket` and wait for `Retry-After`. An exhausted hourly window can mean a wait of several hundred seconds
5. Turn off model training in the AI client before connecting the MCP server. ZoomInfo prohibits MCP data being used for training

## Questions

### Which is better for AI agents, Coresignal API + MCP or ZoomInfo API + MCP?

ZoomInfo API + MCP scores 72.2 (BB) on agent readiness against Coresignal API + MCP's 62.9 (B), and leads in 4 of 7 scored categories. Coresignal API + MCP leads on maintenance & community.

### Do Coresignal API + MCP and ZoomInfo API + MCP need an API key?

Coresignal API + MCP takes an API key or an OAuth sign-in. ZoomInfo API + MCP uses an OAuth sign-in.

### Can an agent call Coresignal API + MCP and ZoomInfo API + MCP without installing anything?

Yes. Coresignal API + MCP has a hosted endpoint at https://api.coresignal.com/cdapi and ZoomInfo API + MCP at https://api.zoominfo.com/gtm.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/coresignal-vs-zoominfo.json, and with the fewest tokens: https://www.anchorterminal.com/compare/coresignal-vs-zoominfo.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "coresignal", "b": "zoominfo"}`. From a terminal: `anchor compare coresignal zoominfo`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/coresignal.json and https://www.anchorterminal.com/api/v1/tools/zoominfo.json

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

- [Apollo API + MCP vs Coresignal API + MCP](https://www.anchorterminal.com/compare/apollo-vs-coresignal.md)
- [Apollo API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/apollo-vs-zoominfo.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 Fuse MCP](https://www.anchorterminal.com/compare/coresignal-vs-fuse-mcp.md)
- [Coresignal API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/coresignal-vs-gojiberry.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 People Data Labs](https://www.anchorterminal.com/compare/coresignal-vs-people-data-labs.md)
- [Coresignal API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-prospeo.md)
- [Crustdata API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-zoominfo.md)
- [Enrich Layer API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/enrich-layer-vs-zoominfo.md)
- [FullEnrich API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-zoominfo.md)
- [Fuse MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/fuse-mcp-vs-zoominfo.md)
- [Gojiberry vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/gojiberry-vs-zoominfo.md)
- [Hunter API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/hunter-vs-zoominfo.md)
- [LeadMagic API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/leadmagic-vs-zoominfo.md)
- [Lusha API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/lusha-vs-zoominfo.md)
- [People Data Labs vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/people-data-labs-vs-zoominfo.md)
- [Prospeo API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/prospeo-vs-zoominfo.md)
- [Coresignal API + MCP vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-dropcontact.md)
- [Dropcontact API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-zoominfo.md)