dev.dnsdoctor/dns-doctor

up checked 2026-11-11T07:39:02.359Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided description

Scan, fix, verify and monitor DNS: SPF, DMARC, DKIM, propagation, health, expiry. Validated fixes.

Summary by lookupd

Scans, validates and monitors DNS and email authentication records like SPF, DKIM and DMARC, with fix guidance and alerts.

Install

Claude Code, remote (streamable-http)

claude mcp add --transport http dns-doctor https://dnsdoctor.dev/mcp

Claude Code, npm package (stdio)

claude mcp add dns-doctor -- npx -y @dnsdoctor/mcp

Codex, remote (streamable-http)

codex mcp add dns-doctor --url https://dnsdoctor.dev/mcp

Codex, npm package (stdio)

codex mcp add dns-doctor -- npx -y @dnsdoctor/mcp

Cursor, remote (streamable-http) → .cursor/mcp.json

{
  "mcpServers": {
    "dns-doctor": {
      "url": "https://dnsdoctor.dev/mcp"
    }
  }
}

Cursor, npm package (stdio) → .cursor/mcp.json

{
  "mcpServers": {
    "dns-doctor": {
      "command": "npx",
      "args": [
        "-y",
        "@dnsdoctor/mcp"
      ]
    }
  }
}

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (29 tools)

Publisher-provided text

• scan_domain Use this when the user asks to check, audit, diagnose or troubleshoot SPF, DKIM, DMARC, email authentication, email deliverability DNS, why their mail lands in
• get_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 be re-read now. Return
• build_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 for a domain (a scan ca
• start_monitoring_signup Use this when the user asks for ongoing DMARC monitoring, RUA report monitoring, new-sender monitoring, email-authentication alerts, ongoing DNS monitoring, or
• count_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. Validate an SPF record and c
• validate_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, level'd findings, and w
• generate_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 a domain that has none
• check_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 ONE specific DKIM select
• parse_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 into readable per-sour
• check_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 — or whenever answeri
• 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 reverse DNS (FCrDNS): reads
• audit_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 audit. Audit a domain's
• build_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 makes a NON-SENDING domai
• check_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 whether a DNS change has pro
• lookup_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 whether a transfer or delete
• get_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 flagged. Read the monitori
• get_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 verdict for ONE domain
• list_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 the caller's account
• check_lookalikes Use 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 t
• get_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's takedown evidence. R
• start_email_test Use 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 to
• get_email_test Use 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
• list_email_tests Use this when a signed-in user asks about email tests they ran before, or how a sender's earlier tests scored. Requires an API token with monitoring:read. Retur
• check_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, or why their logo d
• 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 DNS is hosted, a provid
• check_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_domain). For a TXT reco
• get_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 record plus whether w
• watch_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 on ONE record for the
• check_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 ONE call (never one

Details

• Version: 1.21.0
• Transports: streamable-http, stdio
• Uptime (7 days): 100%
• Median latency: 1019 ms
• First indexed: 2026-11-01T09:00:53.385Z
• Last seen in registry: 2026-11-09T13:17:23.021Z
• Repository: https://github.com/dnsdoctor/mcp
• Website: https://dnsdoctor.dev/methodology

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/dev.dnsdoctor/dns-doctor.svg)](https://lookupd.com/servers/dev.dnsdoctor/dns-doctor)

• 62141 servers
• Last crawl: 2026-11-11T18:39:04.612Z
• API base: https://api.lookupd.com
• MCP URL: https://api.lookupd.com/mcp