Model Context Protocol

Email Verification for AI Agents

Give your AI assistant production-grade email verification. Verify emails, check domains, and validate syntax — directly inside Cursor, Claude Desktop, or any MCP-compatible client.

Get API KeyView API Docs

No credit card required. Free credits included.

5

MCP tools available

2

AI clients supported

Same

Quality as REST API

~30s

Setup time

Why developers use the MCP server

Stop context-switching to verify emails. Let your AI agent handle it while you stay focused on building.

Verify emails while coding

Ask your AI assistant to verify an email address mid-session. No browser tabs, no copy-paste, no interruptions.

Build AI-powered forms

Let your AI agent validate user input in real time. Catch disposable emails, invalid domains, and undeliverable addresses at the source.

Automate email hygiene

Use AI agents to audit mailing lists, flag risky addresses, and clean data — all with the same verification quality as the REST API.

Available MCP Tools

Five purpose-built tools covering every email verification scenario.

verify_email

Full email verification — syntax, MX records, SMTP, disposable detection, privacy services, and deliverability.

1 credit
verify_domain

Full domain verification — MX records, disposable domain detection, privacy services, and catch-all configuration.

1 credit
check_deliverability

Fast deliverability check using MX and SMTP verification only. No external API calls, faster response.

1 credit
verify_batch

Batch verification for up to 100 emails or domains in a single tool call.

1 per item
validate_email_syntax

Instant local RFC 5322 syntax validation with zero network calls.

Free
Setup

Up and running in 30 seconds

Three steps to add email verification to your AI workflow.

01

Get your API key

Sign up for a free account and copy your API key from the dashboard. No credit card required.

02

Add the MCP config

Paste the configuration snippet into your .cursor/mcp.json or Claude Desktop config file.

03

Start verifying

Ask your AI assistant to verify any email or domain. It uses your credentials automatically.

MCP configuration

{
  "mcpServers": {
    "email-checker": {
      "url": "https://api.verify-email.app/mcp",
      "headers": {
        "X-API-Key": "your-api-key"
      }
    }
  }
}

Cursor

Add via Settings → Tools & MCP, or drop the config into .cursor/mcp.json in your project or home directory.

Claude Desktop

Add to the mcpServers section in your claude_desktop_config.json. The server URL and API key header are shown above.

Frequently asked questions

What is the MCP server?

The MCP (Model Context Protocol) server exposes email verification as tools that AI agents can call. It wraps the same REST API used by thousands of developers, so you get production-grade verification directly in your AI workflow.

Which AI clients are supported?

Any MCP-compatible client works. Cursor and Claude Desktop are officially supported. Other clients that implement the Model Context Protocol standard should work without any changes.

Does it consume API credits?

Yes — each tool call consumes credits the same way as a REST API call. validate_email_syntax is always free. All other tools consume 1 credit per email or domain verified.

Is my API key secure?

Your API key is stored locally in your MCP config file and sent only to api.verify-email.app over HTTPS. It is never stored on our servers beyond what is needed to authenticate each request.

Can I use the same key for the REST API and MCP server?

Yes. The MCP server uses the same API key as the REST endpoints. Credits are shared across both.

Add email verification to your AI workflow

Get API Key — it's freeView full API docs