emailmd
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Fix email that lands in spam: SPF, DKIM, DMARC checks, exact DNS fix records, propagation, alerts.
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 40/100 | 热度 20 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-11-18 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 5/5 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 DNS Doctor - Email & DMARC。按照 https://mcp.popnx.com/i/dnsdoctor-dns-doctor.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(dnsdoctor.dev) · ✓ 命令已检查 2026年11月18日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
DNS Doctor - Email & DMARChttps://dnsdoctor.dev/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsDNS Doctor - Email & DMARC
用 DNS Doctor - Email & DMARC 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 DNS Doctor - Email & DMARC,或回答中出现 DNS Doctor - Email & DMARC 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
DNS Doctor - Email & DMARChttps://dnsdoctor.dev/mcp开启新聊天,输入前先从插件列表中选择 DNS Doctor - Email & DMARC
用 DNS Doctor - Email & DMARC 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 DNS Doctor - Email & DMARC,或回答中出现 DNS Doctor - Email & DMARC 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user dns-doctor https://dnsdoctor.dev/mcp应能看到 DNS Doctor - Email & DMARC 在列表中并显示已连接
用 DNS Doctor - Email & DMARC 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 DNS Doctor - Email & DMARC,或回答中出现 DNS Doctor - Email & DMARC 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 DNS Doctor - Email & DMARC 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 DNS Doctor - Email & DMARC,或回答中出现 DNS Doctor - Email & DMARC 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 DNS Doctor - Email & DMARC 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 DNS Doctor - Email & DMARC,或回答中出现 DNS Doctor - Email & DMARC 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://dnsdoctor.dev/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user dns-doctor https://dnsdoctor.dev/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"dns-doctor": {
"url": "https://dnsdoctor.dev/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"dns-doctor": {
"type": "http",
"url": "https://dnsdoctor.dev/mcp"
}
}
}Claude Code
claude mcp add --scope user dns-doctor -- npx -y @dnsdoctor/mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"dns-doctor": {
"command": "npx",
"args": [
"-y",
"@dnsdoctor/mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"dns-doctor": {
"command": "npx",
"args": [
"-y",
"@dnsdoctor/mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"dns-doctor": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@dnsdoctor/mcp"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
工具名称和描述与服务器在 2026年11月18日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
scan_domainUse this when the user asks to check, audit, diagnose or troubleshoot SPF, DKIM, DMARC, email authentication, email deliverability DNS, why their mail lands in spam, MX, DNS health, blacklist status, or domain/SSL expiry for a domain, or wants to fix what a scan finds (fix record
get_reportUse this for the same questions as scan_domain when a recent report is enough (the cheap first look); use scan_domain when the state must be re-read now. Return the stored report for a domain, scanning once only if none exists yet — the cheap read, and the right default for a fir
build_dmarc_upgradeUse this when the user asks how to move DMARC on from p=none, whether it is safe to tighten DMARC, or what the next DMARC policy step is for a domain (a scan can justify quarantine at most; reject needs monitoring evidence) — and after any report showing DMARC below enforcement.
start_monitoring_signupUse this when the user asks for ongoing DMARC monitoring, RUA report monitoring, new-sender monitoring, email-authentication alerts, ongoing DNS monitoring, or website uptime monitoring and down alerts for a domain they own (a verified domain's website is checked from five locati
count_spf_lookupsUse this when the user asks about SPF 'too many lookups', the 10-lookup limit, an SPF PermError, or whether an SPF record is valid. Validate an SPF record and count what it costs. Returns `record_valid` (the record parses as RFC 7208 SPF), `findings` (per-term diagnostics), `has_
validate_dmarc_recordUse this when the user pastes a DMARC record and asks whether it is valid, correct or safe. Validate a pasted DMARC record: parsed tags, level'd findings, and whether it is valid. No DNS lookup — pass the record string itself. `upgrade_record` previews a stronger policy and is ca
generate_dmarc_recordUse this when the user asks to create, generate or write a DMARC record for a domain that has none. Build a DMARC record from scratch for a domain that has none, using a validating engine — never compose one yourself. `policy` is none|quarantine|reject; optional `rua_email` (aggr
check_dkim_selectorUse this when the user asks whether DKIM is set up for a sending platform, whether a specific selector exists, or why DKIM fails. Check ONE specific DKIM selector on a domain — the exact selector the sending platform uses (e.g. `google`, `s1`), which a full scan's common-selector
parse_dmarc_reportUse this when the user uploads or pastes a DMARC aggregate (RUA) XML report and asks what it says. Parse ONE DMARC aggregate (RUA) report into readable per-source aggregates: who sent mail as the domain, how much, and what share was SPF/DKIM aligned. Pass the file's bytes base64-
check_recordUse this when the user asks whether a DNS change has landed, wants a DNS record looked up, or wants to verify a record they just published — or whenever answering needs the live value of a record. Reads the record from the domain's OWN nameservers (cache-free) and from two public
check_reverse_dnsUse this when the user asks about reverse DNS, PTR records, or FCrDNS for a mail server IP. Check one sending IP's forward-confirmed reverse DNS (FCrDNS): reads the IP's PTR record, then resolves that hostname back and reports whether it returns to the same IP. `verdict` is confi
audit_spf_includesUse this when the user asks who can send email as their domain through SPF includes, or wants an SPF supply-chain or third-party sender audit. Audit a domain's SPF supply chain: walks every include and redirect it delegates to, and reports who can transitively send as it. Returns
build_parked_domain_recordsUse this when the user asks how to protect a domain that sends no email from being spoofed. Build the three-record hardening pack that makes a NON-SENDING domain unusable for spoofing: a Null MX, a hard-fail SPF record, and a p=reject; np=reject DMARC record. For parked, redirect
check_propagationUse this when the user asks whether a DNS change has propagated globally, or why a record shows in one place and not another. Check whether a DNS change has propagated GLOBALLY: six vantage points (five owner-run probes across four continents plus this server's own resolver) each
lookup_registrationUse this when the user asks who owns a domain, when it expires, which registrar or nameservers it has, whether it is registered, or whether a transfer or delete lock is set — the WHOIS question. Read a domain's registration from the registry over RDAP: registrar (with IANA id), r
get_alertsUse this when a signed-in operator asks what changed on a monitored domain, whether its website went down, or what the monitoring has flagged. Read the monitoring alert log for the domains the caller's account monitors, newest first, including website uptime incidents (site_down,
get_readinessUse this when a signed-in operator asks whether a monitored domain is ready for the next DMARC step. Read the DMARC enforcement-readiness verdict for ONE domain the caller's account monitors, computed from its aggregate (RUA) report window. Needs a connected DNS Doctor account or
list_my_domainsUse this when a signed-in operator asks which domains their DNS Doctor account monitors, or what to do next on them. Lists every domain on the caller's account with its state — verified, pending (added, ownership not proven yet) or verification_lapsed (the ownership record was re
check_lookalikesUse this when the user asks about lookalike, look-alike, typosquat or impersonation domains of their domain, or whether someone has registered a name close to theirs. DNS-only: checks the closest variants of the name and returns facts — how many resolve and how many accept mail,
get_lookalikesUse this when a signed-in operator asks which lookalike domains of a monitored domain the watch has found, how risky they are, or for one's takedown evidence. Needs a connected DNS Doctor account or an API token with monitoring:read. Returns the account's watched lookalikes for O
start_email_testUse this when the user wants to know how a real email from them actually authenticates — whether a message from Google Workspace, Microsoft 365, a newsletter tool or an app is SPF/DKIM/DMARC aligned, why it lands in spam, or to prove DKIM signing works before tightening DMARC. Re
get_email_testUse this after start_email_test, once the user says they sent the email. Returns status pending | received | expired | error. pending means the message has not arrived (or is still being checked): ask the user to send it if they have not, then call again. received carries result:
list_email_testsUse this when a signed-in user asks about email tests they ran before, or how a sender's earlier tests scored. Needs a connected DNS Doctor account or an API token with monitoring:read. Returns the account's own tests, newest first (optionally only those whose From names one orga
check_bimiUse this when the user asks how to get their logo shown in Gmail, Yahoo, Apple Mail or other inboxes (BIMI), whether their BIMI setup works, or why their logo does not show. A live read of one host's BIMI setup: the DMARC gate (BIMI needs p=quarantine or p=reject; dmarc_sources n
add_monitored_domainAdd a domain to the signed-in user's DNS Doctor monitoring and return the ownership-check TXT record they must publish, plus where their DNS is hosted, a provider-specific guide link and, when their provider supports it, a one-click apply URL. Re-adding a domain they already moni
check_domain_verificationUse this only for DNS Doctor's own ownership TXT challenge on a domain the user already added to their DNS Doctor account (add_monitored_domain). For a TXT record another service asked for (Google Workspace, Microsoft 365, Shopify or any site verification), use check_record inste
get_domain_recordsRead the records a domain the user monitors still needs: the ownership check while it is unverified, and once verified the DMARC reporting record plus whether we have OBSERVED that record published. Read-only: it issues nothing — if a verified domain comes back with no reporting
watch_record_changeUse this when the user asks to be told when a DNS change they are making has finished ("let me know when it's live"). Starts a free watch on ONE record for the signed-in user: DNS Doctor rechecks it every 10 minutes for up to 48 hours with the same verdict as check_record and sen
check_domain_namesUse this when the user is choosing a domain name and wants to know which candidates are already registered. Pass up to 20 candidate names in ONE call (never one call per name). Each name is read live from its registry over RDAP: status is registered | not_registered | unknown. re
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过域名 dnsdoctor.dev 验证(注册中心会核实域名所有权)
代码最后更新于昨天
使用 Apache-2.0
在 221 毫秒内响应(HTTP 200)
无需登录
已读取 29 个工具描述,未发现针对 AI 的隐藏指令
云端地址最近 4 次检查中有 4 次响应 · 最近一次 221 ms · 检查于 2026年11月18日
尚未检查
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/dnsdoctor-dns-doctor)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于昨天,最新版本(1.22.0)于昨天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Build and fix Discord bots from a chat. Kite hosts them 24/7, with no code to deploy.
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.
CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.
| 本项 DNS Doctor - Email & DMARC | emailmd | Kite Discord Bot Builder | e2a — email for AI agents | Infobip MCP | kernelCAD | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 是 | 否 |
| 基础检查 | 5/5 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | Apache-2.0 | MIT | AGPL-3.0 | Apache-2.0 | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A thin MCP server that runs on your machine and calls the public DNS Doctor REST API. It exposes the same 29 tools as the hosted server at https://dnsdoctor.dev/mcp: scan a domain's email authentication (SPF, DMARC, DKIM), MX, DNS health, blacklists and domain/SSL expiry, check propagation, and get the exact fix record to publish.
It holds no diagnosis logic of its own and relays every record string verbatim. Every fix record comes from DNS Doctor's deterministic engine, never from a model guess.
Most clients should use the hosted server instead (no install, no keys):
{ "mcpServers": { "dns-doctor": { "type": "http", "url": "https://dnsdoctor.dev/mcp" } } }
For Claude Code, the DNS Doctor plugin wires the hosted server and adds the skills.
{
"mcpServers": { "dns-doctor": { "command": "npx", "args": ["-y", "@dnsdoctor/mcp@1.21.1"], "env": { "DNSDOCTOR_API_TOKEN": "dnsd_YOUR_TOKEN" } } } }
Node 20 or newer. Pin the version as shown, so the code you run is the code you reviewed.
DNSDOCTOR_API_TOKEN is optional. Anonymous access covers scanning and fixes; the account tools (monitored domains, alerts, readiness, lookalike watches, email tests) need a token. Create one at dnsdoctor.dev under Settings > API tokens. The client sends it only to dnsdoctor.dev, as a bearer token. Never commit it.DNSDOCTOR_API_BASE overrides the origin. It must serve the /api/... paths, i.e. the public site rather than a bare backend port.npm ci
npm test npm run build # -> dist/index.js, the package's bin entrypoint
tools.json and instructions.txt are generated from the hosted server and pinned by a test on the server side: never hand-edit them, and never add a tool description to src/. Both ship in the npm tarball; without them the client has no tools and none of its safety guidance.
Apache-2.0