Skip to main content
Glama
tudadada

mcp-server-domain-checker

by tudadada
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to mcp-server-domain-checker

No user-submitted related servers found.

    Related Servers

    • Domain Checker

      ahramadan44
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables checking domain name availability using WHOIS lookups and DNS resolution. Supports both single and batch domain checking with detailed availability analysis.
      -

    • Domain Checker MCP Server

      ajot
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables domain availability checking through dual verification using WHOIS lookups and DNS resolution. Supports both single and batch processing to provide detailed analysis on whether domains are likely available or already registered.
      4
      -

    • FastDomainCheck MCP Server

      bingal
      A
      license
      A
      quality
      D
      maintenance
      Enables checking domain name availability for single or multiple domains using WHOIS and DNS verification.
      1
      80 PyPI
      21
      MIT

    • mcp-dns

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables DNS record lookups for types like A, MX, TXT, and CNAME, bulk queries of all major record types, and reverse DNS resolution from IP addresses to hostnames.
      4 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools target entirely different concerns: registration availability via registry socket query versus live DNS record resolution. There is no plausible scenario where an agent would confuse the two.

    Naming Consistency5/5

    Both tools follow a clean verb_noun snake_case pattern (check_domain_availability, resolve_dns_records). Consistent and predictable.

    Tool Count3/5

    Two tools is on the thin side for a domain-checker server; a single focused capability pair is defensible but leaves little room for adjacent operations. Not a mismatch, but borderline sparse.

    Completeness3/5

    Availability and DNS cover the core lookup needs, but there is no WHOIS/registrar data, expiry, or bulk/batch checking. Agents needing registration metadata would hit a dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources