Skip to main content
Glama
ofershap

mcp-server-dns

by ofershap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-server-dns

No user-submitted related servers found.

    Related Servers

    • domain-mcp

      danielgtmn
      A
      license
      A
      quality
      A
      maintenance
      MCP server for checking domain name availability via RDAP and WHOIS fallback, supporting single and bulk domain lookups.
      5
      MIT

    • ip-doctor

      Baneado98
      A
      license
      A
      quality
      B
      maintenance
      MCP server for live IP and domain reputation checks via DNS lookups, providing abuse scores and network type without requiring an API key.
      2
      MIT

    • netdiag-mcp

      shigechika
      A
      license
      A
      quality
      A
      maintenance
      MCP server for on-demand network diagnostics, providing DNS lookups with DNSSEC checks, ping, traceroute, TCP port checks, HTTP checks, TLS certificate inspection, WHOIS, and ASN lookups.
      12
      235 PyPI
      MIT

    • intodns-mcp

      RoscoNL
      A
      license
      A
      quality
      A
      maintenance
      MCP server for IntoDNS.ai providing 36 free tools for DNS, DMARC, SPF, DKIM, BIMI, DNSSEC, MTA-STS, FCrDNS, blacklist and email security checks. Citation-grade report snapshots with content hashes. No API key required.
      45
      262 npm
      2
      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

    A3.5/5.0

    Scored across 5 tools

    Disambiguation4/5

    The tools are mostly distinct with clear purposes: dns_lookup for specific record types, resolve_all for common records in bulk, reverse_dns for PTR lookups, and whois for domain registration data. However, check_nameservers overlaps with dns_lookup (which can also return NS records) and resolve_all (which includes NS), potentially causing confusion in tool selection.

    Naming Consistency4/5

    The naming follows a consistent snake_case pattern with descriptive verb-noun combinations (e.g., dns_lookup, reverse_dns). Minor deviations exist: check_nameservers uses 'check' while others use more specific verbs like 'lookup' or 'resolve', but overall the convention is readable and predictable.

    Tool Count5/5

    With 5 tools, this server is well-scoped for DNS operations. Each tool serves a distinct function in the domain, and the count is neither too sparse nor bloated, making it manageable for agents to handle typical DNS-related tasks effectively.

    Completeness4/5

    The toolset covers essential DNS operations: lookup, bulk resolution, reverse lookups, and WHOIS queries. A minor gap exists in lacking explicit tools for DNS record management (e.g., create or update records), but this is reasonable if the server is focused on querying rather than administration, and agents can still perform core diagnostic tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources