DNS Doctor - Email & DMARC
Fix email that lands in spam: SPF, DKIM, DMARC checks, exact DNS fix records, propagation, alerts
Reviews
No review yet. Used DNS Doctor - Email & DMARC? Be the first to help others choose.What it does
DNS Doctor - Email & DMARC is an MCP server, a connector that lets an AI assistant use it as a tool. It can be used hosted (nothing to install) or installed locally.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)Hosted endpoint
https://dnsdoctor.dev/mcpstreamable-http
In Claude Code: claude mcp add --transport http dns-doctor https://dnsdoctor.dev/mcp
Install package
- NPM
@dnsdoctor/mcpv1.21.3 · runs locally (stdio)
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"dns-doctor": {
"url": "https://dnsdoctor.dev/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 1d agoONLINE DNS Doctor - Email & DMARC answered an MCP connection on 16 Nov 2026 and introduced itself as dns-doctor 1.21.1 (MCP protocol 2025-06-18).
29 tools offered to AI assistants
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 spam, MX, DNS health, blacklist status, or domain/SSL expiry for a domain, or waget_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 the stored report for a domain, scanning once only if none exists yet — the chebuild_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 can justify quarantine at most; reject needs monitoring evidence) — and after anystart_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 website uptime monitoring and down alerts for a domain they own (a verified domacount_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 count what it costs. Returns `record_valid` (the record parses as RFC 7208 SPF),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 whether it is valid. No DNS lookup — pass the record string itself. `upgrade_recogenerate_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, using a validating engine — never compose one yourself. `policy` is none|quaracheck_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 selector on a domain — the exact selector the sending platform uses (e.g. `google`, `sparse_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-source aggregates: who sent mail as the domain, how much, and what share was SPF/DKIcheck_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 answering needs the live value of a record. Reads the record from the domain's OWN namecheck_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 the IP's PTR record, then resolves that hostname back and reports whether it reaudit_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
Show 17 more
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 domain unusable for spoofing: a Null MX, a hard-fail SPF record, and a p=reject; np=rcheck_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 propagated GLOBALLY: six vantage points (five owner-run probes across four continenlookup_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 lock is set — the WHOIS question. Read a domain's registration from the registrget_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 monitoring alert log for the domains the caller's account monitors, newest first, includget_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 the caller's account monitors, computed from its aggregate (RUA) report window.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 with its state — verified, pending (added, ownership not proven yet) or verificacheck_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 theirs. DNS-only: checks the closest variants of the name and returns facts — howget_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. Needs a connected DNS Doctor account or an API token with monitoring:read. Returnstart_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 tool or an app is SPF/DKIM/DMARC aligned, why it lands in spam, or to prove DKIM sget_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 arrived (or is still being checked): ask the user to send it if they have not, tlist_email_tests· Use this when a signed-in user asks about email tests they ran before, or how a sender's earlier tests scored. Needs a connected DNS Doctor account or an API token with monitoring:read. Returns the account's own tests, newest first (optionacheck_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 does not show. A live read of one host's BIMI setup: the DMARC gate (BIMI needs padd_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 Ucheck_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 record another service asked for (Google Workspace, Microsoft 365, Shopify or any siget_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 we have OBSERVED that record published. Read-only: it issues nothing — if a verifwatch_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 signed-in user: DNS Doctor rechecks it every 10 minutes for up to 48 hours withcheck_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 call per name). Each name is read live from its registry over RDAP: status is r
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Install package | @dnsdoctor/mcp | DECLARED | SRC-001 Official MCP Registry | 3h ago |
| Version | 1.21.3 | DECLARED | SRC-001 Official MCP Registry | 3h ago |
| Repository | https://github.com/dnsdoctor/mcp | DECLARED | SRC-001 Official MCP Registry | 3h ago |
| Hosted endpoint | https://dnsdoctor.dev/mcp | DECLARED | SRC-001 Official MCP Registry | 3h ago |
| Package registries | npm | DECLARED | SRC-001 Official MCP Registry | 3h ago |
| Local install (package) | yes | DECLARED | SRC-001 Official MCP Registry | 3h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 3h ago |
| Website | https://dnsdoctor.dev/methodology | DECLARED | SRC-001 Official MCP Registry | 3h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 3h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 3h ago |
Change history
- VERSION17 Nov 20261.21.1 → 1.21.3
- VERSION14 Nov 20261.21.0 → 1.21.1
- VERSION09 Nov 20261.20.0 → 1.21.0
- VERSION05 Nov 20261.18.0 → 1.20.0
- VERSION03 Nov 20261.16.2 → 1.18.0
- VERSION30 Oct 20261.16.1 → 1.16.2
- VERSION29 Oct 20261.16.0 → 1.16.1
- VERSION27 Oct 20261.14.0 → 1.16.0
- VERSION20 Oct 20261.12.0 → 1.14.0
- VERSION16 Oct 20261.10.3 → 1.12.0
- VERSION14 Oct 20261.10.2 → 1.10.3
- VERSION13 Oct 20261.10.1 → 1.10.2
- VERSION06 Oct 20261.10.0 → 1.10.1
- VERSION01 Oct 20261.9.0 → 1.10.0
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is DNS Doctor - Email & DMARC still online?
Free alerts · no account▲ 0Do you run DNS Doctor - Email & DMARC? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about DNS Doctor - Email & DMARC
How do I connect DNS Doctor - Email & DMARC?
Use the hosted endpoint https://dnsdoctor.dev/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does DNS Doctor - Email & DMARC offer?
When Electra Index connected on 16 Nov 2026, it listed 29 tools: scan_domain, get_report, build_dmarc_upgrade, start_monitoring_signup, count_spf_lookups, validate_dmarc_record, generate_dmarc_record, check_dkim_selector and more. The full list is in "Live check" above.
Is DNS Doctor - Email & DMARC online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.