Verify email deliverability directly inside Claude. Connect your MyEmailVerifier account once, then ask Claude to check addresses in plain language — no copying lists between tools.
✉ Get Your Free API KeyThree read-only tools for reliable email verification, directly inside Claude.
Syntax, domain, MX and live SMTP mailbox checks, plus disposable, role-based, catch-all, free-provider and greylisting flags.
Verify up to 10 email addresses in a single tool call, with a per-address verdict and a summary of how many are safe to send to.
Ask Claude how many verification credits remain on your account at any time. This tool is free and uses no credits.
Dynamic client registration and rotating refresh tokens. Claude uses your own API key — no shared credentials, no key exposure.
Add the connector in five simple steps — no coding required.
In Claude, open Settings → Connectors → Add custom connector
Paste https://mcp.myemailverifier.com/mcp and click Add
You will be taken to a MyEmailVerifier authorization page.
Enter the API key from your dashboard.
Click Authorize & Connect. Claude now has access to the email verification tools.
Three MCP tools are exposed to Claude once the connector is authorized. All three are read-only — none of them modify or delete anything in your account.
Input
{ "email": "[email protected]" }
Example Output
Input
{ "emails": [ "[email protected]", "[email protected]", "invalid@fake" ] }
Returns a per-address verdict in the same detailed format as verify_email, plus a summary of how many are safe to send to.
Check how many verification credits remain on your account. Takes no input parameters.
Example Output
Just type naturally — Claude knows when to call the verification tool.
"Verify the email address [email protected]"
"Which of these are safe to send marketing email to: [email protected], [email protected], [email protected]?"
"How many verification credits do I have left?"
"Check this list and tell me which ones are disposable addresses"
This connector uses OAuth 2.1 with PKCE (S256), dynamic client registration and rotating refresh tokens. Each user authenticates with their own MyEmailVerifier API key — the server never stores credentials permanently. Access tokens last 1 hour, alongside a 30-day refresh token that is rotated on every use.
| Endpoint | URL | Purpose |
|---|---|---|
| Authorization | https://mcp.myemailverifier.com/authorize |
Redirect user to login & consent |
| Token | https://mcp.myemailverifier.com/token |
Exchange code for Bearer token |
| MCP | https://mcp.myemailverifier.com/mcp |
Streamable HTTP — tool execution endpoint |
2025-06-18 (also supports 2025-03-26 and 2024-11-05).
Every value below reflects the live server configuration.
| Item | Value |
|---|---|
| Transport | MCP Streamable HTTP |
| Protocol version | 2025-06-18 (also supports 2025-03-26 and 2024-11-05) |
| Authorization | OAuth 2.1 with PKCE (S256) |
| Client registration | Dynamic, RFC 7591 |
| Discovery | RFC 9728 protected resource metadata, RFC 8414 server metadata |
| Access token | 1 hour |
| Refresh token | 30 days, rotated on every use |
| Rate limit — tools | 120 requests per minute |
| Rate limit — authorization | 20 requests per 15 minutes |
| Transport security | TLS throughout (Cloudflare + Apache) |
| Status | https://mcp.myemailverifier.com/health |
Limits are applied per IP address to ensure fair usage and service stability.
| Endpoint | Limit | Window |
|---|---|---|
| MCP tool calls | 120 requests | per minute |
| Authorization endpoints | 20 requests | per 15 minutes |
Designed with privacy-first principles — no data retained beyond what is needed.
plain method is rejected.All verification data is subject to the MyEmailVerifier Privacy Policy.
To evaluate the connector, sign up for a free account at myemailverifier.com — free accounts include verification credits with no credit card required.
Reach out through any of the channels below.