Skip to main content
Glama
Whoisjson

@whoisjson/mcp-server

Official
by Whoisjson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @whoisjson/mcp-server

No user-submitted related servers found.

    Related Servers

    • 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
      15 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

    • mcp-ip2location

      eweley95
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to perform IP geolocation, proxy detection, and domain WHOIS lookups using IP2Location.io and IP2WHOIS data.
      5
      MIT

    • MCP Domain Availability Server

      yenyifu
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to check domain name availability for single or multiple domains using DNS, RDAP, and WHOIS lookups. It provides detailed registration status including registrar information and expiration dates while supporting bulk checks of up to 50 domains.
      2
      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 4 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of domain investigation: WHOIS registration data, DNS records, SSL certificate validity, and availability check. There is no overlap or ambiguity in their purposes.

    Naming Consistency4/5

    All names use snake_case and follow a clear pattern, but the verb usage is slightly inconsistent: whois_lookup and dns_lookup share the 'lookup' suffix, ssl_check uses 'check', and domain_availability is a noun phrase. Still readable and predictable.

    Tool Count5/5

    Four tools form a focused, well-scoped set for domain diagnostics. Each tool addresses a core need (WHOIS, DNS, SSL, availability) without redundancy or excess.

    Completeness4/5

    Covers the primary domain lookup operations thoroughly. Minor gaps like reverse DNS or certificate transparency logs are not present, but the included tools handle typical domain investigation workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources