Model Context Protocol · v1.2.3

Email verification for AI agents

Let Claude, ChatGPT, Cursor and any MCP-compatible assistant verify email addresses and check deliverability in real time. One install, nine tools, your API key stays on your side.

Get an API key View on npm

Add it to your AI client

The server runs with npx — nothing to install globally. Create an API key in your dashboard and drop it in below.

🖥️Claude Desktop

Settings → Developer → Edit Config, then add:

{
  "mcpServers": {
    "verifyanyemail": {
      "command": "npx",
      "args": ["-y", "verifyanyemail-mcp"],
      "env": { "VERIFYANYEMAIL_API_KEY": "vae_your_key" }
    }
  }
}

⌨️Claude Code

Run in your terminal:

claude mcp add verifyanyemail \
  -e VERIFYANYEMAIL_API_KEY=vae_your_key \
  -- npx -y verifyanyemail-mcp

✴️Cursor

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" }
    }
  }
}

What the agent can do

Tool	Description	Cost
verify_email	Verify one address — verdict, 0–100 score, safe-to-send, and signals.	1 credit
verify_batch	Submit many addresses for async bulk verification; returns a batch id.	1 / address
get_batch_status	Poll a batch’s progress and per-status counts.	free
get_batch_results	Fetch a paginated page of batch results.	free
check_mx	MX records — can the domain receive mail.	free
check_spf	SPF record and misconfiguration flags.	free
check_dmarc	DMARC policy and alignment.	free
check_dkim	DKIM record for a given selector.	free
check_domain_health	Combined MX/SPF/DKIM/DMARC health grade with findings.	free

Diagnostics are free (no verification credits). Try it with deliverable@test.verifyany.email (and undeliverable@, risky@, unknown@) — canned results, 0 credits.

Hosted connector — ChatGPT & Claude.ai

Prefer a one-click connection with nothing to install? Point your assistant at our hosted MCP endpoint and authenticate with your API key:

https://mcp.verifyany.email/mcp

ChatGPT (paid plans): Plugins → ＋ → Add custom MCP server, paste the URL, and provide your vae_… key as a Bearer token — ChatGPT turns it into a plugin.
Claude.ai (paid plans): Settings → Connectors → Add custom connector, paste the URL, and authenticate with your vae_… key.
Cursor & other MCP clients: add it as a remote (streamable-HTTP) MCP server with an Authorization: Bearer vae_… header.

The connector supports OAuth 2.1 — in ChatGPT and Claude.ai you'll be prompted to connect your VerifyAnyEmail account (nothing to paste); other MCP clients can use a Bearer API key. OpenAI is retiring Custom GPTs on December 11, 2026 in favour of these MCP-based plugins.

Your key stays yours. The MCP server reads your API key only from its own environment and sends it only to the VerifyAnyEmail API over HTTPS — never to the model, never logged. Keep the key server-side and treat the config file like any other secret.

Build with the API directly?

Grab a native SDK for your language, or read the full reference.

Official SDKs API reference