PingValid Email Validation vs BillionVerify
PingValid Email Validation is an MCP server published by pingvalid.com. Marketplaces we read that list it: 1 (Official MCP Registry). BillionVerify is an MCP server published by BillionVerify. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  PingValid Email Validation |  BillionVerify |
|---|---|---|
| Official MCP Registry | Listed Version: 0.4.3 No figure published Not marked · First seen |
Listed Version: 1.1.1 Downloads/month (npm): 259 Downloads/week (npm): 17 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | PingValid Email Validation | BillionVerify |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | 2026-10-18 | Not published |
| Where it runs (differs) | Remote server (pingvalid.com/mcp) | Remote server (mcp.billionverify.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/billionverify/billionverify-mcp |
| Changes in the last 7 days (differs) | 4 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
| Endpoint at the last check (differs) | Responded 3 days ago | Responded 33 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
PingValid Email Validation
Email validation for AI assistants: verdict, risk score, evidence. Free: 100 checks a month.
BillionVerify
Email verification for AI agents: verify single or bulk emails, check credits and history.
How to run each
PingValid Email Validation As a remote MCP server
claude mcp add --transport http pingvalid-email-validation https://pingvalid.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
BillionVerify As a remote MCP server
claude mcp add --transport http billionverify-mcp https://mcp.billionverify.com/mcpRequires: BILLIONVERIFY_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of PingValid Email Validation publish no settings it asks for, so we do not compare settings.
What it can do: PingValid Email Validation · What it can do: BillionVerify · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.