Dns-doctor MCP Server

Scan, fix and verify a domain's DNS — email authentication (SPF, DMARC, DKIM) first, plus multi-region propagation, SPF include supply-chain audits, MX, DNS health, blacklists and domain/SSL expiry…

Local + remotestreamable-httpstdioApache-2.0

What is the Dns-doctor MCP Server?

claude-plugin is an MCP project maintained in the dnsdoctor/claude-plugin repository. The maintainer describes its purpose as “Scan, fix and verify a domain's DNS — email authentication (SPF, DMARC, DKIM) first, plus multi-region propagation, SPF include supply-chain audits, MX, DNS health, blacklists…”. Read the project documentation for the complete scope.

Hosted connection

The maintainer’s configuration uses https://dnsdoctor.dev/mcp. Check the project’s account and authentication instructions when adding the endpoint to your client.

Source

Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
scan_domainFresh scan of a domain; full report.
get_reportPersisted report (scans once if none exists).
build_dmarc_upgradeA validated DMARC enforcement record, capped at p=quarantine and returned only when the server-derived alignment gate passes; without that evidence the…
count_spf_lookupsThe SPF DNS-lookup count against the RFC limit of 10.
validate_dmarc_recordParse and validate a DMARC record, tag by tag.
generate_dmarc_recordBuild a DMARC record from a policy + reporting address.
check_dkim_selectorLook up one DKIM selector and check the key.
parse_dmarc_reportParse an aggregate (RUA) report file into rows.
check_recordRead any DNS record type for a name.
check_propagationWhether a DNS change has gone global: six vantage points (five owner-run probes plus the server's own resolver) read the same name, returning the grid plus a…
lookup_registrationRegistrar, dates, EPP status codes, nameservers, DNSSEC and abuse contact from one RDAP read. Observation only; a registry that did not answer is unknown…
check_lookalikesWhich close variants of a domain's name resolve and which accept mail: counts plus up to ten resolving names. DNS-only facts, never a verdict; a name that…
check_reverse_dnsPTR / forward-confirmed reverse DNS for an IP.
audit_spf_includesThe SPF include/redirect tree — who can transitively send as the domain, with typed findings (broken include, confirmed-unregistered include, expiring…
build_parked_domain_recordsThe Null MX + v=spf1 -all + p=reject; np=reject hardening pack for a domain that sends no mail. The server re-checks DNS itself and refuses when it finds…
start_monitoring_signupA sign-up link to hand to the human who owns the domain. Sends no email and creates nothing — they open it, sign in on our page themselves (a social provider…
get_alertsToken required. The account's monitoring alert log, newest first. Read-only — no acknowledge, no delete. Page down with before until next_before is null before
get_readinessToken required. Whether one monitored domain's aggregate-report evidence justifies a stronger DMARC policy yet: ready, the blockers, and next_record…
get_lookalikesToken required. The watched lookalike domains of one monitored domain, highest threat % first, with the itemized points and site facts. ai_assessment.summary…

How to install the Dns-doctor MCP Server

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

From the project documentation. Replace placeholders and example paths before connecting.