# Mail7 Email Validation (npm · mail7-mcp)

Verify email addresses, clean lists, and audit a domain SPF, DKIM, DMARC and MX setup.

- Trust score: 93/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `mail7-mcp`: 93/100 (this document), [markdown](https://verifymcp.io/servers/net-mail7-email-validation/mail7-mcp.md), [page](https://verifymcp.io/servers/net-mail7-email-validation/mail7-mcp)

## Channel facts

- Registry: `npm`
- Package: `mail7-mcp`
- Version: `0.1.1`
- 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-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to dvlop/mail7-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 38 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 560 tokens (~140/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
  - Structured output schemas are declared (50% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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.

## Install

### How do I install the Mail7 Email Validation MCP server?

Mail7 Email Validation runs locally as an npm package, launched with npx -y mail7-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 net-mail7-email-validation -- npx -y mail7-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "net-mail7-email-validation": {
      "command": "npx",
      "args": [
        "-y",
        "mail7-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "net-mail7-email-validation": {
      "command": "npx",
      "args": [
        "-y",
        "mail7-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add net-mail7-email-validation -- npx -y mail7-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add net-mail7-email-validation --command npx --arg -y --arg mail7-mcp
```

### Hermes

```yaml
mcp_servers:
  net-mail7-email-validation:
    command: "npx"
    args: ["-y", "mail7-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "net-mail7-email-validation": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mail7-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add net-mail7-email-validation -t stdio -c npx -a -y mail7-mcp
```

### Other

```json
{
  "mcpServers": {
    "net-mail7-email-validation": {
      "command": "npx",
      "args": [
        "-y",
        "mail7-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-09-20 (score 93, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 92, −3)

- [functional] Stability: pass → 0.80

### 2026-09-18 (score 95, 0)

- [security] Stability: 0.97 → pass

### 2026-09-17 (score 95, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 94, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 93, −2)

- [functional] Stability: pass → 0.83

### 2026-09-12 (score 95, 0)

- [security] Stability: 0.97 → pass

### 2026-09-11 (score 95, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `validate_email` (~128 tokens)

Validate one email address

Check whether a single email address is deliverable: syntax, domain MX records, disposable-domain database and a live SMTP mailbox probe. Status is one of "Valid", "Not Valid", "Unknown". Unknown means the mailbox could NOT be checked (catch-all domain, greylisting, blocked SMTP port) - it is NOT a bad address. Never delete, reject or report Unknown addresses as invalid; present them separately and let the user decide. Use validate_emails instead when you have more than one address.

Input parameters:

- `email` (string, required): The email address to check, e.g. user@example.com

Output parameters:

- `details` (string|null)
- `email` (string)
- `formatValid` (boolean)
- `is_disposable` (boolean|null)
- `mxValid` (boolean)
- `smtpValid` (boolean)
- `status` (string)
- `valid` (boolean|null): true = deliverable, false = does not exist, null = Unknown

### `validate_emails` (~186 tokens)

Validate a list of email addresses

Check up to 50 email addresses in one call and get a per-address verdict plus a summary. Status is one of "Valid", "Not Valid", "Unknown". Unknown means the mailbox could NOT be checked (catch-all domain, greylisting, blocked SMTP port) - it is NOT a bad address. Never delete, reject or report Unknown addresses as invalid; present them separately and let the user decide. Requires MAIL7_API_KEY (anonymous callers get a 25-address free sample only). Each address takes a few seconds of real SMTP work, so this call is slow by nature: for a longer list, split it and call this tool repeatedly with the next 50 addresses. Never run two calls in parallel - the API serialises one bulk job per client and the second call fails.

Input parameters:

- `emails` (array, required): The addresses to check, at most 50 per call

Output parameters:

- `note` (string)
- `partial` (boolean): true when the list was cut short (free anonymous sample or a limit was hit)
- `results` (array)
- `summary` (object)

### `check_domain` (~179 tokens)

Check a domain mail configuration

Audit a domain's email setup in one call: MX records, SPF, DKIM, DMARC, MTA-STS, TLS-RPT, DNSSEC and BIMI, graded A-F with a fix for every problem found. Use this to answer "can this domain send and receive mail" or "why do our messages land in spam". Takes a domain (example.com), not an email address. The default answer summarises every section; pass `section` to get the full records and findings of one of them.

Input parameters:

- `dkim_selector` (string): Optional DKIM selector to look up, e.g. "google" or "s1". Omit if unknown.
- `domain` (string, required): Domain to check, e.g. example.com
- `section` (string): Drill into a single section instead of the whole summary

### `check_spf` (~67 tokens)

Check a domain SPF record

Fetch and analyse the SPF record of a domain: the raw record, its mechanisms, lookup count and common misconfigurations. Use check_domain instead when the question is about overall deliverability rather than SPF specifically.

Input parameters:

- `domain` (string, required): Domain to check, e.g. example.com

## Diagnostics

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

## Score history

- 2026-09-20: 93
- 2026-09-19: 92
- 2026-09-18: 95
- 2026-09-17: 95
- 2026-09-16: 94
- 2026-09-15: 94
- 2026-09-14: 93
- 2026-09-13: 93
- 2026-09-12: 95
- 2026-09-11: 95
- 2026-09-10: 94
- 2026-09-09: 94
- 2026-09-08: 93
- 2026-09-07: 93
- 2026-09-06: 92
- 2026-09-05: 92
- 2026-09-04: 91
- 2026-09-03: 91
- 2026-09-02: 91
- 2026-09-01: 90
- 2026-08-31: 90
- 2026-08-30: 89
- 2026-08-29: 89
- 2026-08-28: 88
- 2026-08-27: 88
- 2026-08-26: 87
- 2026-08-25: 86
- 2026-08-24: 85
- 2026-08-23: 85
- 2026-08-22: 84

## Common questions

### What is the Mail7 Email Validation MCP server?

Mail7 Email Validation is an MCP server listed in the public MCP registry as net.mail7/email-validation. Verify email addresses, clean lists, and audit a domain SPF, DKIM, DMARC and MX setup. This page covers its npm package (mail7-mcp).

### Is the Mail7 Email Validation MCP server safe to use?

Mail7 Email Validation scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Mail7 Email Validation MCP server expose?

Mail7 Email Validation exposes 4 tools: validate_email, validate_emails, check_domain, check_spf. Their descriptions and schemas cost roughly 560 tokens of context every time the server is loaded.

### Is the Mail7 Email Validation MCP server still maintained?

Mail7 Email Validation is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Mail7 Email Validation MCP server under?

Mail7 Email Validation 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/mail7-mcp
- Socket report: https://socket.dev/npm/package/mail7-mcp
- Repository: https://github.com/dvlop/mail7-mcp
- Website: https://mail7.net/integrations/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/net-mail7-email-validation/mail7-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/net-mail7-email-validation/mail7-mcp.json
- HTML version of this page: https://verifymcp.io/servers/net-mail7-email-validation/mail7-mcp