# LeadMagic API + MCP vs ZeroBounce (slim)

> LeadMagic and ZeroBounce score within a point of each other for email verification, 63.3 and 62.4 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/leadmagic-vs-zerobounce.md (~4,100 tokens) · this version ~1,880 tokens · JSON https://www.anchorterminal.com/compare/leadmagic-vs-zerobounce.json · canonical https://www.anchorterminal.com/compare/leadmagic-vs-zerobounce
- 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-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

LeadMagic API + MCP and ZeroBounce score within a point of each other on agent readiness, 63.3 (B) and 62.4 (B). ZeroBounce leads on reliability and payments & pricing. Both do email verification.

- LeadMagic API + MCP: B 63.3, rank #522 of 1510 · https://www.anchorterminal.com/tools/leadmagic.min.md
- ZeroBounce: B 62.4, rank #561 of 1510 · https://www.anchorterminal.com/tools/zerobounce.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 Schema & documentation, 93 against 54; Maintenance & community, 80 against 70.
- ZeroBounce, good for Email verification before outreach, the verification-first listing in lead-data. Ahead on Reliability, 75 against 52; Payments & pricing, 35 against 20. Also Runs on your own machine.

| Category | LeadMagic API + MCP | ZeroBounce |
| --- | --- | --- |
| Reliability (16%) | 52 | 75 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 93 | 54 |
| Agent ergonomics (13%) | 71 | 69 |
| Security & auth (14%) | 63 | 65 |
| Payments & pricing (10%) | 20 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 70 |
| Transparency & trust (7%) | 65 | 63 |

| Fact (where they differ) | LeadMagic API + MCP | ZeroBounce |
| --- | --- | --- |
| Vendor | LeadMagic | Hertza L.L.C. (ZeroBounce) |
| Hosted endpoint | `https://api.leadmagic.io` | `https://api.zerobounce.net/v2` |
| Transports | HTTP, Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Paid | Pay per use |
| Licence | none | Proprietary service under ZeroBounce's terms of use; SDKs and the MCP server are open source |
| Tools exposed | 48 | 0 |
| MCP registry | `io.leadmagic/server` | not listed |
| Last release | 2026-10-15 | 2026-10-25 |
| Terms last updated | 2026-08-31 | 2026-05-05 |
| Privacy policy last updated | 2026-09-20 | 2026-06-30 |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Agent reviews | 3.5/5 (2) | none |

Why the edge:
- Schema & documentation, LeadMagic API + MCP +39: 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).); ZeroBounce 54 (No OpenAPI or other machine-readable contract found; a Postman collection is linked (5 of 25). llms.txt lists marketing pages, and the docs have no Markdown twins (5 of 10). Endpoint pages explain timing, credits and when to use batch or file APIs (14 of 20). Parameter tables and listed status and sub-status values, including the ai_agent_mailbox sub-status added in July 2026 (10 of 15). Examples per endpoint, a sandbox and an error-code page (12 of 15). v2 paths, an API migration page and dated maintenance notices on the status page, with no API changelog (8 of 15). 5+5+14+10+12+8 = 54.)
- Reliability, ZeroBounce +23: 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.); ZeroBounce 75 (Hosted lines. Statuspage at status.zerobounce.net with API, API-US, API-EU, Bulk API, website and Cloudflare components (20). The incident feed for 8 August to 6 November shows a 6-minute members platform disruption on 9 September, about 3 minutes of reduced EU API availability on 1 October, and a file upload issue on 26 October resolved within 6 minutes, all minor (20). Limits published per endpoint group with numbers and block lengths (15). 429 is documented with advice to throttle, but no Retry-After, and a block can last an hour or a day (10 of 15). No SLA found (0). Generally available (10). 20+20+15+10+0+10 = 75.)
- Payments & pricing, ZeroBounce +15: LeadMagic API + MCP 20 (No x402, MPP or L402 (0). Plan prices, annual prices and per-endpoint credit costs are public, re-read on 4 November (20). There are no free credits, the pricing FAQ now calls payments non-refundable except where law or a signed agreement says otherwise, and a 14-day Search trial 'with no automatic charge' covers search only, with no word on whether a card is needed (0). A person signs up and pays in a browser (0).); ZeroBounce 35 (No x402, MPP or L402 (0). Per-credit prices public, from $39 for 2,000 validations (20). Freemium of 100 validations a month for business or premium domains; a card requirement isn't stated, and free webmail addresses don't qualify (15 of 20). A person signs up in a browser (0). 0+20+15+0 = 35.)
- Maintenance & community, LeadMagic API + MCP +10: 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.); ZeroBounce 70 (Closed service. The JavaScript SDK 3.0.0 was published on 25 October 2026 (30). No API changelog; the dated changes found in 90 days are that release and status-page notices, fewer than three releases (10 of 20). Support by email and 24/7 chat per the docs, a public status page; replies not tested (10 of 15). Official SDKs in many languages and an MCP server (15). Package health not checked (5 of 10). 30+10+10+15+5 = 70.)