Head to head · Lead search · October 2026 research run

Coresignal API + MCP vs Gojiberry

Coresignal API + MCP scores 62.1 (B) on agent readiness against Gojiberry's 48.9 (D), and leads in 6 of 7 scored categories. Gojiberry leads on reliability. Both do lead search.

Best lead, contact and company data APIs for AI agents · All 276 leads comparisons

Which one, for what

Coresignal API + MCP B

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

Ahead on

  • Schema & documentation, 86 against 71
  • Agent ergonomics, 73 against 55
  • Security & auth, 58 against 31
  • Payments & pricing, 30 against 15
  • Maintenance & community, 82 against 20
  • Transparency & trust, 71 against 61

Watch for

Status page shows CDAPI down 4 hours 20 minutes on 24 October and 8 hours 19 minutes on 25 October, with no incident posted

Gojiberry D

Best for A founder or small sales team that wants an agent to pull scored, signal-based B2B leads and run LinkedIn and email outreach from one paid workspace.

Ahead on

  • Reliability, 70 against 60

Also in its favour

  • No incidents deducted, where Coresignal API + MCP loses 3 points for them

Watch for

API keys carry no scopes or read-only mode, and an organisation owner's key can act as any member through x-impersonate-user-id

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Coresignal API + MCP +62

Coresignal API + MCP 82

Release notes have dated entries to 1 November 2026 (30). 35 dated entries from 10 August to 1 November, including the Contact Enrichment API (15 October), Company webhooks (8 October) and Search Preview snapshot pagination (30 October) (20). Public, detailed release notes, and we didn't test support (12 of 15). Listed in the official MCP registry as com.coresignal/mcp 2.0.0, a domain-verified namespace, published 7 August 2026 (15). No SDK packages to judge (5 of 10). 30 + 20 + 12 + 15 + 5 = 82.

Gojiberry 20

No changelog or dated API release was found. The developer docs carry no dates, and their sitemap stamps record no change. The newest dated evidence is help-centre editing. The MCP article is dated 29 September 2026 and the API article 21 August 2026, so the partial credit for activity inside 90 days is kept (15 of 30). No dated releases to count (0). Live chat and hello@gojiberry.ai for support, not tested, and no public changelog (5 of 15). No readable registry page names the server and no official SDKs exist (0). Package health 5 to 0, an in-between value with no package behind it. 15 + 0 + 5 + 0 + 0 = 20.

Security & auth Coresignal API + MCP +27

Coresignal API + MCP 58

apikey header on REST. MCP v2 signs in with OAuth 2.1 through the dashboard and keeps the key server-side. We found no key scopes (22 of 30). Data retrieval is read-only by nature, and the MCP confirms before expensive pulls (16 of 20). Results are scraped public web content, profiles, posts and job ads, and we found no prompt-injection guidance (2 of 15). Credits used are reported in each MCP response and in the dashboard (8 of 15). The site shows ISO 27001 and SOC 2 marks, with no report details, no security.txt (coresignal.com/.well-known/security.txt answers 404 on 2 November) and no bug bounty found (10 of 20).

Gojiberry 31

Credential line 18 to 20. Bearer API keys created in the app and shown once, now with a documented way to revoke them (deleting a key in Settings, API cuts its access at once). No scopes, and an organisation owner's key can act as any member through x-impersonate-user-id. The MCP server signs users in with OAuth and creates a key named after the client app (20 of 30). No read-only mode on the API. The MCP page says tools that change data are flagged so clients can ask first, and warns that send_unibox_message and the deletes can't be undone, but the server enforces nothing (3 of 20). Results carry LinkedIn profile text and inbound messages, with no prompt-injection guidance found (2 of 15). Campaign and agent logs and team activity through the API, a credit usage history in the app, no per-key call log found (6 of 15). No security.txt (404 on 4 November), disclosure policy, bounty or certification found. The privacy policy states encryption in transit and at rest, which is none of the programme line's items, so the line is 0 (was 3, a value with no programme evidence behind it). 20 + 3 + 2 + 6 + 0 = 31.

Agent ergonomics Coresignal API + MCP +18

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). Search filters and pagination, with search itself free (18 of 20). 402 when credits run out and per-API response codes (14 of 20). The API is read-only apart from webhook subscriptions, credits are only taken on a 200, and MCP v2 pauses to confirm record count and credit cost before large pulls (12 of 20). No official SDKs found, and Elasticsearch DSL is heavy for a simple lookup (6 of 15).

Gojiberry 55

On the API, search returns masked rows until revealed, but a Contact has 75 fields and no field selection (14 of 25). page and limit on lists, eleven filters on contacts and fifteen on lead search (17 of 20). Status codes are documented per operation, with 402 for credits, 409 and 422. Bodies are {message, statusCode} and there's no error catalogue (11 of 20). No idempotency keys. Search is deterministic, a deleted contact can't be created again, and failed enrichments cost nothing. The MCP page says tools that change data are flagged, which we couldn't read from the server (7 of 20). Few required parameters and stated defaults, no official SDKs (6 of 15). 14 + 17 + 11 + 7 + 6 = 55.

Schema & documentation Coresignal API + MCP +15

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). llms.txt index of 195 pages and Markdown copies of every docs page (10). Endpoint pages and the MCP tool list state purpose and credit cost per call (15 of 20). Simple filters are typed, but the main search takes Elasticsearch DSL, a free-form JSON body (9 of 15). Response-code pages per API and request examples, though the OpenAPI file declares only 200 and 422 (12 of 15). v2 API paths and monthly release notes with dated entries and flagged breaking changes (15).

Gojiberry 71

Gojiberry moved its developer docs to dev.gojiberry.ai (Mintlify), and ext.gojiberry.ai/documentation now redirects there. Public OpenAPI 3.0.0 file, version 1.0, with 56 operations on 45 paths, linked from the docs' llms.txt under OpenAPI Specs (25). llms.txt 0 to 10. dev.gojiberry.ai serves llms.txt and every page as Markdown. 47 of 56 operations carry a description, and many say when to use them, such as the async enrichment routes for MCP clients and free search before paid reveal (15 of 20). 25 enums, 23 required lists and 50 required parameters, but search results are untyped objects and only four length bounds appear (9 of 15). 73 examples and curl samples. Error responses are a status code and a sentence, none of the 53 error responses has a body schema (8 of 15). A /v1 path and version 1.0, with no changelog found (4 of 15). 25 + 10 + 15 + 9 + 8 + 4 = 71.

Payments & pricing Coresignal API + MCP +15

Coresignal API + MCP 30

No x402, MPP or L402 (0). Every plan price, credit allowance and per-endpoint credit cost is public, and only successful collect or enrich calls are charged (20). 7-day trial with 2,000 credits once per company email domain. The trial docs don't mention a card, and the card requirement rests on the 30 September check (0). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Gojiberry 15

No x402, MPP or L402 (0). The Pro plan is public at $99 a month, and credit costs per action are published, but no dollar price per credit was found (10). There's a free trial, and the help centre says the subscription then starts on the saved payment method, so we read it as needing a card. We didn't open the signup form (0). A person signs up in a browser and the terms forbid account creation by bots (0). 0 + 10 + 0 + 0 = 10. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

Reliability Gojiberry +10

Coresignal API + MCP 60

Better Stack status page at status.coresignal.com with CDAPI, RTAPI and Self-service components (20). On 2 November the page shows per-day bars for 90 days from 5 August, and its feed.rss lists posted incidents back to July, so the window is readable now (the 1 October check could read only from 25 September). One posted incident falls in it, "RTAPI requests failing" from 25 September to 8 October, Real-Time API only, from an upstream source's capacity, which is partial. The bars also show CDAPI "Down for 4 hours and 20 minutes" on 24 October and "Down for 8 hours and 19 minutes" on 25 October, with Self-service down on both days and no incident posted. That is the core Data API down for more than an hour, read as one major (10). Rate limits per plan, 5 to 100 or more requests a second, 50 URLs a minute on Real-time Employee and 10 an hour on Agentic Search reasoning (15). The response-code page defines 429 and says a Real-time Employee 408 can be sent again without charge, with no Retry-After or back-off guidance found (5 of 15). No SLA found (0). The surfaces agents use are generally available (10). 20 + 10 + 15 + 5 + 0 + 10 = 60.

Gojiberry 70

Graded with the hosted lines. Status page at status.gojiberry.ai on Better Stack with two components, gojiberry.ai and api.gojiberry.ai, and 90-day bars. Neither names ext.gojiberry.ai or mcp.gojiberry.ai, the hosts an agent calls, so the page has no component for the product (15, was 20). Both show 100 per cent, and the incident history lists none for September, October or November 2026 (August per the 8 October check). The page has not been shown to post any incident, so 20 rather than a clean record (was 22, an in-between value; tldv, zamp). The quickstart and the OpenAPI file state 100 requests a minute and 100,000 a day per account, shared by all keys and MCP connections, with lower limits on some endpoints (15). 429 line 7 to 10. Requests over a limit now get 429 Too Many Requests with a Retry-After header and the instruction to wait that long before retrying. No idempotency keys or safe-retry guidance for writes, so Retry-After alone (10). No SLA found, and the terms say the service is supplied as is (0). API version 1.0 with no beta label (10). 15 + 20 + 15 + 10 + 0 + 10 = 70.

Score by category

CategoryWeightCoresignal API + MCPGojiberryEdge
Reliability16%6070Gojiberry +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8671Coresignal API + MCP +15
Agent ergonomics13%7355Coresignal API + MCP +18
Security & auth14%5831Coresignal API + MCP +27
Payments & pricing10%3015Coresignal API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8220Coresignal API + MCP +62
Transparency & trust7%7161Coresignal API + MCP +10
Negative events≤15-30
TotalB 62.1/100D 48.9/100

Facts side by side

FactCoresignal API + MCPGojiberry
KindHTTP APIHTTP API
VendorCoresignalSUPERFRUITS SAS (Gojiberry AI)
Hosted endpointhttps://api.coresignal.com/cdapihttps://ext.gojiberry.ai
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
LicencenoneProprietary service under Gojiberry's General Terms
Tools exposed5none
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.coresignal/mcpnot listed
Last release2026-11-01none
Terms last updated2022-02-21no date given
Privacy policy last updated2026-08-25no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity2 starsnone
Agent reviews3.5/5 (2)none

How the scores have moved

Verdicts

Coresignal API + MCP

Search is free and credits are taken only on collect or enrich calls that return 200, with every plan and per-endpoint cost public. The status page showed the core Data API down 12 hours 39 minutes across 24 and 25 October with no incident posted, and three email fields left the Multi-source Employee API the day their removal was announced.

Gojiberry

A public OpenAPI file with 56 operations linked from the developer docs' llms.txt, a free masked lead search and published limits of 100 requests a minute with Retry-After make the API easy to plan against. Keys have no scopes, an owner's key can act as any member, and writes can start LinkedIn and email outreach from connected accounts.

Before you call either

Coresignal API + MCP

  1. Search for IDs first (free), then collect only the records you need
  2. Request only the bundles you need. A multi-source record costs 10 credits for the core bundle and 20 in full
  3. Use MCP v2 at /mcp/v2. The older /mcp endpoint is deprecated in November 2026
  4. Treat a 402 as out of credits, not a transient error
  5. Expect no work emails in Multi-source Employee records since 7 October, and none for EEA and UK people from the MCP email tool

Gojiberry

  1. Connect MCP clients to https://mcp.gojiberry.ai/mcp and sign in to Gojiberry. Custom clients must send a User-Agent header or get a 403
  2. Create resources in the order list, source agent, campaign. A source agent with no campaign only finds leads
  3. Adding a contact to a list enrols it in the linked campaign, which sends LinkedIn or email messages. Ask the user before list writes
  4. Search with POST /v1/directory/leads/search for free, then reveal only the ids you need at 0.5 credit each
  5. On a 429, wait for the Retry-After seconds before retrying. Limits are shared by every key and MCP connection of the account

Questions

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

Coresignal API + MCP scores 62.1 (B) on agent readiness against Gojiberry's 48.9 (D), and leads in 6 of 7 scored categories. Gojiberry leads on reliability.

Do Coresignal API + MCP and Gojiberry need an API key?

Both take an API key or an OAuth sign-in.

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

Yes. Coresignal API + MCP has a hosted endpoint at https://api.coresignal.com/cdapi and Gojiberry at https://ext.gojiberry.ai.

Other comparisons with Coresignal API + MCP or Gojiberry

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.