# LeadMagic API + MCP vs Retriever (slim)

> LeadMagic scores 64.5 (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/leadmagic-vs-retriever.md (~4,650 tokens) · this version ~1,030 tokens · JSON https://www.anchorterminal.com/compare/leadmagic-vs-retriever.json · canonical https://www.anchorterminal.com/compare/leadmagic-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)

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.

- LeadMagic API + MCP: B 64.5, rank #585 of 1557 · https://www.anchorterminal.com/tools/leadmagic.min.md
- Retriever: F 32, rank #1455 of 1557 · https://www.anchorterminal.com/tools/retriever.min.md
- LeadMagic API + MCP, good 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 No incidents deducted, where Retriever loses 15 points for them.
- Retriever, good for A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.

| Category | LeadMagic API + MCP | Retriever |
| --- | --- | --- |
| Reliability (16%) | 52 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 93 | 82 |
| Agent ergonomics (13%) | 71 | 75 |
| Security & auth (14%) | 63 | 23 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 5 |
| Transparency & trust (7%) | 65 | 49 |

| Fact (where they differ) | LeadMagic API + MCP | Retriever |
| --- | --- | --- |
| Vendor | LeadMagic | Retriever |
| Hosted endpoint | `https://api.leadmagic.io` | `https://api.retriever.run/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Tools exposed | 48 | 67 |
| Read-only variant documented | no | 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 |
| 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 |

Why the edge:
- 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…); 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, LeadMagic API + MCP +40: LeadMagic API + MCP 63 (REST keys prefixed `lm_` in the `X-API-Key` header.); 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, LeadMagic API + MCP +16: LeadMagic API + MCP 65 (Closed service with terms naming Lead Magic Corporation, Massachusetts (15).); Retriever 49 (Closed source with clear terms, last updated 30 August 2026 (15).)
- Schema & documentation, LeadMagic API + MCP +11: LeadMagic API + MCP 93 (OpenAPI file at leadmagic.io/openapi.json, per the 30 September check (25).); Retriever 82 (OpenAPI 3.1 file, version 1.0.0, about 51 paths, linked from llms.txt (25).)
- 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 che…); Retriever 45 (No status page found, linked from neither the site nor the docs (0), so no incident history to read (5).)
