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 分