Skip to main content
Glama
dnsdoctor

DNS Doctor

by dnsdoctor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to DNS Doctor

No user-submitted related servers found.

    Related Servers

    • mailX tools

      Mailwarm
      A
      license
      A
      quality
      D
      maintenance
      MCP 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.
      17
      MIT

    • domainintel-mcp

      Bishop81
      A
      license
      A
      quality
      D
      maintenance
      An 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.
      7
      28 npm
      MIT

    • mailtype-api

      GSterlingPress
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP 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.
      -

    • agpc-domain-check

      markolati85
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP 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

    • dnsdoctor

      Baneado98
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that checks SPF, DKIM, DMARC, and MX records for a domain, returning a health verdict and specific DNS fixes to improve email deliverability.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 25 tools

    Disambiguation5/5

    Each tool has a clearly distinct, well-scoped purpose. Even the closest pairs are explicitly differentiated in their descriptions: get_report vs scan_domain (cached read vs fresh scan), check_record vs check_propagation (single record vs global agreement grid), and count_spf_lookups vs audit_spf_includes (lookup counting vs supply-chain walk). Names and descriptions unambiguously signal when to use which.

    Naming Consistency4/5

    The overwhelming majority follow a consistent verb_noun pattern: check_propagation, add_monitored_domain, build_dmarc_upgrade, get_alerts, scan_domain, parse_dmarc_report. A few read as noun-phrases or drop the verb (get_lookalikes is fine, but check_domain_verification and count_spf_lookups are consistent; the minor wrinkle is that 'start_email_test' vs 'get_email_test' vs 'list_email_tests' form a micro-family that is still predictable). Overall highly readable and consistent.

    Tool Count4/5

    25 tools is at the upper end of comfortable for a DNS/email-authentication server that legitimately spans propagation, SPF/DKIM/DMARC, monitoring, lookalikes, reverse DNS, registration and email testing. Every tool maps to a real sub-domain, but the count is heavy enough that a slimmer surface (e.g. merging report-read/scan or signup helpers) would reduce load. Still justified by scope.

    Completeness5/5

    The surface covers the full domain lifecycle: observation (check_record, check_propagation, lookup_registration, check_reverse_dns), record generation (generate_dmarc_record, build_dmarc_upgrade, build_parked_domain_records), validation (count_spf_lookups, validate_dmarc_record), monitoring (add_monitored_domain, start_monitoring_signup, check_domain_verification, get_readiness, get_alerts), and reporting (scan_domain, get_report, parse_dmarc_report). No obvious dead ends for the stated DNS-doctor purpose.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources