# dns-doctor (slim) > dns-doctor, an MCP server by dnsdoctor.dev, listed from the official MCP registry. Indexed, not reviewed: facts and our own checks, no score or ranking. Scan, fix, verify and monitor DNS: SPF, DMARC, DKIM, propagation, health, expiry. Validated fixes. - Full: https://www.anchorterminal.com/tools/dnsdoctor-dns-doctor.md (~1,700 tokens) · this version ~1,630 tokens · JSON https://www.anchorterminal.com/tools/dnsdoctor-dns-doctor.json · canonical https://www.anchorterminal.com/tools/dnsdoctor-dns-doctor - Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-04 # dns-doctor > Indexed, not reviewed: facts from the official MCP registry and our own checks. No score, grade or rank, and not in the rankings until the panel reviews it. How the index works: https://www.anchorterminal.com/indexed/ - Kind: MCP server, by dnsdoctor.dev (https://dnsdoctor.dev/methodology) - Category: Observability & incidents (https://www.anchorterminal.com/categories/observability.md) - Listed because: It's published in the registry under dnsdoctor.dev, a namespace the registry only gives to whoever proves they control that domain. - What the official MCP registry says: Scan, fix, verify and monitor DNS: SPF, DMARC, DKIM, propagation, health, expiry. Validated fixes. ## Facts - MCP registry: `dev.dnsdoctor/dns-doctor` 1.10.0 - Endpoint: https://dnsdoctor.dev/mcp (streamable HTTP) - Package: npm `@dnsdoctor/mcp` (stdio) - Source: https://github.com/dnsdoctor/claude-plugin - Website: https://dnsdoctor.dev/methodology - npm downloads a week: 88 - GitHub stars: 2 - Registry entry updated: 2026-10-01 ## Tools - Tools it lists (22, about 10,348 tokens of context, `tools/list` without credentials over MCP 2026-07-28, checked 2026-10-04 22:24 UTC): - `scan_domain` (writes): 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` (writes): 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.… - `build_dmarc_upgrade` (writes): 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… - `start_monitoring_signup` (read-only): Use this when the user wants DMARC monitoring, RUA report monitoring, new-sender monitoring, email-authentication alerts, ongoing DNS monitoring, or to start a… - `count_spf_lookups` (read-only): 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… - `validate_dmarc_record` (read-only): 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… - `generate_dmarc_record` (read-only): 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… - `check_dkim_selector` (read-only): 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… - `parse_dmarc_report` (read-only): 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… - `check_record` (read-only): 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… - `check_reverse_dns` (read-only): 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):… - `audit_spf_includes` (read-only): 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` (read-only): 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… - `check_propagation` (read-only): 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… - `lookup_registration` (read-only): 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… - `get_alerts` (read-only): Use this when a signed-in operator asks what changed on a monitored domain, or what the monitoring has flagged. Read the monitoring alert log for the domains… - `get_readiness` (read-only): 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… - `check_lookalikes` (read-only): 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… - `get_lookalikes` (read-only): 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.… - `add_monitored_domain` (writes): 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… - `check_domain_verification` (writes): Check whether the ownership TXT record for a domain the user has added is visible yet, and mark it verified when it is. The result says WHICH outcome occurred… - `get_domain_records` (read-only): 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… - How its tools read to an agent (0 errors, 1 warning, 1 note, about 10,348 tokens; rules at https://www.anchorterminal.com/check.md; not part of the score): - warn TC18 start_monitoring_signup: readOnlyHint is true but the name says "start" - note TC29 server: about 632 tokens (6% of the definitions) are titles that repeat property or function names - JSON: https://www.anchorterminal.com/api/v1/tools/dnsdoctor-dns-doctor.json - Being indexed says nothing about quality, and nobody can pay for it. Ask for a review: https://www.anchorterminal.com/builders/#claiming