# Email Verifier MCP Server | Verify Emails in Claude | $0.30/1k (`cold_email_master/email-verifier-mcp-server`) Actor

MCP server that lets AI agents verify email addresses. Syntax, DNS, MX and SMTP checks with disposable and role-based detection, no mail sent. Works in Claude, Cursor, Chatgpt and any MCP client. $0.30 per 1,000.

- **URL**: https://apify.com/cold\_email\_master/email-verifier-mcp-server.md
- **Developed by:** [indrajit guha](https://apify.com/cold_email_master) (community)
- **Categories:** AI, Lead generation, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.30 / 1,000 email verifieds

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Email Verifier MCP Server — verify email addresses from Claude, Cursor or any agent

**Give your AI assistant the ability to check whether an email address is real.** This Actor is an [MCP](https://modelcontextprotocol.io) server: connect it once, and your agent can verify addresses mid-conversation — before it drafts outreach, enriches a CRM record, or hands you a lead list.

$0.30 per 1,000 addresses verified. No Verimailx account needed — you authenticate with your Apify token.

***

### What your agent can do

| Tool | What it does |
|---|---|
| `verify_email` | Check one address. Returns a verdict, a 0–100 deliverability score, and every individual check. |
| `verify_email_list` | Check up to 25 addresses in one call. Returns per-address records plus a summary count by verdict. |

Each check runs RFC syntax validation, DNS resolution, MX record inspection and an SMTP handshake, and flags disposable and role-based mailboxes. **No mail is ever sent** — the SMTP handshake asks the receiving server whether a mailbox exists and then disconnects, so nobody on your list is contacted.

Verdicts are `valid` (safe to send), `invalid` (will bounce), `risky` (disposable, role-based, or a catch-all domain) and `unknown` (server timeout or ambiguous response).

***

### Connect it

#### Claude Desktop / Claude Code

Add this to your MCP configuration, using an [Apify API token](https://console.apify.com/account/integrations):

```json
{
  "mcpServers": {
    "verimailx": {
      "url": "https://cold-email-master--verimailx-email-mcp.apify.actor/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_API_TOKEN>"
      }
    }
  }
}
```

#### Cursor, Windsurf, and other MCP clients

Same URL, same bearer token. The server speaks MCP over the Streamable HTTP transport.

The Actor runs in [Standby mode](https://docs.apify.com/platform/actors/development/programming-interface/standby), so an instance is kept warm and answers immediately — there is no run to start.

***

### What it looks like in use

> **You:** Before I import these, are any of them going to bounce?
> `founder@stripe.com, info@mailinator.com, nobody@thisdomaindoesnotexist.xyz`
>
> **Claude:** *(calls `verify_email_list`)* One of three is safe to send to. `founder@stripe.com` is valid, score 98. `info@mailinator.com` is risky — it's a disposable address and a role mailbox. `nobody@thisdomaindoesnotexist.xyz` is invalid; the domain has no MX records.

***

### Pricing

**$0.30 per 1,000 addresses verified** — billed per address, not per call or per run.

| Volume | Cost |
|---|---:|
| 100 addresses | $0.03 |
| 1,000 addresses | $0.30 |
| 10,000 addresses | $3.00 |

Failed lookups are not charged. Apify's platform fee is included in the rate.

If you set a maximum charge for the run, the server checks the remaining budget
before it verifies anything. Once the budget is spent it says so plainly — it
will not keep verifying addresses it cannot bill you for, and a partial list
call tells you exactly which addresses it left unverified.

***

### Verifying more than 25 at a time

This server is built for conversational use — an agent checking a handful of addresses inside a task. For list cleaning at scale, use the bulk Actor instead: [Bulk Email Verifier & Validator](https://apify.com/cold_email_master/bulk-email-verifier-validator). It takes a link to a CSV, an Apify dataset ID, or a pasted list, and handles tens of thousands of addresses per run at the same price.

***

### FAQ

**Q: Do I need a Verimailx account?**
A: No. The Actor carries the Verimailx credentials; you authenticate with your Apify token and are billed through Apify.

**Q: Does this send email to the addresses I check?**
A: No. Verification stops at the SMTP handshake. No message is delivered and the recipient sees nothing.

**Q: How accurate is catch-all detection?**
A: Catch-all domains — ones configured to accept mail at any address — are reported as `risky` rather than `valid`, because an individual mailbox behind a catch-all cannot be confirmed. Treating them as valid is the most common cause of bounces on a "clean" list.

**Q: What happens to the addresses I check?**
A: They are sent to the Verimailx API for verification and are not written to any persistent storage by this Actor.

**Q: Can I use this without an AI agent?**
A: For scripted use the [REST Actor](https://apify.com/cold_email_master/bulk-email-verifier-validator) is a better fit — MCP is designed for tool-calling clients.

***

### Support

- **Issues with this Actor:** open an issue on the Actor's Issues tab
- **Bulk pricing (100k+ addresses):** contact us through Apify messaging
- **Verimailx API:** [verimailx.com](https://verimailx.com)

***

### Changelog

#### 0.0.1 — Initial release

- `verify_email` and `verify_email_list` tools over Streamable HTTP, served through Actor Standby.
- Pay-per-event billing, charged per address verified.

# Actor input Schema

## Actor input object example

```json
{}
```

# Actor output Schema

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("cold_email_master/email-verifier-mcp-server").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("cold_email_master/email-verifier-mcp-server").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call cold_email_master/email-verifier-mcp-server --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,cold_email_master/email-verifier-mcp-server"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/sEbbExIelmaHzQlDX/builds/9sBrhdk6DeEOTGlqA/openapi.json