Give your AI tools a clean email check.

Add one remote MCP URL, sign in, and choose the project that should pay for checks made by your AI tools.

Connection details

Most MCP clients only need the server URL. Your browser will open so you can sign in and approve a project.

Server URL
https://emailverifier.dev/mcp
Authentication
Sign in with emailverifier.dev and choose a project
API key option
Use X-API-Key for headless servers and scripts

Available tools

Two tools.
One job each.

verify_email

Verify a complete email address before creating a lead, inviting a user, or updating customer data.

Input
email · string · required
Returns
email · status · action · flagged · signals · suggestion
Cost
1 project credit

Request

POST /mcp
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "verify_email",
    "arguments": {
      "email": "demo@gmail.com"
    }
  }
}

check_domain

Check a domain before deciding whether to accept addresses from it or apply stricter signup rules.

Input
domain · string · required
Returns
domain · classification · risk · mail_routing
Cost
1 project credit

Request

POST /mcp
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "check_domain",
    "arguments": {
      "domain": "gmail.com"
    }
  }
}

Useful results.
Honest uncertainty.

Discovery is free.

initialize and tools/list do not spend project credits. Each tool call uses one credit.

Projects stay isolated.

You choose one project during authorization. Its credits and request history stay separate.

No guessing.

If a reliable answer is not available, the result is unknown.