# emailverifier.dev

> emailverifier.dev is a freemium MCP server for data quality. Hosted MCP server that verifies email addresses and domains for AI agents. It runs as a hosted remote server, so there is nothing to install locally.

- **Kind:** MCP server
- **Pricing:** Freemium
- **Platforms:** API, Web
- **Website:** https://emailverifier.dev/docs/mcp
- **Repository:** https://github.com/usamaejaz/emailverifier.dev
- **MCP Registry name:** io.github.usamaejaz/emailverifier
- **Categories:** [data quality](https://ai-powered.com/categories/data-quality)
- **Listing updated:** 2026-11-20

## About

The README describes this as a hosted Model Context Protocol server, so there is nothing to install or run locally. An agent connects over Streamable HTTP, signs in through a browser or sends a project API key, and then calls tools that check an address or a domain before the agent acts on it.

The two tools are verify_email, which returns a status, a recommended action, risk signals and an optional typo suggestion, and check_domain, which reports classification, risk and whether the domain can receive mail. Results cover syntax, mail routing, disposable and free-provider lists, role-address signals and mailbox acceptance where it can be tested. Each returned result is a recommendation that the calling application is expected to act on.

The page is aimed at developers and teams who want agents to validate addresses while creating leads, inviting users or cleaning customer records. Credits are charged per check, and the same balance is shared with the REST API and bulk verifier of the same vendor.

## Features

- **Hosted remote server:** Connects over Streamable HTTP at a single endpoint, so no local package or container is needed.
- **Email verification tool:** verify_email returns a status, an allow, review or block action, signals and a possible typo fix.
- **Domain checking tool:** check_domain reports classification, risk and whether mail routing is available for a domain.
- **Browser or API key auth:** Supports OAuth sign-in to a chosen project or an X-API-Key header for scripts.
- **Structured results:** Responses include both text content and structuredContent for agents to parse.
- **Per-check credits:** Each authenticated check uses one project credit, including unknown results.

## Good for

- Validate addresses before creating a sales lead from an agent workflow
- Block disposable or free-provider signups in an onboarding flow
- Check a domain's mail routing before inviting a user
- Flag role-based or risky addresses while updating customer records

## Install

### Claude Code (Terminal)

```sh
claude mcp add --transport http emailverifier https://emailverifier.dev/mcp
```

### Claude Desktop (Settings → Connectors → Add custom connector)

```sh
https://emailverifier.dev/mcp
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "emailverifier": {
      "url": "https://emailverifier.dev/mcp"
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "emailverifier": {
      "type": "http",
      "url": "https://emailverifier.dev/mcp"
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "emailverifier": {
      "serverUrl": "https://emailverifier.dev/mcp"
    }
  }
}
```

### Grok Bot (Grok Bot desktop app → Connect apps → Add a custom connector)

```sh
https://emailverifier.dev/mcp
```

Enter a Name (for example "emailverifier.dev"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin.

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "emailverifier": {
      "type": "http",
      "url": "https://emailverifier.dev/mcp"
    }
  }
}
```

## Tools

- `verify_email`: Checks a complete email address for status, action, flags and signals.
- `check_domain`: Checks a domain's classification, risk and mail routing.

## FAQ

### What tools does the server expose?

The README lists verify_email and check_domain as the tools to look for in the client's tool list after authorization.

### How much does emailverifier.dev cost?

The pricing page lists 1,000 free starter credits on the first project, and a one-time $10 pack of 20,000 credits at $0.50 per 1,000 checks. Each check uses one credit.

### Does a verification guarantee delivery?

No. The docs state that verification does not prove inbox ownership or guarantee delivery, and that timeouts or mail-server restrictions can produce an unknown status.

### Which clients can connect?

The docs give setup steps for Claude Code, Cursor and Codex, and say other clients need remote Streamable HTTP support with OAuth or custom headers.

### How do I add emailverifier.dev to Claude Code?

Run this command in your terminal: claude mcp add --transport http emailverifier https://emailverifier.dev/mcp

### What are the best alternatives to emailverifier.dev?

The closest alternatives to emailverifier.dev are UK Data: Email and domain checks and Verified.net.

## Where this comes from

- Description: written from the project's website and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.

## Alternatives

- [UK Data: Email and domain checks](https://ai-powered.com/mcp/uk-data-email-and-domain-checks): UK Data: Email and domain checks is a freemium MCP server for communication.
- [Verified.net](https://ai-powered.com/mcp/verified-net): Verified.net is a freemium MCP server for data quality.

---
Source: https://ai-powered.com/mcp/emailverifier-dev
