Connect ValidatedMails with MCP

Set up your assistant

1. Create an API key in the console. Validation uses your account’s prepaid credits.
2. Install uv and Python 3.10 or newer.
3. Download the MCP server and save it in a permanent local folder.
4. Add the configuration below to an MCP client that supports local stdio servers. Replace the absolute path and API key, then restart the client. If it cannot find uv, use its absolute executable path.

{
  "mcpServers": {
    "validatedmails": {
      "command": "uv",
      "args": ["run", "/absolute/path/validatedmails_mcp.py"],
      "env": { "VALIDATEDMAILS_API_KEY": "YOUR_API_KEY" }
    }
  }
}

This adapter runs on your computer and calls https://api.validatedmails.com. There is no hosted MCP URL. Keep the key in your client’s private configuration; do not commit it or paste it into a conversation.

Start with a free connection check

Ask your assistant to call check_api_key. It verifies authentication without consuming credits. Then ask it to verify one email, or a batch of up to 100 addresses.

• check_api_key: verify the configured key and account identity; free.
• validate_email: verify one address.
• validate_batch: verify 1–100 addresses in input order.

Validation costs one credit per valid, risky, or invalid result. Unknown results are not charged. These tools can spend credits; configure your assistant’s tool permissions accordingly.

Use the API directly

Set VALIDATEDMAILS_API_KEY in your environment and check it without spending credits:

curl https://api.validatedmails.com/api-keys/me \
  -H "Authorization: Bearer $VALIDATEDMAILS_API_KEY"

Use Authorization: Bearer for authentication. See the validation quickstart for requests and the response reference for fields.

Handle results and failures

Branch on status: valid, risky, invalid, or unknown. Unknown means inconclusive; it does not mean invalid. Inspect batch item errors as well as the overall response.

A timeout can occur after the API has processed a request. The adapter does not automatically retry paid requests. An HTTP 401 means the key was rejected, 402 means insufficient credits, and 429 means rate or capacity limits. Retain the request ID when investigating failures.

For machine-readable guidance, start with llms.txt or this guide as Markdown.