Mailvett: Email Validation API for AI Agents vs emailverifier.dev
Mailvett: Email Validation API for AI Agents is an MCP server published by cybermax.cybermax-tools.workers.dev. Marketplaces we read that list it: 1 (Official MCP Registry). emailverifier.dev is an MCP server published by usamaejaz. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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 |  Mailvett: Email Validation API for AI Agents | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 No figure published Not marked · First seen |
Listed Version: 1.0.0 No figure published 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 | Mailvett: Email Validation API for AI Agents | emailverifier.dev |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mailvett.cybermaxtools.com/mcp) | Remote server (emailverifier.dev/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/usamaejaz/emailverifier.dev |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 38 h ago returned HTTP 200 | Responded 27 h ago, requires authentication |
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
Mailvett: Email Validation API for AI Agents
Mailvett: validate emails. MX, provider, disposable/role/free flags, typo fix, verdict.
emailverifier.dev
Verify emails and domains for routing, disposable providers, role accounts, and SMTP risk.
How to run each
Mailvett: Email Validation API for AI Agents
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: x-api-key header
emailverifier.dev As a remote MCP server
claude mcp add --transport http emailverifier https://emailverifier.dev/mcpCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: Mailvett: Email Validation API for AI Agents · What it can do: emailverifier.dev · 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.