Mail7 Email Validation vs Agent Email

A side-by-side look at the Mail7 Email Validation and Agent Email MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Mail7 Email Validation logoMail7 Email ValidationCommunication · Local subprocess (stdio)Verify email addresses, clean lists, and audit a domain SPF, DKIM, DMARC and MX setup.56GoodAuth: not declaredAgent Email logoAgent EmailCommunication · Local subprocess (stdio)Local email connectivity for AI agents — read, draft, send, and organize Outlook mail via MCP65GreatAuth: not declared

Verdict: choose Mail7 Email Validation for communication work as a local process; choose Agent Email for communication as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Mail7 Email Validation logoChoose Mail7 Email Validation when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: MAIL7_API_KEY, MAIL7_BASE_URL.
  • You want tools like validate_email, validate_emails, check_domain.
Explore Mail7 Email Validation

Agent Email logoChoose Agent Email when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like list_emails, read_email, search_emails.
Explore Agent Email

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMail7 Email Validation logoMail7 Email ValidationAgent Email logoAgent Email
CategoryCommunicationCommunication
Quality signal56/100 · Good65/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsMAIL7_API_KEYMAIL7_BASE_URLNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars06
Directory activity 2 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
Tools427

Tools & capabilities

Mail7 Email Validation tools 4

  • validate_emailCheck 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.
  • validate_emailsCheck 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.
  • check_domainAudit 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.
  • check_spfFetch 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.

Agent Email tools 27

  • list_emailsList recent emails with filtering by unread status, folder, sender, and limit. Use offset for pagination. A row with `isDraft: true` is an unsent draft — it has NOT been sent, and its `receivedAt` is provider-supplied metadata, not evidence of delivery. Never describe such a row as a sent, delivered, or received email.
  • read_emailRead the full content of an email by ID, transformed to token-efficient markdown. When the response has `isDraft: true` the message is an unsent draft — it has NOT been sent, and `receivedAt` is provider-supplied metadata, not evidence of delivery; never describe it as a sent, delivered, or received email. Set format to 'html' to get the raw body HTML instead of markdown — use this when you need to preserve inline styling (colour, background-colour, underline, strikethrough) that the markdown conversion discards, e.g. to change one sentence of a formatted body and leave the rest alone. Raw HTML costs far more tokens than markdown, so leave the default alone unless you need the styling; check `bodyFormat` (`text` means the message had no HTML part, so do not send it as HTML) before writing a body back, and never write one back with `bodyTruncated: true` — you do not have the whole body. strip_quoted_history and strip_signatures are markdown-shaped text transforms and are NOT applied when format is 'html'; the HTML is returned verbatim. To write it back, call create_draft/update_draft with format: 'html' AND force_black: false — force_black defaults to true and wraps your HTML in a force-black div, so leaving it on nests another wrapper on every round trip. Set strip_quoted_history to true to drop the terminal "On … wrote:" / Outlook-header / `>`-prefix reply chain and replace it with a short marker. Set strip_signatures to true to remove detected signatures and legal disclaimers; it defaults to false here for MCP compatibility even though the core action defaults to true.
  • search_emailsSearch emails using full-text query across one or all mailboxes. Use offset for pagination. Results include unsent drafts: a row with `isDraft: true` has NOT been sent — its `receivedAt` is provider-supplied metadata, not evidence of delivery. Never describe such a row as a sent, delivered, or received email.
  • get_mailbox_statusGet mailbox connection status, unread count, and warnings
  • list_mailboxesList every configured mailbox: its logical `name` (pass this as the `mailbox` argument to other tools), its `emailAddress`, provider, connection status, and which one is the default. Reports mailboxes that failed to authenticate too, so it stays useful for diagnosing a broken setup.
  • get_threadRetrieve all messages in a conversation thread by message ID. A thread can end with an unsent draft reply: a message with `isDraft: true` has NOT been sent, so it is not a sent reply — though earlier sent replies from the same author may exist elsewhere in the thread. Never describe such a message as a sent, delivered, or received email.
  • send_emailCompose and send a new email. Gated by send allowlist. Draft mode bypasses allowlist. If a send fails with SEND_STATUS_UNKNOWN, the message may already have been delivered; do not resend without checking Sent Items. An identical send repeated within the duplicate window is refused with a DUPLICATE_SEND_* code instead of delivering twice; pass allow_duplicate: true only when a human has decided to send the same message again.
  • reply_to_emailReply to an email within an existing thread. Default reply_all=true cc's the original thread; pass reply_all=false to reply only to the sender. Send path validates all effective recipients against the send allowlist; draft path bypasses. If a send fails with SEND_STATUS_UNKNOWN, the message may already have been delivered; do not resend without checking Sent Items. An identical reply repeated within the duplicate window is refused with a DUPLICATE_SEND_* code instead of delivering twice; pass allow_duplicate: true only when a human has decided to send the same reply again.
  • create_draftCreate an email draft with to/cc/bcc recipients. Supports body_file with YAML frontmatter (to, cc, bcc, subject, reply_to, format). Use reply_to for threaded reply drafts, where to and subject are derived from the parent message and may be omitted; pass reply_all=false with reply_to to draft a sender-only reply.
  • send_draftSend a previously created draft. Enforces send allowlist before sending. Rate-limited. If a send fails with SEND_STATUS_UNKNOWN, the message may already have been delivered; do not resend without checking Sent Items. Sending the same draft id twice within the duplicate window is refused with a DUPLICATE_SEND_* code instead of delivering twice; pass allow_duplicate: true only when a human has decided to send it again.
  • update_draftUpdate a draft email. Body edits are refused for reply drafts; non-reply body edits require replace_body=true and replace the body wholesale. Subject, recipients (to/cc/bcc), and attachments remain editable. Allowlist is enforced at send_draft time, not here.
  • cancel_scheduled_sendCancel a pending provider-held scheduled send. Only verified scheduled drafts can be cancelled.
  • +15 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Mail7 Email Validation

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mail7-email-validation": {
      "command": "npx",
      "args": [
        "-y",
        "mail7-mcp"
      ],
      "env": {
        "MAIL7_API_KEY": "YOUR_MAIL7_API_KEY_HERE",
        "MAIL7_BASE_URL": "YOUR_MAIL7_BASE_URL_HERE"
      }
    }
  }
}

Agent Email

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "agent-email": {
      "command": "npx",
      "args": [
        "-y",
        "email-agent-mcp"
      ]
    }
  }
}

Frequently asked questions

Mail7 Email Validation is categorized under Communication and uses a local stdio subprocess. Agent Email belongs to Communication and uses a local stdio subprocess. Pick Mail7 Email Validation for communication work and Agent Email for communication.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Mail7 Email Validation has no declared pricing — check the project's own site. Agent Email has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add mail7-email-validation and agent-email as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Mail7 Email Validation has a quality signal of 56/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Agent Email has 65/100 (Great) with 4 views, 0 installs and 6 GitHub stars.