mailverdict

dev.mailverdict由 mailverdict.dev 发布官方发布者v0.1.1更新于 Oct 28, 2026

Keyless email checks: disposable, role, and free-provider detection, MX, and typo suggestions.

已验证Streamable HTTP可网页运行开发者工具安全与监控

概览

AI 生成的概览

无需密钥的远程 MCP 服务器,让助手检查邮箱地址和域名的临时邮箱、角色账号、免费邮箱、MX 记录与拼写建议。

可以做什么
  • 检查邮箱地址的语法、一次性/临时域名、角色账号、免费邮箱服务商、拼写建议与 MX 记录,返回结果、原因、0-100 评分及各信号布尔值
  • 检查域名的临时邮箱名单归属、免费服务商状态、拼写建议与 MX 记录
  • 在不愿外发完整地址时,仅对域名做筛查
适用场景
适合在搭建或审查注册与表单校验流程时,让助手判断某个地址是否像临时邮箱、info@ 这类角色邮箱,或真实域名的拼写错误。它面向应用内的逐条校验,而非批量清洗名单。
运行要求
远程 Streamable HTTP 端点 api.mailverdict.dev/mcp;未声明注册、API 密钥或请求头。项目内另有本地 stdio 版本,需要 Node 20 或更高版本。MX 查询经由公共 DNS-over-HTTPS 解析器,需要网络访问。
安装前请注意
结果只是基于公开黑名单的启发式建议,会出现误判,不要凭单个布尔值直接封禁用户。托管服务免费、尽力而为、无 SLA,并按 IP 限流,禁止用于批量清洗购买或抓取的名单。仅查域名可不发送本地部分,但完整邮箱检查会把地址发送给该服务。

安装

在 SourceWeft 中

  1. 打开 控制台中的 mailverdict,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

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

交给智能体安装

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

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

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

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "mailverdict": {
      "type": "http",
      "url": "https://api.mailverdict.dev/mcp"
    }
  }
}

README

mailverdict

Email intelligence API: disposable/burner detection, role-account detection, free-provider classification, MX validation, and typo suggestions. Keyless and free at the entry tier, built to be the email-check dependency that coding agents reach for when they scaffold a signup flow.

API: https://api.mailverdict.dev · npm: mailverdict · Freshness feed ("Burner Feed"): GET /v1/changes

Why this exists

Every SaaS signup form needs the same three answers — is this a burner? is this a person or a mailbox like info@? did they typo their domain? — and the current options are stale GitHub lists you have to vendor yourself or paid validators gated behind signup. The value here is not the code (it's small on purpose): it's the maintained dataset — burner domains churn daily, and this repo rebuilds its dataset from every maintained public source on a daily schedule, plus its own discovery over time.

Quickstart

bash
npm installnpm run build:data   # fetch + merge upstream lists into data/dataset.jsonnpm testnpm run dev          # http://localhost:8787

Requires Node >= 20.

bash
curl "localhost:8787/v1/[email protected]"
json
{  "email": "[email protected]",  "user": "jane",  "domain": "mailinator.com",  "tag": null,  "normalized_email": "[email protected]",  "result": "risky",  "reason": "disposable_email",  "score": 5,  "valid_syntax": true,  "disposable": true,  "disposable_match": "mailinator.com",  "role": false,  "free": false,  "mx_found": true,  "mx_records": ["mail2.mailinator.com"],  "did_you_mean": null,  "accept_all": null}

Response follows the Kickbox/Emailable industry convention (result, reason, bare booleans, did_you_mean = full corrected address, score 0–100) so code written against those APIs ports with near-zero edits.

Endpoints: GET /v1/check?email= · GET /v1/check/{email} · POST /v1/check (batch ≤100) · GET /v1/domain/{domain} · GET /v1/changes?since=24h (freshness feed) · GET /v1/meta · /llms.txt · /openapi.yaml. Add mx=false to skip the DNS lookup.

Privacy-conscious default: if you only need burner/typo screening, check the domain (/v1/domain/{domain}) — no email address leaves your system. Use the full email check when you need role detection or normalization.

SDK: living data with a static safety net

sdk/ packages the integration story: call the live API, fall back to a bundled offline snapshot on timeout/failure — fresher than a vendored static list, but never a hard runtime dependency in your signup path.

ts
import { createClient } from 'mailverdict'const check = await createClient().checkEmail(input)if (check.disposable) reject()          // check.source: 'live' | 'snapshot'

Published on npm as mailverdict; see sdk/README.md.

MCP server

Hosted, keyless remote server — point any MCP client at:

POST https://api.mailverdict.dev/mcp

Stateless Streamable HTTP (JSON-RPC 2.0), no signup or key. Tools: check_email, check_domain.

A stdio server also ships for local use:

bash
npm run mcp   # stdio transport; tools: check_email, check_domain

Register the local one in Claude Code: claude mcp add mailverdict -- npx tsx src/mcp.ts (run from this directory).

Architecture

pipeline/build.ts     daily: fetch upstream lists -> merge/dedupe -> apply                      allowlist -> data/dataset.json + data/meta.jsonsrc/lib/*             pure logic: parse, classify, suggest, MX-over-DoHsrc/app.ts            Hono app (runtime-agnostic)src/server.ts         Node entry (self-hosting)src/worker.ts         Cloudflare Workers entry (production: api.mailverdict.dev)src/mcp.ts            MCP stdio server for coding agents.github/workflows/    daily dataset refresh + auto-commit

DNS is done over DoH (cloudflare-dns.com) so the same code runs on Node and edge runtimes. Subdomains match their parents (foo.mailinator.com → mailinator.com).

Data sources & attribution

The dataset aggregates these excellent permissively-licensed community lists — see data/meta.json for per-source counts, status, and license on every build (unlicensed and GPL lists are deliberately excluded):

Merge precedence (important — the free-provider list contains temp-mail domains and typo-squats like mailinator.com and gmial.com): allowlists rescue from disposable, then disposable wins over free.

Roadmap

mailverdict is built agent-first: the first call works with zero signup, the docs are operable by coding agents (/llms.txt, OpenAPI), and the dataset's freshness is provable via the Burner Feed rather than claimed.

  • Keyless free API — the first call works with zero signup
  • Industry-compatible response shape (Kickbox/Emailable convention: result, reason, did_you_mean, bare booleans)
  • llms.txt (agent-operable: endpoint-first, curl-able), OpenAPI spec
  • MCP server — local stdio and hosted keyless remote (Streamable HTTP) at /mcp
  • Daily automated dataset refresh + auto-deploy
  • Freshness changelog + /v1/changes feed (clean-build diffs only; 90-day retention)
  • SDK with bundled snapshot fallback, published on npm (mailverdict)
  • Production deployment on Cloudflare Workers (api.mailverdict.dev)
  • Official MCP registry listing (dev.mailverdict/mailverdict)
  • Per-IP rate limiting
  • Detection-lag benchmark: measure and publish how quickly new burner domains enter the dataset
  • Better Auth plugin (keyless check in the before-create hook)
  • Framework snippets (Zod .refine(), React Hook Form, server actions)
  • Optional API keys for high-volume / commercial use

Status

v0.1.1 — live at https://api.mailverdict.dev (Cloudflare Workers), with a hosted keyless remote MCP server at /mcp and an official MCP registry listing. The dataset refreshes and redeploys daily via GitHub Actions, and the mailverdict SDK is published on npm. 41 tests cover the core logic, HTTP layer, MCP handler, and SDK live/fallback paths.

Disclaimers, privacy & fair use

  • Advisory signals, not verdicts. Classifications aggregate public blocklists and heuristics; false positives happen (domains churn, upstream lists disagree). Don't hard-block users on a single boolean — combine with your own signals and give flagged users a path forward.
  • Wrongly listed? If your domain is misclassified, open a misclassified-domain report. Allowlist corrections ship with the next daily build, and fixes are submitted upstream when a source list is at fault.
  • Privacy. No accounts, no logging of email addresses, nothing stored per request. MX checks send only the domain (never the local part) to a public DNS-over-HTTPS resolver. Traffic metrics are aggregate and PII-free.
  • No SLA. The hosted API is free and best-effort while in beta. If your signup flow must never block on us, use the SDK (it falls back to a bundled offline snapshot) or self-host — see docs/deploy.md.
  • Fair use. Built for signup and form validation inside applications. Do not use it to bulk-clean purchased or scraped mailing lists; per-IP rate limits apply and abusive traffic gets blocked.

Commercial use & higher limits

The hosted API is free with per-IP rate limits. Need higher throughput, an SLA, or commercial terms? Email [email protected].

License

MIT — see LICENSE; it covers the code and dataset pipeline. The hosted service at api.mailverdict.dev is provided "as is", without warranty of any kind. The aggregated dataset sources carry their own permissive licenses, recorded per-source in data/meta.json.

来源:README.md,提交 d79c2b4

工具

2

check_email

Check an email address: syntax, disposable/burner domain, role account, free provider, typo suggestion, MX records. Returns result (deliverable|undeliverable|risky|unknown), reason, score 0-100, and per-signal booleans.

输入参数mxemail必填

check_domain

Check a domain: disposable/burner list membership, free-provider status, typo suggestion, MX records.

输入参数mxdomain必填

版本历史

1
  1. v0.1.1最新Sep 16, 2026

评分

已满足适用检查项的 100%

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

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