# LeadMagic API + MCP vs Leadsets (slim)

> LeadMagic scores 64.5 (B) to Leadsets's 62.9 (B) for lead search. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/leadmagic-vs-leadsets.md (~4,400 tokens) · this version ~980 tokens · JSON https://www.anchorterminal.com/compare/leadmagic-vs-leadsets.json · canonical https://www.anchorterminal.com/compare/leadmagic-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)

LeadMagic API + MCP scores 64.5 (B) on agent readiness against Leadsets's 62.9 (B), and leads in 2 of 7 scored categories. Leadsets leads on agent ergonomics and payments & pricing. Both do lead search.

- LeadMagic API + MCP: B 64.5, rank #588 of 1571 · https://www.anchorterminal.com/tools/leadmagic.min.md
- Leadsets: B 62.9, rank #661 of 1571 · https://www.anchorterminal.com/tools/leadsets.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 40; Schema & documentation, 93 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 71; Payments & pricing, 50 against 30. Also Free to start without a card.

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

| Fact (where they differ) | LeadMagic API + MCP | Leadsets |
| --- | --- | --- |
| Vendor | LeadMagic | Leadsets |
| Hosted endpoint | `https://api.leadmagic.io` | `https://mcp.leadsets.ai` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Pricing | Paid | Freemium |
| Tools exposed | 48 | 8 |
| MCP registry | `io.leadmagic/server` | `io.github.leadsets/leadsets` |
| Last release | 2026-10-15 | 2026-11-22 |
| Terms last updated | 2026-08-31 | 2026-11-15 |
| Privacy policy last updated | 2026-09-20 | 2026-11-19 |
| Terms restrict automated access | yes | not found in the text |
| 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:
- Schema & documentation, LeadMagic API + MCP +35: LeadMagic API + MCP 93 (OpenAPI file at leadmagic.io/openapi.json, per the 30 September check (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…)
- Payments & pricing, Leadsets +20: LeadMagic 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 +19: LeadMagic API + MCP 71 (The full hosted MCP connection carries every tool, which the docs now split into four focused connections (Tables 22, Tables setup 22, Data enrichment 27, Bulk…); 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…)
- Reliability, LeadMagic API + MCP +12: 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…); 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).)
