Skip to main content
Glama
tudadada

mcp-server-whois

by tudadada
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to mcp-server-whois

No user-submitted related servers found.

    Related Servers

    • 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
      6
      3
      12 npm
      MIT

    • Whois MCP

      modelcontextprotocol-servers
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to perform WHOIS lookups to retrieve domain registration details, including ownership, registration dates, and availability status without requiring browser searches.
      4
      43 npm
      21
      MIT

    • Domain Checker MCP Server

      3viky
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to check domain availability, perform batch domain lookups, and generate intelligent domain name suggestions across multiple TLDs using WHOIS integration.
      3
      MIT

    • DomScan MCP Server

      estevecastells
      A
      license
      A
      quality
      C
      maintenance
      Domain intelligence for DNS, WHOIS/RDAP, SSL/TLS, subdomain discovery, availability, valuation, email security, and typosquatting and brand protection.
      1
      1
      MIT

    • Whois MCP

      bharathvaj-ganesan
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that allows AI agents to perform WHOIS lookups, enabling users to directly ask the AI about domain availability, ownership, registration details, and other domain information.
      4
      559 npm
      59
      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

    B3.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one fetches raw WHOIS data, the other analyzes registration lifecycle details from that data. There is no practical overlap or ambiguity in when to use each.

    Naming Consistency3/5

    Both names use snake_case, but the pattern is inconsistent: 'raw_whois_lookup' is a noun phrase while 'analyze_registration_lifecycle' follows a verb-noun structure. The names are still readable and descriptive, but they do not share a uniform convention.

    Tool Count3/5

    Two tools is on the thin end of the spectrum for a WHOIS-focused server. The pair covers raw lookup and one analysis function, which is borderline but arguably sufficient for a narrow use case.

    Completeness2/5

    The server provides raw WHOIS retrieval and expiry/creation analysis, but lacks common operations such as structured/parsed WHOIS output, registrar information, nameserver details, or domain availability checks. Agents needing standard WHOIS data beyond registration lifecycle would have to do their own parsing and may hit dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources