Skip to main content
Glama
danielgtmn

domain-mcp

by danielgtmn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to domain-mcp

No user-submitted related servers found.

    Related Servers

    • domain-check-mcp

      stucchi
      A
      license
      A
      quality
      D
      maintenance
      MCP server for checking domain name availability across 500+ TLDs using RDAP with WHOIS fallback for specific TLDs.
      2
      MIT

    • domain-mcp

      itsalfredakku
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server for domain availability checks, WHOIS lookups, and domain suggestions using RDAP and TCP port 43. It allows users to perform bulk checks and retrieve registration details across multiple TLDs without requiring an API key.
      41 npm
      -

    • 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
      32 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
    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: check_domain and check_domains are clearly single vs bulk variants, while domain_info is differentiated by its stated purpose (metadata for known-registered domains). However, check_domain and domain_info perform essentially the same underlying check, which could cause mild misselection; the description mitigates this but the overlap is real.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern (check_domain, check_domains, domain_info, list_supported_tlds, clear_domain_cache). Minor deviation: domain_info uses 'info' rather than a clearer verb like 'get_domain_info', breaking the otherwise clean pattern, and clear_domain_cache uses an adjective+noun rather than object-first.

    Tool Count4/5

    Five tools is within the ideal 3-15 range and appropriate for a domain-checking server. The count feels slightly trimmed—check_domain and domain_info are near-duplicates, suggesting one could be folded into the other—but the overall scope is reasonably well served.

    Completeness4/5

    The server covers checking, bulk checking, metadata lookup, TLD discovery, and cache management, covering the core domain-lookup workflows well. Minor gaps exist: there is no tool for WHOIS-style detailed records beyond raw payloads, and no capability to register or manage domains (if that were in scope). For pure lookups, the surface is complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources