Skip to main content
Glama
Sign In
mambalabsdev

WHOIS Domain Lookup MCP Server

by mambalabsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to WHOIS Domain Lookup MCP Server

No user-submitted related servers found.

    Related Servers

    • WebDataTools Domain & website

      paulet4a-commits
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to run domain and website intelligence checks, including WHOIS/RDAP, DNS and email security, TLS headers, subdomains, tech stack, contacts, SEO, Core Web Vitals, sitemaps, and Wayback page diffs, using the caller's own Apify token.
      11
      MIT

    • domain-rdap-mcp

      Lulu-The-Narwhal
      A
      license
      A
      quality
      D
      maintenance
      Enables real-time domain registration lookups via RDAP, including availability, expiration, and registrar details, with no API key required. Supports natural language queries like 'is example.com available?' or 'when does example.com expire?'.
      1
      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
      30 npm
      21
      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.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is nothing to confuse it with. Its name and description make the single capability (registrant/expiry lookup for domains) unmistakable.

    Naming Consistency5/5

    The lone tool follows a clear verb_noun snake_case convention (lookup_domain_whois). There is no mixed convention to evaluate against, and the name is self-describing.

    Tool Count3/5

    The server's scope is narrow (read-only WHOIS/RDAP lookup), so a single tool is defensible, but it is thin: batch submission and result retrieval are fused into one call, and there is no companion tool for polling or re-fetching a run.

    Completeness4/5

    The lookup itself is thorough, returning registrar, dates, status, nameservers, DNSSEC, and partial registrant data with per-row status for failures. The gap is lifecycle: a failed run returns a run ID but there is no tool to check that run's status or retrieve its output.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources