MCP server

Connect EmailVerify Pro to Claude, Cursor, Windsurf or any Model Context Protocol client. Email verification tools with read-only and destructive annotations.

The Model Context Protocol lets an AI assistant call real tools instead of guessing. This server exposes 144 tools — every endpoint except the 8 inbound ESP webhooks, which exist for SendGrid, SES, Postmark and Stripe to call you.

Once connected, an assistant can verify addresses, clean lists, resolve catch-all domains and check your quota, all without you writing any code.

Install

Node — nothing to install ahead of time:

{
  "mcpServers": {
    "emailverify": {
      "command": "npx",
      "args": ["-y", "@emailverifypro/mcp"],
      "env": { "EMAILVERIFY_API_KEY": "evp_your_key" }
    }
  }
}

Python:

{
  "mcpServers": {
    "emailverify": {
      "command": "uvx",
      "args": ["--from", "emailverify[mcp]", "emailverify-mcp"],
      "env": { "EMAILVERIFY_API_KEY": "evp_your_key" }
    }
  }
}

Where that config goes

In Claude Desktop the file is reachable via Settings → Developer → Edit Config. Restart the app after editing.

Try it

Ask in plain language:

• “Verify brandon@seamlessai.com and tell me whether it will bounce.”
• “Here are 40 addresses — which are safe to email?”
• “Is acme.com a catch-all domain?”
• “What email format does stripe.com use? Then work out Jane Doe's address.”
• “How much of my verification quota is left this month?”
• “Add these five addresses to my suppression list.”
• “This address came back unknown — dig into why.”

What the assistant sees

Each tool carries the endpoint's summary, its method and path, and an annotation saying how dangerous it is.

Tools are named after the endpoint: get_validate, post_validate_bulk, post_find_email, delete_gdpr_erase.

Coverage by category

Narrowing the tool list

144 tools is a large surface, and most clients choose more accurately from a smaller set. Two environment variables trim it:

EMAILVERIFY_MCP_READONLY=1

Publishes only the 90 read-only tools — nothing can delete or overwrite. This is the safest setting for a shared or autonomous assistant.

EMAILVERIFY_MCP_TAGS="Verification,Bulk,Account"

Publishes only those categories. Combine both for a minimal, read-only verification surface.

Configuration

A read-only, verification-only setup:

{
  "mcpServers": {
    "emailverify": {
      "command": "npx",
      "args": ["-y", "@emailverifypro/mcp"],
      "env": {
        "EMAILVERIFY_API_KEY": "evp_your_key",
        "EMAILVERIFY_MCP_READONLY": "1",
        "EMAILVERIFY_MCP_TAGS": "Verification,Bulk"
      }
    }
  }
}

Checking it works

Run the server by hand. It speaks JSON-RPC over stdio and prints a banner to stderr:

EMAILVERIFY_API_KEY=evp_your_key npx -y @emailverifypro/mcp

emailverify MCP server v1.0.0 — 144 tools (API v6.0.0)

If you see that line, the server is healthy and the problem is in your client config.

Troubleshooting

The server doesn't appear. JSON config files are unforgiving — a trailing comma or a missing brace silently breaks the whole file. Validate it, then fully restart the client.

Tools appear but every call fails with 401. EMAILVERIFY_API_KEY is missing or wrong. It must sit in the env block of the server entry, not in your shell — MCP servers do not inherit your interactive environment.

Calls time out. Some verifications legitimately take 30 seconds or more while SMTP probes run. Raise EMAILVERIFY_TIMEOUT, or ask the assistant to use the async bulk endpoint and poll the job.

npx is slow the first time. It downloads the package on first run. Install it globally (npm i -g @emailverifypro/mcp) and use emailverify-mcp as the command to avoid the delay.

The assistant picks the wrong tool. Narrow the surface with EMAILVERIFY_MCP_TAGS, and name the operation you want in your prompt.