Give it an address, get a VALID / RISKY / INVALID verdict with a deliverability score — combining live MX/SMTP checks with disposable, role-based and catch-all detection that plain regex validators miss.
| ✉️ Syntax | RFC-shaped local@domain, length limits, and typos like gmial.com / hotmial.com |
| 📮 MX (live) | does the domain have mail servers — i.e. can it receive mail at all (live DNS) |
| 🗑️ Disposable | hundreds of temp-mail / throwaway providers (mailinator.com, 10minutemail, temp-mail, Guerrilla Mail …) |
| 👥 Role-based | shared mailboxes (info@, admin@, support@) that hurt deliverability |
| 🎯 SMTP mailbox | deep: live RCPT-TO probe of the real mail server — does the specific inbox exist? No email is ever sent. Plus catch-all detection. |
GET /verify?email=jane@example.com GET /verify?email=foo@mailinator.com # → RISKY, disposable GET /verify?email=jane@gmial.com # → RISKY, domain typo
Try it: /verify?email=jane@example.com · /verify?email=foo@mailinator.com
{
"mcpServers": {
"email-verify": { "command": "npx", "args": ["-y", "mailbox-verify-mcp"] }
}
}Or connect over HTTP at POST /mcp. Tools: verify_email, verify_many.
The /pro/* routes are gated by x402. Your agent pays $0.05 USDC per call automatically — no sign-up, no API key. The paid tier runs the live SMTP mailbox probe. Settles on-chain to the operator wallet.
GET /pro/verify?email=<addr> # 402 → pay → deep result GET /pro/verify_many?emails=... # up to 50 addresses