DNS Doctor plugin for Claude Code — skill + MCP server for email-deliverability
DNS Doctor plugin for Claude Code — skill + MCP server for email-deliverability diagnosis with validated fix records
active Production-safe Score 93/100 http no auth
At a glance
| Endpoint | https://dnsdoctor.dev/mcp |
|---|---|
| Source | https://github.com/dnsdoctor/claude-plugin |
| Transport | http |
| Tools | 29 |
| Auth | none |
| First seen | 2026-09-02 04:18:44 |
| Last checked | 2026-11-17 21:50:52 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 453 / 706 ms |
| Last successful check | 2026-11-17 21:50:52 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (29)
scan_domain— Use this when the user asks to check, audit, diagnose or troubleshoot SPF, DKIM, DMARC, email authentication, email deliverability DNS, whyget_report— Use 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 bebuild_dmarc_upgrade— Use 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 forstart_monitoring_signup— Use this when the user asks for ongoing DMARC monitoring, RUA report monitoring, new-sender monitoring, email-authentication alerts, ongoingcount_spf_lookups— Use this when the user asks about SPF 'too many lookups', the 10-lookup limit, an SPF PermError, or whether an SPF record is valid. Validatevalidate_dmarc_record— Use this when the user pastes a DMARC record and asks whether it is valid, correct or safe. Validate a pasted DMARC record: parsed tags, levgenerate_dmarc_record— Use 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 acheck_dkim_selector— Use this when the user asks whether DKIM is set up for a sending platform, whether a specific selector exists, or why DKIM fails. Check ONEparse_dmarc_report— Use this when the user uploads or pastes a DMARC aggregate (RUA) XML report and asks what it says. Parse ONE DMARC aggregate (RUA) report incheck_record— Use 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 —check_reverse_dns— Use this when the user asks about reverse DNS, PTR records, or FCrDNS for a mail server IP. Check one sending IP's forward-confirmed reverseaudit_spf_includes— Use 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 audibuild_parked_domain_records— Use this when the user asks how to protect a domain that sends no email from being spoofed. Build the three-record hardening pack that makescheck_propagation— Use this when the user asks whether a DNS change has propagated globally, or why a record shows in one place and not another. Check whetherlookup_registration— Use this when the user asks who owns a domain, when it expires, which registrar or nameservers it has, whether it is registered, or whetherget_alerts— Use this when a signed-in operator asks what changed on a monitored domain, whether its website went down, or what the monitoring has flaggeget_readiness— Use this when a signed-in operator asks whether a monitored domain is ready for the next DMARC step. Read the DMARC enforcement-readiness velist_my_domains— Use 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 tcheck_lookalikes— Use this when the user asks about lookalike, look-alike, typosquat or impersonation domains of their domain, or whether someone has registerget_lookalikes— Use 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'sstart_email_test— Use this when the user wants to know how a real email from them actually authenticates — whether a message from Google Workspace, Microsoftget_email_test— Use this after start_email_test, once the user says they sent the email. Returns status pending | received | expired | error. pending meanslist_email_tests— Use 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 Doctorcheck_bimi— Use 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,add_monitored_domain— Add a domain to the signed-in user's DNS Doctor monitoring and return the ownership-check TXT record they must publish, plus where their DNScheck_domain_verification— Use this only for DNS Doctor's own ownership TXT challenge on a domain the user already added to their DNS Doctor account (add_monitored_domget_domain_records— Read the records a domain the user monitors still needs: the ownership check while it is unverified, and once verified the DMARC reporting rwatch_record_change— Use 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 oncheck_domain_names— Use 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
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:50:52 | ✓ | ✓ | 334 ms | 90 | active |
| 2026-11-17 21:35:40 | ✓ | ✓ | 587 ms | 90 | active |
| 2026-11-17 21:20:23 | ✓ | ✓ | 378 ms | 90 | active |
| 2026-11-17 21:05:14 | ✓ | ✓ | 1466 ms | 87 | active |
| 2026-11-17 20:49:51 | ✓ | ✓ | 646 ms | 90 | active |
| 2026-11-17 20:34:41 | ✓ | ✓ | 743 ms | 90 | active |
| 2026-11-17 20:19:35 | ✓ | ✓ | 391 ms | 90 | active |
| 2026-11-17 20:04:14 | ✓ | ✓ | 645 ms | 90 | active |
| 2026-11-17 19:49:04 | ✓ | ✓ | 481 ms | 90 | active |
| 2026-11-17 19:33:57 | ✓ | ✓ | 733 ms | 90 | active |
| 2026-11-17 19:18:42 | ✓ | ✓ | 557 ms | 90 | active |
| 2026-11-17 19:03:27 | ✓ | ✓ | 348 ms | 90 | active |
| 2026-11-17 18:48:14 | ✓ | ✓ | 433 ms | 90 | active |
| 2026-11-17 18:33:00 | ✓ | ✓ | 603 ms | 90 | active |
| 2026-11-17 18:17:48 | ✓ | ✓ | 543 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://dnsdoctor.dev/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/dnsdoctor-dev-mcp # JSON