Skip to main content
Glama
mail7-mcp

mail7-mcp

by dvlop

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

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:

{
  "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.

Variable

Default

Purpose

MAIL7_API_KEY

-

Raises rate limits, unlocks full bulk validation

MAIL7_BASE_URL

https://mail7.net/api

Override the API endpoint

Related MCP server: domain-security-mcp-server

Tools

Tool

What it does

validate_email

One address: syntax, MX, disposable-domain check, live SMTP mailbox probe

validate_emails

Up to 50 addresses per call, with a Valid / Not Valid / Unknown summary

check_domain

Full mail-config audit graded A-F: MX, SPF, DKIM, DMARC, MTA-STS, TLS-RPT, DNSSEC, BIMI

check_spf

SPF record, mechanisms, lookup count and misconfigurations

Ask your assistant things like:

  • "Is sales@acme.com 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:

{
  "email": "user@example.com",
  "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

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

License

MIT. Part of the Mail7 integrations.

Available Tools

4 tools
check_domainCheck a domain mail configurationA
Read-only

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.

Inputs: domain (required), section, dkim_selector.

check_spfCheck a domain SPF recordA
Read-only

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.

Inputs: domain (required).

validate_emailValidate one email addressA
Read-only

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.

Inputs: email (required). Returns: email, valid, status, details, +4 more

validate_emailsValidate a list of email addressesA
Read-only

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.

Inputs: emails (required). Returns: note, partial, results, summary

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clear and distinct purpose: validate_email for single addresses, validate_emails for batches, check_domain for comprehensive domain audits, and check_spf for SPF-specific analysis. The slight overlap between check_domain and check_spf is explicitly addressed in the descriptions.

    Naming Consistency5/5

    All tool names follow the verb_noun pattern (validate_email, validate_emails, check_domain, check_spf) with consistent snake_case and clear action verbs.

    Tool Count5/5

    Four tools is well-scoped for an email validation and domain checking server, providing just the right amount of functionality without redundancy.

    Completeness5/5

    The surface covers both email validation (single and batch) and domain deliverability checks (comprehensive via check_domain, specific via check_spf). No obvious dead ends or missing operations for the stated purpose.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Email-deliverability tools for AI agents — 12 MCP tools across email verification, DNSBL across 50 zones, SPF/DKIM/DMARC analysis, spam-trap scoring, domain intelligence, and email finder. Free tier with no credit card.
      12
      35 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to verify email addresses in real-time, checking syntax, DNS, MX records, and SMTP handshake, returning verdicts and deliverability scores without sending actual emails.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to verify email deliverability and check mailbox existence, manage bulk verification batches, and monitor verification credit balances directly from chat.
      6
      1
      MIT