# Dnsdoctor MCP server

Source: https://glimind.com/server/mcp-registry%2Fdev.dnsdoctor%2Fmcp
Registry id: `mcp-registry/dev.dnsdoctor/mcp`
Status: live (checked 2026-10-27T02:43:57.040Z)

## Verdict

Dnsdoctor MCP server answered 99.95% of Glimind's liveness checks over 30 days, better than 36% of MCP servers, with 819 ms median handshake and 5 outages in 90 days. Its agent-readiness grade is A (99/100) across 27 tools, costing an agent about 8,727 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.95% | 36% of MCP servers |
| Median handshake latency | 819 ms | 28% of MCP servers |
| p95 handshake latency | 2912 ms | — |
| Checks in 30 days | 4,951 | — |
| Outages, 90 days | 5 | — |
| Median recovery | 7 min | — |
| Agent-readiness score | 99/100 (A) | 93% of MCP servers |
| Tools | 27 | — |
| Tool-list size for an agent | ~8,727 tokens | 32% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "dnsdoctor-mcp-server": {
      "type": "http",
      "url": "https://dnsdoctor.dev/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http dnsdoctor-mcp-server https://dnsdoctor.dev/mcp
```

## Tools (27)

- `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 provid
- `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 
- `build_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 ca
- `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 domai
- `check_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 d
- `check_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 select
- `check_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 reco
- `check_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 t
- `check_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 pro
- `check_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 answeri
- `check_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
- `count_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 c
- `generate_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
- `get_alerts`: 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 th
- `get_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 w
- `get_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 
- `get_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. R
- `get_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
- `get_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
- `list_email_tests`: Use this when a signed-in user asks about email tests they ran before, or how a sender's earlier tests scored. Requires an API token with monitoring:read. Retur
- `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 
- `lookup_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
- `parse_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-sour
- `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 
- `start_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 to
- `start_monitoring_signup`: Use this when the user asks for ongoing DMARC monitoring, RUA report monitoring, new-sender monitoring, email-authentication alerts or ongoing DNS monitoring of
- `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 w

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.