Skip to main content
Glama
ip2whois

mcp-ip2whois

Official
by ip2whois
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-ip2whois

No user-submitted related servers found.

    Related Servers

    • Whois MCP

      bharathvaj-ganesan
      A
      license
      A
      quality
      F
      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
      302 npm
      60
      MIT

    • domainintel-mcp

      Bishop81
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for domain intelligence — WHOIS, DNS records, SSL certificate inspection, SPF/DMARC validation, security-header audits, and blacklist/reputation checks, callable by AI agents. Powered by domainintel.app; runs server-side, no local setup.
      7
      36 npm
      MIT

    • Whodis MCP Server

      vinsidious
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to check domain name availability using WHOIS lookups.
      7 npm
      4
      ISC

    • whois-mcp

      xiaobenyang-com
      A
      license
      A
      quality
      D
      maintenance
      A WHOIS domain name query server based on Model Context Protocol (MCP), supporting the resolution of over 877 top-level domains and 169 country code top-level domains, and providing comprehensive domain name registration information query functions.
      3
      2
      Apache 2.0

    • Whoisfreaks

      WhoisFreaks
      F
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server that exposes the full WhoisFreaks API suite as AI-callable tools. Works with Claude Desktop, Cursor, Windsurf, VS Code, Continue, Zed, and any other MCP-compatible AI client.
      -
    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 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one resolves IP addresses to hosted domains, the other retrieves WHOIS data for domain names. There is no functional overlap.

    Naming Consistency5/5

    Both tools follow the consistent verb_noun pattern (get_hosted_domains, get_whois), making the naming predictable and easy to understand.

    Tool Count3/5

    With only two tools, the server feels minimal for the domain of IP and domain information. While the tools cover core functionalities, the count is at the lower boundary of what's reasonable.

    Completeness3/5

    The tools cover hosted domains and WHOIS lookups, but common related operations like IP geolocation, domain availability checks, or reverse IP lookups are missing. The surface is functional but not comprehensive.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources