VerifyAnyEmail MCP Server
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@VerifyAnyEmail MCP Server Verify jane.doe@acme.com and tell me if it's safe to send"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
VerifyAnyEmail MCP Server
Official Model Context Protocol server for VerifyAnyEmail — give any AI agent real-time email verification and deliverability diagnostics.
Works with Claude Desktop, Claude Code, Cursor, Windsurf, ChatGPT (MCP connectors), and any other MCP client.
What it does
Tool | Description | Credits |
| Verify one address — verdict ( | 1 per call |
| Submit many addresses for async bulk verification; returns a | 1 per address |
| Poll a batch's progress and per-status counts. | free |
| Fetch a paginated page of batch results. | free |
| Domain MX records / can it receive mail. | free |
| SPF record + misconfiguration flags. | free |
| DMARC policy and alignment. | free |
| DKIM record for a selector. | free |
| Combined MX/SPF/DKIM/DMARC health grade with findings. | free |
The diagnostics are free (no verification credits). Verification spends credits — except test addresses
at test.verifyany.email (deliverable@, undeliverable@, risky@, unknown@), which return canned results
and cost 0 credits, perfect for trying it out.
Related MCP server: email-verify
Setup
You need a VerifyAnyEmail API key (vae_…) — create one in the dashboard → API Keys.
The server is distributed on npm and runs with npx (no install needed).
Claude Desktop
Edit claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": {
"verifyanyemail": {
"command": "npx",
"args": ["-y", "verifyanyemail-mcp"],
"env": { "VERIFYANYEMAIL_API_KEY": "vae_your_key_here" }
}
}
}Restart Claude Desktop. You'll see the VerifyAnyEmail tools available.
Claude Code
claude mcp add verifyanyemail -e VERIFYANYEMAIL_API_KEY=vae_your_key_here -- npx -y verifyanyemail-mcpCursor
Add to ~/.cursor/mcp.json (or a project .cursor/mcp.json):
{
"mcpServers": {
"verifyanyemail": {
"command": "npx",
"args": ["-y", "verifyanyemail-mcp"],
"env": { "VERIFYANYEMAIL_API_KEY": "vae_your_key_here" }
}
}
}Any other MCP client
Run the binary over stdio with the API key in the environment:
VERIFYANYEMAIL_API_KEY=vae_your_key_here npx -y verifyanyemail-mcpConfiguration
Env var | Required | Default | Purpose |
| ✅ | — | Your |
| — |
| Override the API base URL. |
| — |
| Per-request timeout in milliseconds. |
Example prompts
"Is
jane.doe@acme.coma real, safe-to-send address?""Verify these 500 signups and tell me which are risky." (uses
verify_batch)"Check the email deliverability health of
example.com.""Does
example.comhave a valid SPF and DMARC setup?"
Security
Your API key is read only from the server's environment and sent only to the VerifyAnyEmail API over HTTPS. It is never logged (logs go to stderr; the stdout stream is reserved for the MCP protocol).
Keep the key server-side — treat the MCP config file like any other secret.
Links
Website & dashboard: https://verifyany.email
API docs: https://verifyany.email/docs
Issues: https://github.com/verifyanyemail/verifyanyemail-mcp/issues
MIT © VerifyAnyEmail
Available Tools
9 toolscheck_dkimARead-onlyInspect
Check a domain's DKIM signing record for a given selector. Free — no verification credits.
Inputs: domain (required), selector.
check_dmarcARead-onlyInspect
Check a domain's DMARC policy (none | quarantine | reject) and alignment. Free — no verification credits.
Inputs: domain (required).
check_domain_healthARead-onlyInspect
Run an overall email-deliverability health check for a domain — combines MX, SPF, DKIM, DMARC and related signals into a single graded summary with actionable findings. Free — no verification credits.
Inputs: domain (required).
check_mxARead-onlyInspect
Look up a domain's MX (mail exchanger) records and whether it can receive email. Free — no verification credits.
Inputs: domain (required).
check_spfARead-onlyInspect
Check a domain's SPF record and flag common misconfigurations. Free — no verification credits.
Inputs: domain (required).
get_batch_resultsARead-onlyInspect
Fetch a page of results for a bulk verification batch. Paginated — use page and pageSize for large batches.
Inputs: batchId (required), page, pageSize.
get_batch_statusARead-onlyInspect
Check the progress of a bulk verification batch: lifecycle state (queued | processing | completed | failed), addresses processed, and per-status counts once available.
Inputs: batchId (required).
verify_batchAInspect
Submit many email addresses for asynchronous bulk verification. Returns a batchId immediately; the job runs in the background. Poll get_batch_status until status is 'completed', then call get_batch_results. Reserves 1 credit per address. Prefer verify_email for one-off checks.
Inputs: emails (required), name, webhookUrl.
verify_emailAInspect
Verify whether a single email address is real and safe to send to, in real time. Returns a deliverability verdict (deliverable | undeliverable | risky | unknown), a 0–100 confidence score, a safeToSend flag, and signals (catch-all, disposable, role-based, free provider, likely typo). Spends 1 verification credit per call. Tip: addresses at the test.verifyany.email domain (e.g. deliverable@test.verifyany.email, undeliverable@…, risky@…, unknown@…) return canned results and cost 0 credits.
Inputs: email (required), smtpProbe, catchAllDetection.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
The tools have clearly distinct purposes: single verification vs. batch submission vs. batch status/results, and individual DNS checks vs. an aggregate domain-health check. Descriptions clarify the relationship between check_domain_health and the individual check_* tools, preventing likely misselection.
Names follow predictable snake_case verb_noun patterns grouped by function: check_* for DNS diagnostics, verify_* for email verification, and get_batch_* for batch retrieval/status. The mixed prefix families are consistent within their domains and easy to infer.
Nine tools is well-scoped for an email verification and domain-health server. Each tool covers a meaningful operation, and there are no redundant or filler tools.
The core workflows are covered: single verification, batch submit/status/results, individual DNS checks, and aggregate domain health. Minor gaps exist around batch lifecycle management such as cancellation or listing batches, but these are not critical for typical agent use.
Maintenance
Related MCP Connectors
Free SPF, DKIM, DMARC, blacklist, MX and bounce checks for any domain, as MCP tools for AI agents.
Email verification and domain intelligence for AI agents, including single and bulk email checks.
Email verification and domain intelligence for AI agents. MX, RDAP, SSL checks. 25 free credits.
Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.
Related MCP Servers
- AlicenseAqualityDmaintenanceEmail-deliverability tools for AI agents — 12 MCP tools across email verification, DNSBL across 50 zones, SPF/DKIM/DMARC analysis, spam-trap scoring, domain intelligence, and email finder. Free tier with no credit card.1235 npm1MIT
- AlicenseAqualityDmaintenanceEnables real-time email verification via MCP tools, checking syntax, MX, disposable domains, and optional SMTP probe to determine deliverability with a VALID/RISKY/INVALID verdict.23 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to verify email addresses in real-time, checking syntax, DNS, MX records, and SMTP handshake, returning verdicts and deliverability scores without sending actual emails.-

truelist-mcpofficial
AlicenseAqualityCmaintenanceEnables AI assistants to validate individual or batch email addresses for deliverability, and to check account plan information, through MCP tools.329 npmMIT