Beta Model Context Protocol

Easy Email Verification MCP server

A hosted Model Context Protocol server that lets AI agents verify email addresses: one address or up to 50 per call, with the result, the reason and risk signals. Connect it to any MCP client with your API key.

Set up your client

Prompt: Connect the Easy Email Verification MCP server (https://mcp.easyemailverification.com/mcp, header X-API-Key) and verify john.smith@acme.com

Why Easy Email Verification

Single, batch and bulk

verify_email for one address, verify_emails for up to 50, and bulk jobs for up to 10,000 with a summary instead of the whole list. Inputs are validated and deduplicated before any credit is used.

Honest results

valid, invalid or unknown with the reason. Tool descriptions tell the model that unknown is neither valid nor invalid.

Safe by design

No automatic retries that could charge twice, clear tool errors for invalid keys and missing credits, and logs that never contain email addresses.

Same key, same credits

Uses your Easy Email Verification API key and plan. Test with the public sandbox key first.

How it works

1

Add the server URL https://mcp.easyemailverification.com/mcp to your MCP client, with your API key in the X-API-Key header.

2

The client lists seven tools: verify_email, verify_emails, get_credits, create_bulk_job, get_bulk_status, get_bulk_summary and delete_bulk_job.

3

When you ask to verify addresses, the agent calls a tool; each address uses one credit.

4

The agent gets structured results (result, reason, safe_to_send, disposable, role, free, accept_all, did_you_mean) and answers you.

Set up

1
Get an API key. Create a free account and copy a key in API settings, or test with eev_sandbox_key and addresses at sandbox.easyemailverification.com (no credits).
2
Configure your client (replace YOUR_API_KEY):
Claude Code – Terminal
claude mcp add --transport http --scope user eev https://mcp.easyemailverification.com/mcp --header "X-API-Key: YOUR_API_KEY"
Cursor – ~/.cursor/mcp.json
{
  "mcpServers": {
    "eev": {
      "url": "https://mcp.easyemailverification.com/mcp",
      "headers": { "X-API-Key": "YOUR_API_KEY" }
    }
  }
}
VS Code – .vscode/mcp.json (asks for the key once)
{
  "inputs": [{ "type": "promptString", "id": "eev-key", "description": "EEV API key", "password": true }],
  "servers": {
    "eev": {
      "type": "http",
      "url": "https://mcp.easyemailverification.com/mcp",
      "headers": { "X-API-Key": "${input:eev-key}" }
    }
  }
}
Codex CLI – ~/.codex/config.toml
[mcp_servers.eev]
url = "https://mcp.easyemailverification.com/mcp"
http_headers = { "X-API-Key" = "YOUR_API_KEY" }
Windsurf – ~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "eev": {
      "serverUrl": "https://mcp.easyemailverification.com/mcp",
      "headers": { "X-API-Key": "YOUR_API_KEY" }
    }
  }
}
Gemini CLI – ~/.gemini/settings.json
{
  "mcpServers": {
    "eev": {
      "httpUrl": "https://mcp.easyemailverification.com/mcp",
      "headers": { "X-API-Key": "YOUR_API_KEY" }
    }
  }
}
Claude Desktop – Settings → Developer → Edit Config (needs Node.js)
{
  "mcpServers": {
    "eev": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.easyemailverification.com/mcp", "--header", "X-API-Key:${EEV_API_KEY}"],
      "env": { "EEV_API_KEY": "YOUR_API_KEY" }
    }
  }
}
3
Check the connection: the client should list verify_email, verify_emails and the bulk and credit tools. Then ask: Verify valid@sandbox.easyemailverification.com.

Transport: Streamable HTTP, stateless, POST only. Authentication: X-API-Key header (OAuth is not available yet, so web apps such as Claude.ai and the Gemini app cannot connect). The server is in beta; clients tested so far: Claude Code.

Prompts to try

Verify john.smith@acme.com and tell me if it is safe to send to.

Check these addresses and tell me which ones to remove before my campaign: anna@example.org, sales@example.com, mark@gmial.com

Read contacts.csv, verify the email column and add the result and the reason.

Before saving this signup form, verify the address with Easy Email Verification and reject invalid or disposable ones.

Your account and credits

Each verified address uses one credit from the account that owns the API key, except when the receiving server cannot be reached (reason no_connect). Errors are returned as tool errors: invalid key, no credits left (with a link to plans) and rate limits (with the wait time when the API provides it).

Building an application instead of using an agent? Call the REST API directly: agents.md and openapi.json.

Create a free account · Plans and credits

Other ways to use Easy Email Verification with AI

Claude Beta

Add the MCP server to Claude Code with one command, or to Claude Desktop with mcp-remote. Uses your API key. Claude.ai in the browser needs OAuth (coming later).

Learn more

AI coding assistants Available

Point Claude Code, Cursor, Copilot or Codex at agents.md and the OpenAPI spec to write a correct integration.

Learn more

Gemini Beta

Add the MCP server to Gemini CLI in settings.json with your API key. The Gemini app (gemini.google.com) needs OAuth and comes later.

Learn more

All AI integrations

FAQ

What is the MCP server URL?

https://mcp.easyemailverification.com/mcp, over Streamable HTTP. Send your API key in the X-API-Key header.

Which clients work?

Any MCP client that supports remote HTTP servers with custom headers. Tested so far: Claude Code. Setup for the others is listed above.

Does it support OAuth?

Not yet. Clients that only connect with OAuth (Claude.ai in the browser, the Gemini app) cannot use it for now.

Will a failed call charge me twice?

No. The server never retries a request that may have reached the API; it only retries when the connection failed before sending.

What does "unknown" mean?

The receiving mail server did not give a reliable answer (for example a timeout or a temporary block). Unknown is neither valid nor invalid; the reason says why.

Give your agent email verification

One URL, one header, every verification you need.

By using this website, you automatically accept that we use cookies.