DNS Doctor
Related Servers
Alternatives to DNS Doctor
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceProvides DNS lookup and email authentication diagnostic tools (SPF, DKIM, DMARC, MX, etc.) for use with MCP-compatible clients. Enables natural language queries to check DNS records and email health.7-
- AlicenseAqualityDmaintenanceMCP server for email deliverability: validate SPF/DKIM/DMARC/BIMI, check blacklists, test SMTP/IMAP, look up DNS, and generate ready-to-deploy records for any major email provider. Ships with two one-click prompts (audit-deliverability, setup-dns). Public, no auth.17MIT

DNS Doctorofficial
AlicenseAqualityBmaintenanceChecks and fixes a domain's email authentication (SPF, DKIM, DMARC), DNS health, propagation, blacklists and domain/SSL expiry, returning copy-paste fix records from a validating engine, never a model guess. Local stdio server (npx -y @dnsdoctor/mcp) with the same 27 tools as the hosted https://dnsdoctor.dev/mcp.29765 npmApache 2.0- AlicenseAqualityDmaintenanceAn MCP server for domain intelligence — WHOIS, DNS records, SSL certificate inspection, SPF/DMARC validation, security-header audits, and blacklist/reputation checks, callable by AI agents. Powered by domainintel.app; runs server-side, no local setup.749 npmMIT
- FlicenseNot gradedqualityBmaintenanceMCP server for inspecting email domains and addresses, providing objective domain-level email infrastructure answers such as MX, SPF, DMARC, MTA-STS, and disposable-domain evidence.-
- AlicenseNot gradedqualityDmaintenanceMCP server that lets agents check domain email authentication (SPF, DKIM, DMARC, MX) via a free API, returning grades and shareable report URLs. Also provides tools for listing paid services and partner program terms.MIT
TDQS
Scored across 27 tools
Most tools have clearly distinct purposes, and the descriptions actively cross-reference neighbors (get_report vs scan_domain, check_record vs check_domain_verification, count_spf_lookups vs audit_spf_includes, check_lookalikes vs get_lookalikes). The remaining friction is the cluster of DMARC record tools (generate_dmarc_record, build_dmarc_upgrade, validate_dmarc_record, get_readiness) plus the four record-reading tools, which are separable only by reading the long descriptions carefully.
Every name is snake_case with a predictable verb_noun shape: check_*, get_*, list_*, start_*, build_*, generate_*, validate_*, parse_*, add_*, audit_*, count_*, scan_domain, lookup_registration. No camelCase or stylistic mixing.
27 tools is at the heavy end of the rubric, and the surface spans several sub-products (one-off DNS checks, DMARC record builders, email testing, monitoring/account management, lookalike watch). Each tool appears to earn its place, but the breadth pushes it past a comfortably scannable set.
Coverage is strong: scan/get report, per-record lookup, propagation, registration, SPF deep audit, BIMI, reverse DNS, the full DMARC lifecycle (generate, validate, upgrade, readiness), email testing with history, and monitoring signup/verification/alerts. Minor gaps: no way to remove or stop monitoring a domain, and no alert acknowledgment/delete by explicit design.