MCP Server

emailvalidation ships a hosted Model Context Protocol (MCP) server, so AI agents and assistants can call the API as native tools — no SDK or glue code required.

https://api.emailvalidation.io/mcp

The endpoint speaks the streamable HTTP transport. All requests — including listing the available tools — require your API key, sent as the apikey header. You can get a free API key here.

Connect

Using Claude Code:

claude mcp add --transport http emailvalidation https://api.emailvalidation.io/mcp --header "apikey: YOUR_API_KEY"

Or add the server to any MCP-capable client (Claude Desktop, Cursor, VS Code, ...):

{
  "mcpServers": {
    "emailvalidation": {
      "url": "https://api.emailvalidation.io/mcp",
      "headers": { "apikey": "YOUR_API_KEY" }
    }
  }
}

Available tools

The tools are generated from the same OpenAPI specification that describes the REST API, so they always match the documented endpoints, parameters and responses.

Tool	Endpoint	Description
`getInfo`	`GET /v1/info`	Validate an email address
`createBulkJob`	`POST /v1/bulk`	Submit a list for bulk verification
`listBulkJobs`	`GET /v1/bulk`	List your bulk jobs
`getBulkJob`	`GET /v1/bulk/{job_id}`	Get a bulk job's status
`deleteBulkJob`	`DELETE /v1/bulk/{job_id}`	Delete a bulk job
`getStatus`	`GET /v1/status`	Account quota status

Every bulk endpoint is a tool except the results download: GET /v1/bulk/{job_id}/results returns a JSON or CSV file of up to 100,000 rows, too large for a tool result. Download it from the job's links.results over the REST API once getBulkJob reports completed. createBulkJob takes the list as the emails array; CSV and TXT file uploads are only available over the REST API.

Quotas and errors

Tool calls are metered exactly like REST requests: they consume your plan quota and return the same status codes and error responses (401, 422, 429, ...). If a call fails, the tool result contains the API's error message including hints on how to proceed.