# VerifyAnyEmail (npm · verifyanyemail-mcp)

Real-time email verification and deliverability diagnostics (MX, SPF, DKIM, DMARC).

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.verifyany.email`: 38/100, [markdown](https://verifymcp.io/servers/verifyanyemail-verifyanyemail-mcp/mcp.md), [page](https://verifymcp.io/servers/verifyanyemail-verifyanyemail-mcp/mcp)
- npm · `verifyanyemail-mcp`: 66/100 (this document), [markdown](https://verifymcp.io/servers/verifyanyemail-verifyanyemail-mcp/verifyanyemail-mcp.md), [page](https://verifymcp.io/servers/verifyanyemail-verifyanyemail-mcp/verifyanyemail-mcp)

## Channel facts

- Registry: `npm`
- Package: `verifyanyemail-mcp`
- Version: `1.2.3`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 94 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 711 tokens (~79/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the VerifyAnyEmail MCP server?

VerifyAnyEmail runs locally as an npm package, launched with npx -y verifyanyemail-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add verifyanyemail-verifyanyemail-mcp -- npx -y verifyanyemail-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "verifyanyemail-verifyanyemail-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "verifyanyemail-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "verifyanyemail-verifyanyemail-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "verifyanyemail-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add verifyanyemail-verifyanyemail-mcp -- npx -y verifyanyemail-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "verifyanyemail-verifyanyemail-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "verifyanyemail-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add verifyanyemail-verifyanyemail-mcp --command npx --arg -y --arg verifyanyemail-mcp
```

### Hermes

```yaml
mcp_servers:
  verifyanyemail-verifyanyemail-mcp:
    command: "npx"
    args: ["-y", "verifyanyemail-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "verifyanyemail-verifyanyemail-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "verifyanyemail-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add verifyanyemail-verifyanyemail-mcp -t stdio -c npx -a -y verifyanyemail-mcp
```

### Other

```json
{
  "mcpServers": {
    "verifyanyemail-verifyanyemail-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "verifyanyemail-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-31 (score 66, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-30 (score 51)

First indexed and scored.

## MCP tools (9)

### `verify_email` (~187 tokens)

Verify whether a single email address is real and safe to send to, in real time. Returns a deliverability verdict (deliverable | undeliverable | risky | unknown), a 0–100 confidence score, a safeToSend flag, and signals (catch-all, disposable, role-based, free provider, likely typo). Spends 1 verification credit per call. Tip: addresses at the test.verifyany.email domain (e.g. deliverable@test.verifyany.email, undeliverable@…, risky@…, unknown@…) return canned results and cost 0 credits.

Input parameters:

- `catchAllDetection` (boolean): Set false to skip catch-all detection. Default true.
- `email` (string, required): The email address to verify, e.g. name@example.com
- `smtpProbe` (boolean): Set false to skip the live SMTP mailbox probe (DNS-only). Default true.

### `verify_batch` (~107 tokens)

Submit many email addresses for asynchronous bulk verification. Returns a batchId immediately; the job runs in the background. Poll get_batch_status until status is 'completed', then call get_batch_results. Reserves 1 credit per address. Prefer verify_email for one-off checks.

Input parameters:

- `emails` (array, required): Array of email addresses to verify.
- `name` (string): Optional human-friendly label for the batch.
- `webhookUrl` (string): Optional HTTPS URL to receive a signed batch.completed callback.

### `get_batch_status` (~54 tokens)

Check the progress of a bulk verification batch: lifecycle state (queued | processing | completed | failed), addresses processed, and per-status counts once available.

Input parameters:

- `batchId` (string, required): The batchId returned by verify_batch.

### `get_batch_results` (~83 tokens)

Fetch a page of results for a bulk verification batch. Paginated — use page and pageSize for large batches.

Input parameters:

- `batchId` (string, required): The batchId returned by verify_batch.
- `page` (integer): 1-based page number. Default 1.
- `pageSize` (integer): Rows per page (1–1000). Default 100.

### `check_mx` (~50 tokens)

Look up a domain's MX (mail exchanger) records and whether it can receive email. Free — no verification credits.

Input parameters:

- `domain` (string, required): The domain to inspect, e.g. example.com

### `check_spf` (~45 tokens)

Check a domain's SPF record and flag common misconfigurations. Free — no verification credits.

Input parameters:

- `domain` (string, required): The domain to inspect, e.g. example.com

### `check_dmarc` (~50 tokens)

Check a domain's DMARC policy (none | quarantine | reject) and alignment. Free — no verification credits.

Input parameters:

- `domain` (string, required): The domain to inspect, e.g. example.com

### `check_dkim` (~68 tokens)

Check a domain's DKIM signing record for a given selector. Free — no verification credits.

Input parameters:

- `domain` (string, required): The domain to inspect, e.g. example.com
- `selector` (string): The DKIM selector, e.g. 'google' or 'mail'. Optional.

### `check_domain_health` (~67 tokens)

Run an overall email-deliverability health check for a domain — combines MX, SPF, DKIM, DMARC and related signals into a single graded summary with actionable findings. Free — no verification credits.

Input parameters:

- `domain` (string, required): The domain to inspect, e.g. example.com

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/verifyanyemail-verifyanyemail-mcp/verifyanyemail-mcp#diagnostics

## Score history

- 2026-11-05: 66
- 2026-11-04: 66
- 2026-11-03: 66
- 2026-11-02: 66
- 2026-11-01: 66
- 2026-10-31: 66
- 2026-10-30: 51

## Common questions

### What is the VerifyAnyEmail MCP server?

VerifyAnyEmail is an MCP server listed in the public MCP registry as io.github.verifyanyemail/verifyanyemail-mcp. Real-time email verification and deliverability diagnostics (MX, SPF, DKIM, DMARC). This page covers its npm package (verifyanyemail-mcp).

### Is the VerifyAnyEmail MCP server safe to use?

VerifyAnyEmail scores 66 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the VerifyAnyEmail MCP server expose?

VerifyAnyEmail exposes 9 tools: verify_email, verify_batch, get_batch_status, get_batch_results, check_mx, and 4 more. Their descriptions and schemas cost roughly 711 tokens of context every time the server is loaded.

### Is the VerifyAnyEmail MCP server still maintained?

VerifyAnyEmail is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the VerifyAnyEmail MCP server under?

VerifyAnyEmail declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/verifyanyemail-mcp
- Socket report: https://socket.dev/npm/package/verifyanyemail-mcp
- Repository: https://github.com/verifyanyemail/verifyanyemail-mcp
- Website: https://verifyany.email/mcp
- Changelog RSS feed: https://verifymcp.io/servers/verifyanyemail-verifyanyemail-mcp/verifyanyemail-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/verifyanyemail-verifyanyemail-mcp/verifyanyemail-mcp.json
- HTML version of this page: https://verifymcp.io/servers/verifyanyemail-verifyanyemail-mcp/verifyanyemail-mcp