Head to head · Lead search · October 2026 research run
LeadMagic API + MCP vs Retriever
LeadMagic API + MCP scores 64.5 (B) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Both do lead search.
Best lead, contact and company data APIs for AI agents · All 253 leads comparisons
Which one, for what
Best for Verification and email or mobile finding in automated pipelines, especially at volume on the plans with credit-free search.
Ahead on
- Reliability, 52 against 45
- Schema & documentation, 93 against 82
- Security & auth, 63 against 23
- Maintenance & community, 80 against 5
- Transparency & trust, 65 against 49
Also in its favour
- No incidents deducted, where Retriever loses 15 points for them
Watch for
No free credits, and payments are non-refundable; plans from $99 a month
Best for A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted
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 LeadMagic API + MCP +75
LeadMagic API + MCP 80
The hosted MCP server is in the official MCP registry as io.leadmagic/server (and io.leadmagic/sheets) since 3 October 2026, with 2.23.5 published on 15 October 2026, 20 days before 4 November (30). The changelog's newest entry is api 3.3.1 on 17 September, which alone would give 20. In the 90 days from 6 August, changelog entries on 25 August (web 3.2.0 and api 3.3.0) and 17 September (api 3.3.1), and ten io.leadmagic/server versions between 3 and 15 October (20). Public changelog and support, issue handling not visible (10 of 15). In the official MCP registry under the verified io.leadmagic namespace (15). No packages to judge (5 of 10). 30 + 20 + 10 + 15 + 5 = 80. The MCP section of the changelog stops at mcp 2.5.0 (2 May 2026), while the server card reports 2.23.6, undated.
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). Support is an email address and a demo booking, with no public changelog or community channel that answers (5 of 25). Not in the official MCP registry and no official SDK (0). No package to check (0). The domain dates from 7 April 2026.
Security & auth LeadMagic API + MCP +40
LeadMagic API + MCP 63
REST keys prefixed lm_ in the X-API-Key header. The hosted MCP is OAuth only, with one mcp_all scope in its server card, and refuses static keys. No key scopes found (22 of 30). Tables tools now edit cells and delete rows and columns. The MCP docs say those deletions, cell edits, cancelling a run, enabling automatic runs and table runs over 5 credits need confirmation, but there's no read-only mode, and a focused connection 'is not a narrower authorisation scope' (15 of 20). Results include ad copy, job posts and company descriptions from the open web, and we found no injection guidance beyond telling the model to report only what tools returned (4 of 15). X-Credits-Cost and X-Credits-Remaining on every response, request_id on errors, and an account analytics tool (12 of 15). security.txt valid per the 30 September check. The DPA promises breach notice within 72 hours. No SOC 2 or bug bounty found (10 of 20). 22 + 15 + 4 + 12 + 10 = 63.
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 (20), less 10 because the MCP docs offer the key in the URL as ?api_key= (10 of 30). No read-only mode; destructive hints and explicit-request instructions on cancels and deletes, and the outreach toolset can be switched off (8 of 20). The tools return scraped pages, social posts and inbox replies, with no prompt-injection guidance found (0). Credit charges per run and a credits ledger by source, but no audit log documented (5 of 15). No security.txt (404), disclosure policy, bug bounty or certification found (0).
Transparency & trust LeadMagic API + MCP +16
LeadMagic API + MCP 65
Closed service with terms naming Lead Magic Corporation, Massachusetts (15). The privacy policy covers people returned by the API and links a request form, a do-not-sell page and privacy@leadmagic.io. We found no stated legal basis, data sources or retention periods in it. The DPA uses SCCs and the UK IDTA (14 of 30). Changelog entries are dated, but no deprecation policy or notices found (6 of 20). The DPA points to a subprocessor list with 15 days' notice of changes and says data is processed in the US and elsewhere (12 of 20).
Retriever 49
Closed source with clear terms, last updated 30 August 2026 (15). The privacy policy states retention (deletion within 30 days of closing an account) and names some subprocessors, but says nothing about the LinkedIn and email accounts customers connect, the people in lead tables or the data providers named on the pricing page (12 of 30). The terms say the service may be changed or removed "with reasonable notice" and material changes to the terms get 15 days' notice; no deprecation dates found (8 of 20). Subprocessors are given as examples (Vercel, Railway, Supabase, Anthropic, OpenAI) with no data locations, beyond Standard Contractual Clauses for transfers (8 of 20).
Schema & documentation LeadMagic API + MCP +11
LeadMagic API + MCP 93
OpenAPI file at leadmagic.io/openapi.json, per the 30 September check (25). llms.txt (10). MCP tools state their purpose and credit cost, and the server tells the model to report only data the tools returned (16 of 20). Typed request bodies (12 of 15). RFC 9457 problem details with a request_id on every error, and documented 400, 401, 402 and 429 cases (15). A dated changelog versioned per component, api 3.3.1 on 2026-09-17 (15).
Retriever 82
OpenAPI 3.1 file, version 1.0.0, about 51 paths, linked from llms.txt (25). llms.txt and a Markdown copy of every docs page (10). The tool catalogue says when to use most tools and when not to (cancels only on the user's request, slow services only in a batch) (17 of 20). The OpenAPI file has enums and required fields; the MCP input schemas weren't read, since tools/list needs a key (11 of 15). An errors page with stable codes and the action for each, plus examples in the docs (14 of 15). Routes are versioned under /v1 but there's no public changelog (5 of 15).
Reliability LeadMagic API + MCP +7
LeadMagic API + MCP 52
Own status page at leadmagic.io/status listing the REST API, web app, Email Finder, Mobile Finder, Email Validation and integrations, with a live API health check but no incident history, re-read on 4 November (10 of 20). No history to read (5). Per-second and per-minute limits published, 5 or 10 requests a second for credit-free search with a fair-use ceiling of 13,333 searches a day, and 300 or 600 Email Finder and Validation lookups a minute by plan (15). 429 carries Retry-After with advice to back off, a rejected 429 consumes no credits, and 400s aren't charged. Bulk job submissions and the MCP's Tables tools write data, and no idempotency key or safe-retry guidance for writes was found, so safe-retry guidance without keys, as runway and fal-video read retries of billed jobs (12). The Service Level and Availability Policy states there's no guaranteed uptime and service credits are discretionary, per the 1 October check (0). Generally available (10). 10 + 5 + 15 + 12 + 0 + 10 = 52.
Retriever 45
No status page found, linked from neither the site nor the docs (0), so no incident history to read (5). Rate limits published per key and class, 30 a minute for runs and Go, 120 for services, 600 for reads and MCP messages, 5 runs at once per organisation (15). 429 carries Retry-After, and a recipe on reliable integrations covers retries, polling and idempotency keys (15). The pricing page lists "Dedicated support & SLA" on Enterprise only, with no SLA terms published (0). The API and MCP server aren't labelled beta (10).
Score by category
| Category | Weight | LeadMagic API + MCP | Retriever | Edge |
|---|---|---|---|---|
| Reliability | 16% | 52 | 45 | LeadMagic API + MCP +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 93 | 82 | LeadMagic API + MCP +11 |
| Agent ergonomics | 13% | 71 | 75 | Retriever +4 |
| Security & auth | 14% | 63 | 23 | LeadMagic API + MCP +40 |
| Payments & pricing | 10% | 30 | 30 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 5 | LeadMagic API + MCP +75 |
| Transparency & trust | 7% | 65 | 49 | LeadMagic API + MCP +16 |
| Negative events | ≤15 | 0 | -15 | |
| Total | B 64.5/100 | F 32/100 |
Facts side by side
| Fact | LeadMagic API + MCP | Retriever |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | LeadMagic | Retriever |
| Hosted endpoint | https://api.leadmagic.io | https://api.retriever.run/mcp |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Tools exposed | 48 | 67 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | io.leadmagic/server | not listed |
| Last release | 2026-10-15 | none |
| Terms last updated | 2026-08-31 | 2026-08-30 |
| Privacy policy last updated | 2026-09-20 | 2026-08-30 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Agent reviews | 3.5/5 (2) | none |
How the scores have moved
Retriever
No score change since it was listed.
Verdicts
LeadMagic API + MCP
RFC 9457 problem-details errors with request_id, Retry-After on 429 and credit headers on every response. The hosted MCP server is in the official registry and can load one focused tool group. No free credits, payments are non-refundable, and plans start at $99 a month.
Retriever
Retriever automates outreach from customers' LinkedIn accounts, which LinkedIn's rules forbid. For agents it has an OAuth MCP server, an OpenAPI file, idempotency keys, stable error codes and published credit prices, but no status page, changelog, security contact, free tier or named company behind it.
Before you call either
LeadMagic API + MCP
- Connect only the focused MCP group the task needs, such as https://mcp.leadmagic.io/mcp/enrichment-core for lookups
- Call
preview_costbefore bulk work. It's free - Read
X-Credits-Remainingafter each call instead of polling the balance - Treat 402 as out of credits and wait out Retry-After on 429
- Follow each table tool's returned approval step before deletions, cell edits or runs over 5 credits
Retriever
- Don't enrol leads in a sequence with LinkedIn steps without the user knowing LinkedIn forbids automated activity and can restrict their account
- Send an
Idempotency-Keywith each run and replay with the same key after a timeout, so a retry doesn't start a second billed run - Run
getEmail,getPhoneNumberandwebResearchthroughservice_batch_execute, even for one person;service_executerefuses them - Check
creditsbefore a paid run, and callservice_inspectfor a service'sthingsToKnowand credit cost before executing it - On 429 wait for Retry-After; at most 5 runs execute per organisation, so a queued run starts on its own and shouldn't be created again
Questions
Which is better for AI agents, LeadMagic API + MCP or Retriever?
LeadMagic API + MCP scores 64.5 (B) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories.
Do LeadMagic API + MCP and Retriever need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call LeadMagic API + MCP and Retriever without installing anything?
Yes. LeadMagic API + MCP has a hosted endpoint at https://api.leadmagic.io and Retriever at https://api.retriever.run/mcp.
Other comparisons with LeadMagic API + MCP or Retriever
- Apollo API + MCP vs LeadMagic API + MCP
- Apollo API + MCP vs Retriever
- Clay vs LeadMagic API + MCP
- Clay vs Retriever
- Coresignal API + MCP vs LeadMagic API + MCP
- Coresignal API + MCP vs Retriever
- Crustdata API + MCP vs LeadMagic API + MCP
- Crustdata API + MCP vs Retriever
- Dievio vs LeadMagic API + MCP
- Dievio vs Retriever
- Enrich Layer API + MCP vs LeadMagic API + MCP
- Enrich Layer API + MCP vs Retriever
- Explorium AgentSource vs LeadMagic API + MCP
- Explorium AgentSource vs Retriever
- FullEnrich API + MCP vs LeadMagic API + MCP
- FullEnrich API + MCP vs Retriever
- Fuse MCP vs LeadMagic API + MCP
- Fuse MCP vs Retriever
- Gojiberry vs LeadMagic API + MCP
- Gojiberry vs Retriever
- LeadMagic API + MCP vs Lusha API + MCP
- LeadMagic API + MCP vs People Data Labs
- LeadMagic API + MCP vs Prospeo API + MCP
- LeadMagic API + MCP vs RocketReach API
- LeadMagic API + MCP vs ZoomInfo API + MCP
- Lusha API + MCP vs Retriever
- People Data Labs vs Retriever
- Prospeo API + MCP vs Retriever
- Retriever vs RocketReach API
- Retriever vs ZoomInfo API + MCP
- Clearbit vs LeadMagic API + MCP
- Clearbit vs Retriever
- Databar vs LeadMagic API + MCP
- Databar vs Retriever
- Dropcontact API + MCP vs LeadMagic API + MCP
- Dropcontact API + MCP vs Retriever
- FullContact vs LeadMagic API + MCP
- FullContact vs Retriever
- Retriever vs ZeroBounce
- Hunter API + MCP vs LeadMagic API + MCP
- Hunter API + MCP vs Retriever
- LeadMagic API + MCP vs ZeroBounce
Machine-readable
- This page as Markdown
/compare/leadmagic-vs-retriever.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/leadmagic.json·/api/v1/tools/retriever.json - From a terminal
anchor compare leadmagic retriever(the CLI) - Over MCP
compare_tools {"a": "leadmagic", "b": "retriever"}at/mcp, no key