The Dns Doctor MCP server,
connected in one click.

“Use “scan_domain”: Force a fresh scan of a domain and return its full report: seven deterministic checks — SPF, DKIM, DMARC, MX, DNS hardening, domain/TLS expi.”

“Use “get_report”: Return the stored report for a domain, scanning once only if none exists yet — the cheap read, and the right default for a first look. Retur.”

“Use “build_dmarc_upgrade”: Return a validated DMARC enforcement-upgrade record for a domain. The alignment gate (whether p=reject is safe) is derived server-side from.”

“Use “start_monitoring_signup”: Return a sign-up link to give to the HUMAN who owns a domain, so they can start monitoring it themselves. Nothing is created and no email is.”

scan_domain — Force a fresh scan of a domain and return its full report: seven deterministic checks — SPF, DKIM, DMARC, MX, DNS hardening, domain/TLS expi

get_report — Return the stored report for a domain, scanning once only if none exists yet — the cheap read, and the right default for a first look. Retur

build_dmarc_upgrade — Return a validated DMARC enforcement-upgrade record for a domain. The alignment gate (whether p=reject is safe) is derived server-side from

start_monitoring_signup — Return a sign-up link to give to the HUMAN who owns a domain, so they can start monitoring it themselves. Nothing is created and no email is

count_spf_lookups — Validate an SPF record and count what it costs. Returns `record_valid` (the record parses as RFC 7208 SPF), `findings` (per-term diagnostics

validate_dmarc_record — Validate a pasted DMARC record: parsed tags, level'd findings, and whether it is valid. No DNS lookup — pass the record string itself. `upgr

generate_dmarc_record — Build a DMARC record from scratch for a domain that has none, using a validating engine — never compose one yourself. `policy` is none|quara

check_dkim_selector — Check ONE specific DKIM selector on a domain — the exact selector the sending platform uses (e.g. `google`, `s1`), which a full scan's commo