MyEmailVerifier MCP Connector

Real-time email verification for Claude

This is a remote Model Context Protocol server that lets Claude verify email deliverability using your MyEmailVerifier account.

Connector URL

https://mcp.myemailverifier.com/mcp

Connect it

In Claude, open Settings → Connectors → Add custom connector.
Paste the connector URL above and click Add.
Click Connect. You will be sent to a MyEmailVerifier authorization page.
Enter your API key (find it in your dashboard) and authorize.

Tools

Name	Title	Description
`verify_email`	Verify Email Address	Verify a single email address with MyEmailVerifier. Performs syntax, domain, MX and live SMTP mailbox checks, and reports whether the address is safe to send to, plus disposable, role-based, catch-all, free-provider and greylisting flags. Consumes one verification credit from the connected account.
`verify_email_batch`	Verify Email Addresses (Batch)	Verify up to 10 email addresses in one call and return a per-address verdict plus a summary count of how many are safe to send to. Consumes one verification credit per address.
`get_credit_balance`	Check Credit Balance	Return the number of email verification credits remaining on the connected MyEmailVerifier account. Consumes no credits.

All tools are read-only and non-destructive. Each address verified consumes one credit.

Example prompts

“Verify the email address [email protected]”
“Which of these addresses are safe to send to: [email protected], [email protected], [email protected]?”
“How many verification credits do I have left?”

Technical details

Transport	MCP Streamable HTTP (JSON responses)
Protocol versions	2025-06-18, 2025-03-26, 2024-11-05
Authorization	OAuth 2.1 + PKCE (S256), dynamic client registration, rotating refresh tokens
Resource metadata	`/.well-known/oauth-protected-resource`
Server metadata	`/.well-known/oauth-authorization-server`
Rate limit	120 requests / minute

Privacy

This connector stores nothing. Email addresses are passed straight to the MyEmailVerifier API and are not logged or retained. Your API key is encrypted into the access token itself and never written to disk or a database. See the privacy policy.