Mail7 Email Validation

net.mail7Published by mail7.netv0.1.1Updated Oct 24, 2026

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

The publisher's own server: email-validation.org email validation

VerifiedSTDIODesktop onlyCommunication & CollaborationSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant verify email addresses, clean address lists, and audit a domain's SPF, DKIM, DMARC and MX mail configuration.

What you can do
Provides four tools: validate_email checks one address for syntax, MX, disposable domains and a live SMTP mailbox probe; validate_emails handles up to 50 addresses per call with a Valid / Not Valid / Unknown summary; check_domain audits a domain's mail configuration and grades it A-F; check_spf reports the SPF record, mechanisms, lookup count and misconfigurations. Results come back as text plus structured fields, and check_domain can be re-called with a section argument for raw records.
When to use it
Useful when an assistant needs to check whether an address is a real mailbox, clean a signup or marketing list, or diagnose why a domain's mail lands in spam. It fits list hygiene and domain mail-configuration troubleshooting rather than general email sending.
Requirements
Runs locally over stdio via npx, so Node 18 or newer is required and no install step is needed. An API key in MAIL7_API_KEY is optional but anonymous callers are limited to 5 checks per minute and a 25-address bulk sample. MAIL7_BASE_URL can override the default API endpoint. Network access to the Mail7 API is needed.
Before you install
The server sends addresses and domain names to the Mail7 API for checking, so treat submitted data as shared with a third party. MAIL7_API_KEY is a secret and should be supplied through the environment rather than committed to config files. Checks are live SMTP conversations and take seconds each; bulk calls are capped at 50 addresses and should not be run in parallel.

Installation

In SourceWeft

  1. Open Mail7 Email Validation in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Mail7 MCP server

Email validation for AI assistants. This is an MCP server that gives Claude, Cursor, Windsurf, Cline and any other MCP client four tools: verify a single address, clean a list, check a domain's SPF record, and audit a domain's whole mail configuration.

Honest by design: Mail7 answers Valid, Not Valid or Unknown, and the tool descriptions tell the model in plain words that Unknown means "could not be verified", not "bad". An assistant using this server will not silently delete addresses it could not check.

Install

Node 18+ required. No install step - the server runs through npx.

Claude Code

bash
claude mcp add mail7 --env MAIL7_API_KEY=your_key -- npx -y mail7-mcp

Claude Desktop (claude_desktop_config.json), Cursor (~/.cursor/mcp.json), and most other clients use the same shape:

json
{  "mcpServers": {    "mail7": {      "command": "npx",      "args": ["-y", "mail7-mcp"],      "env": { "MAIL7_API_KEY": "your_key" }    }  }}

Get an API key at mail7.net/account. The server also runs without one, but anonymous callers are limited to 5 checks per minute and a 25-address free bulk sample - not enough for real work.

VariableDefaultPurpose
MAIL7_API_KEY-Raises rate limits, unlocks full bulk validation
MAIL7_BASE_URLhttps://mail7.net/apiOverride the API endpoint

Tools

ToolWhat it does
validate_emailOne address: syntax, MX, disposable-domain check, live SMTP mailbox probe
validate_emailsUp to 50 addresses per call, with a Valid / Not Valid / Unknown summary
check_domainFull mail-config audit graded A-F: MX, SPF, DKIM, DMARC, MTA-STS, TLS-RPT, DNSSEC, BIMI
check_spfSPF record, mechanisms, lookup count and misconfigurations

Ask your assistant things like:

  • "Is [email protected] a real mailbox?"
  • "Clean this list of signups and tell me which ones bounce."
  • "Why do our emails to customers land in spam? Check ourdomain.com."

How results are shaped

validate_email and validate_emails return structured content alongside the text, so a client that supports structured tool output gets typed fields:

jsonc
{  "email": "[email protected]",  "status": "Unknown",        // "Valid" | "Not Valid" | "Unknown"  "valid": null,              // true | false | null (null = Unknown)  "formatValid": true,  "mxValid": true,  "smtpValid": false,  "is_disposable": false,  "details": "Server accepts all addresses (catch-all) - status unknown"}

check_domain returns a compact graded summary with a fix for every problem. To see the raw records of one part, call it again with section set to mx, spf, dkim, dmarc, mta_sts, tls_rpt, dnssec, bimi or domain.

Notes for large lists

Every address is a live SMTP conversation, so a check takes seconds, not milliseconds. validate_emails caps at 50 addresses per call on purpose - call it repeatedly with the next chunk rather than pushing a whole file through one call, and never run two calls in parallel (the API serialises one bulk job per client).

Development

bash
npm installnpm run build      # -> dist/node dist/index.js # speaks MCP over stdio

License

MIT. Part of the Mail7 integrations.

Source: README.md at commit b03ac76

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Email-Validation integrations

email-validation.org email validation

org.email-validationOfficial publisher

email-validation.org email validation's hosted MCP server, published by email-validation.org; credential required; Streamable HTTP.

Streamable HTTPWeb executableAuth
Credential requiredOct 26, 2026

NoBounce Email Validation

Published by GitHub account notprathap

Remote NoBounce server that lets an assistant validate single email addresses or bulk lists in real time for syntax, MX, disposable domains and more.

Streamable HTTPWeb executableAuth
Data & Analytics2 toolsOct 30, 2026

Mailvett: Email Validation API for AI Agents

dev.workers.cybermax-tools.cybermax

A remote MCP endpoint that lets an assistant validate email addresses, checking MX records, provider, disposable/role/free flags, typos and an overall verdict.

Streamable HTTPWeb executable
Communication & CollaborationNot indexed yetOct 24, 2026

Mailvett: Email Validation API for AI Agents

Published by GitHub account CyberMax-tools

A remote MCP endpoint that lets an assistant validate email addresses, checking MX records, provider, disposable/role/free flags, typo fixes and an overall pass

Streamable HTTPWeb executable
Communication & CollaborationNot indexed yetOct 24, 2026

Mailvett: Email Validation API for AI Agents

Published by GitHub account shawmena-dotcom

A remote MCP server that lets an assistant validate up to 10 email addresses at a time, returning a verdict, score and deliverability signals.

Streamable HTTPWeb executable
Communication & Collaboration1 toolOct 24, 2026