VerifyAnyEmail

io.github.verifyanyemail由 GitHub 账号 verifyanyemail 发布v1.2.3更新于 Oct 30, 2026

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

已验证Streamable HTTP可网页运行安全与监控商业与电商

概览

AI 生成的概览

VerifyAnyEmail 可验证邮箱地址是否真实、可安全投递，并诊断域名的 MX、SPF、DKIM 与 DMARC 配置。

可以做什么
  • 验证单个邮箱地址，返回可投递性结论、0–100 置信度、是否可安全发送以及 catch-all、一次性、角色邮箱等信号
  • 提交大量地址进行异步批量验证，轮询批次状态并分页获取结果
  • 查询域名的 MX 记录及是否可接收邮件
  • 检查 SPF、DMARC、DKIM 记录并标记常见配置错误
  • 执行综合域名健康检查，汇总 MX、SPF、DKIM、DMARC 并给出评级与问题清单
适用场景
适合需要清洗或筛选邮箱名单、在发送前筛查注册邮箱、或在营销活动前审查域名发信配置的场景。免费的诊断工具便于在不消耗额度的情况下试用。
运行要求
需要 VerifyAnyEmail API 密钥（vae_...），通过环境变量 VERIFYANYEMAIL_API_KEY 提供。可通过 npx（Node.js）以 stdio 在本地运行，也可作为远程端点并使用 OAuth 连接。可选设置 VERIFYANYEMAIL_BASE_URL 与 VERIFYANYEMAIL_TIMEOUT_MS。需要访问 VerifyAnyEmail API 的网络。
安装前请注意
验证会消耗额度：单次验证 1 个额度，批量按每个地址 1 个额度，诊断工具免费；test.verifyany.email 下的测试地址不消耗额度。API 密钥属于机密，请妥善保护 MCP 配置文件。提交验证的地址会通过 HTTPS 发送至 VerifyAnyEmail API。

安装

在 SourceWeft 中

  1. 打开 控制台中的 VerifyAnyEmail，将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.verifyanyemail%2Fverifyanyemail-mcp/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "mcpServers": {
    "verifyanyemail": {
      "type": "http",
      "url": "https://mcp.verifyany.email/mcp"
    }
  }
}

README

VerifyAnyEmail MCP Server

Official Model Context Protocol server for VerifyAnyEmail — give any AI agent real-time email verification and deliverability diagnostics.

Works with Claude Desktop, Claude Code, Cursor, Windsurf, ChatGPT (MCP connectors), and any other MCP client.

What it does

ToolDescriptionCredits
verify_emailVerify one address — verdict (deliverable/undeliverable/risky/unknown), 0–100 score, safeToSend, and signals (catch-all, disposable, role-based, typo).1 per call
verify_batchSubmit many addresses for async bulk verification; returns a batchId.1 per address
get_batch_statusPoll a batch's progress and per-status counts.free
get_batch_resultsFetch a paginated page of batch results.free
check_mxDomain MX records / can it receive mail.free
check_spfSPF record + misconfiguration flags.free
check_dmarcDMARC policy and alignment.free
check_dkimDKIM record for a selector.free
check_domain_healthCombined MX/SPF/DKIM/DMARC health grade with findings.free

The diagnostics are free (no verification credits). Verification spends credits — except test addresses at test.verifyany.email (deliverable@, undeliverable@, risky@, unknown@), which return canned results and cost 0 credits, perfect for trying it out.

Setup

You need a VerifyAnyEmail API key (vae_…) — create one in the dashboard → API Keys.

The server is distributed on npm and runs with npx (no install needed).

Claude Desktop

Edit claude_desktop_config.json (Settings → Developer → Edit Config):

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

Restart Claude Desktop. You'll see the VerifyAnyEmail tools available.

Claude Code

bash
claude mcp add verifyanyemail -e VERIFYANYEMAIL_API_KEY=vae_your_key_here -- npx -y verifyanyemail-mcp

Cursor

Add to ~/.cursor/mcp.json (or a project .cursor/mcp.json):

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

Any other MCP client

Run the binary over stdio with the API key in the environment:

bash
VERIFYANYEMAIL_API_KEY=vae_your_key_here npx -y verifyanyemail-mcp

Configuration

Env varRequiredDefaultPurpose
VERIFYANYEMAIL_API_KEY✅—Your vae_… API key.
VERIFYANYEMAIL_BASE_URL—https://api.verifyany.emailOverride the API base URL.
VERIFYANYEMAIL_TIMEOUT_MS—30000Per-request timeout in milliseconds.

Example prompts

  • "Is [email protected] a real, safe-to-send address?"
  • "Verify these 500 signups and tell me which are risky." (uses verify_batch)
  • "Check the email deliverability health of example.com."
  • "Does example.com have a valid SPF and DMARC setup?"

Security

  • Your API key is read only from the server's environment and sent only to the VerifyAnyEmail API over HTTPS. It is never logged (logs go to stderr; the stdout stream is reserved for the MCP protocol).
  • Keep the key server-side — treat the MCP config file like any other secret.

Links

MIT © VerifyAnyEmail

来源：README.md，提交 44b0045

工具

9

verify_email

Verify Email Address

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. [email protected], undeliverable@…, risky@…, unknown@…) return canned results and cost 0 credits.

输入参数email必填smtpProbecatchAllDetection

verify_batch

Verify Emails in Bulk

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.

输入参数nameemails必填webhookUrl

get_batch_status

Get Bulk Verification Status

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

输入参数batchId必填

get_batch_results

Get Bulk Verification Results

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

输入参数pagebatchId必填pageSize

check_mx

Check MX Records

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

输入参数domain必填

check_spf

Check SPF Record

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

输入参数domain必填

check_dmarc

Check DMARC Policy

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

输入参数domain必填

check_dkim

Check DKIM Record

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

输入参数domain必填selector

check_domain_health

Check Domain Email Health

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.

输入参数domain必填

版本历史

1
  1. v1.2.3最新Oct 30, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分