DNS Doctor - Email & DMARC
v1.22.0Fix email that lands in spam: SPF, DKIM, DMARC checks, exact DNS fix records, propagation, alerts.
Endpoint health
online- Last checked
- 11/20/2026, 8:18:59 AM
- Latency
- 482 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:dev.dnsdoctor%2Fdns-doctor
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"dev.dnsdoctor/dns-doctor": {
"url": "https://dnsdoctor.dev/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
25 shown · authentication unknown
Add Monitored Domain
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 provider-specific guide link and, when their provider supports it, a one-click apply URL. Re-adding a domain they already monitor returns that domain rather than an error. Needs a linked DNS Doctor account: until the human has one, or if the host's connect prompt fails, use start_monitoring_signup and print its link instead. Print every record host and value EXACTLY as returned — never rewrite, reformat or improve a record string. Nothing here is applied to anyone's DNS: a human publishes every record, and you must show them what you are about to add and get their approval before using any DNS tool of your own. When guidance.note is present, relay it as given: it covers edge cases such as a domain on Automatic DMARC.
Schema valid · SHA-256 0f946d7ddb6f…
View input schema
{ "type": "object", "properties": { "domain": { "description": "The domain, e.g. example.com. For add_monitored_domain: any registrable domain the linked account owns (re-adding one it already monitors returns that row). For check_domain_verification and get_domain_records: a domain this account already monitors, verified or still pending. Any other name — another account's, or one nobody monitors — is refused as not found; ownership is never disclosed.", "title": "Domain", "type": "string" } }, "required": [ "domain" ], "title": "add_monitored_domainArguments" }Audit SPF Includes
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 SPF supply chain: walks every include and redirect it delegates to, and reports who can transitively send as it. Returns the resolved tree, per-node lookup attribution, the total authorized IPv4 address count, and typed findings — include_broken (a target that no longer publishes SPF, a PermError today), include_registrable (a delegated-to domain that does not exist, so a stranger who registers it becomes an authorized sender), include_expiring (registration lapsing within 30 days), pass_all_nested (a +all deep in the chain) and spf_record_unusable (the audited domain's OWN record is missing or does not parse, so there is no chain to walk). A domain we could not verify is reported as unverified and NEVER as available — never tell anyone a name is free on this tool's say-so unless the finding is include_registrable AND carries registry_confirmed: true. A registry_confirmed: false finding rests on DNS alone, which cannot tell an unsold name from one in redemption or on clientHold: report the mechanism as broken and the takeover risk as possible, but never as an available domain. Findings are risk analysis, not instructions: no SPF fix record exists here or anywhere else in DNS Doctor, because dropping a mechanism can silently de-authorize a real sender — relay the findings and let the domain's owner decide. Use count_spf_lookups instead when the question is only the 10-lookup limit.
Connections
streamable-http
https://dnsdoctor.dev/mcp