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
      C
      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
      38 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 20 tools

    Disambiguation5/5

    Each tool targets a distinct DNS/email-authentication operation: propagation check vs local record check, SPF lookup counting vs include auditing, DMARC validation vs upgrade vs generation vs report parsing. Descriptions clearly specify when to choose one over the other, and overlapping tools (scan_domain vs get_report) are explicitly differentiated by freshness.

    Naming Consistency5/5

    All 20 tools follow a consistent verb_noun pattern (check_*, get_*, build_*, parse_*, validate_*, etc.). There are no mixed naming conventions or vague verbs like 'process' or 'run'. The naming clearly indicates both the action and the subject.

    Tool Count4/5

    At 20 tools, the server has a comprehensive surface for DNS and email authentication diagnostics, monitoring, and record generation. It exceeds the ideal 3-15 range but remains justified by the domain's breadth; each tool represents a distinct valuable operation without redundancy.

    Completeness4/5

    The tool set covers the full lifecycle of DNS security: checking propagation, verifying records, scanning full domains, validating/upgrading/generating DMARC, auditing SPF, checking DKIM, reverse DNS, domain registration info, monitoring setup, alerts, and report parsing. Minor gaps exist, such as no generic record listing beyond specific types and no DNSSEC validation beyond registration lookup, but the core workflows are well-covered.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources