Skip to main content
Glama
tudadada

mcp-dns

by tudadada
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mcp-dns

No user-submitted related servers found.

    Related Servers

    • mcp-server-dns

      ofershap
      A
      license
      A
      quality
      D
      maintenance
      MCP server for DNS lookups, reverse DNS, WHOIS, and domain checks. Zero auth, zero config.
      5
      55 npm
      3
      MIT

    • Lookup-Domain

      xiaobenyang-com
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides comprehensive domain name research tools, including RDAP, WHOIS, and DNS query functionality.
      1
      2
      Apache 2.0

    • mcp-dnstwist

      w0h1v
      A
      license
      Not graded
      quality
      F
      maintenance
      A Model Context Protocol (MCP) server for dnstwist, a powerful DNS fuzzing tool that helps detect typosquatting, phishing, and corporate espionage.
      21 npm
      51
      MIT

    • Domain Tools MCP Server

      deshabhishek007
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides comprehensive domain analysis capabilities including WHOIS lookups, DNS record queries, and DNS health checking.
      14
      MIT

    • mcp-server-domain-appraisal

      tudadada
      A
      license
      A
      quality
      C
      maintenance
      Model Context Protocol (MCP) server providing automated domain valuation, authoritative WHOIS lookup, and comparable sales analysis for AI agents
      3
      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.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of overlapping purposes. The tool's purpose is singular and unambiguous.

    Naming Consistency5/5

    The single tool follows the verb_noun pattern (resolve_dns), which is clear and consistent. With only one tool, there are no conflicting conventions.

    Tool Count3/5

    A single tool for DNS resolution is minimal but functional. It feels slightly thin for a server, but the one tool does cover the primary domain adequately.

    Completeness4/5

    The tool covers common record types (A, AAAA, MX, TXT, NS, CNAME) but omits less common types like PTR, SRV, or SOA. This is a minor gap for most DNS use cases.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources