whois

This MCP server provides WHOIS lookup capabilities for domains, IPs, and ASN data via four tools: whois_domain, whois_tld, whois_ip, and whois_as. whois_domain returns registration details for a given domain, including registrar, registrant, registration and expiry dates, nameservers, and status. whois_tld fetches WHOIS information about a top-level domain, which can be useful to understand ownership patterns and regulatory details of a TLD. whois_ip looks up WHOIS information for an IP address, revealing its block allocation, organization, and related metadata. whois_as provides WHOIS data for an Autonomous System Number (ASN), useful for identifying the organization and network details behind an IP range. To use these tools, enable the Whois MCP server in your Cursor or MCC environment; the tools will appear under Available Tools and can be invoked by the agent when domain-related questions arise.

Prerequisites:

• Node.js (recommended latest LTS) and npm installed on your system.
• Internet connection to fetch the MCP package via npx.

Installation steps:

1. Ensure Node.js and npm are installed.
2. Run the MCP server using npx:

npx -y @bharathvaj/whois-mcp@latest

3. (Optional) Add the server to Cursor project configuration:

{
  "mcpServers": {
    "whois": {
      "command": "npx",
      "args": [
        "-y",
        "@bharathvaj/whois-mcp@latest"
      ]
    }
  }
}

4. (Optional) In Roo Code or MCC, reference the same configuration to expose the tools to agents.
5. If you prefer building locally, install dependencies and build (where applicable):

pnpm install
pnpm build

6. Debug or verify using the MCP Inspector as needed:

pnpm build
npx @modelcontextprotocol/inspector node dist/index.js

Notes:

• The server uses the @bharathvaj/whois-mcp package; ensure you pull the latest version with the same command you place in your environment (npx ...@latest).
• Some WHOIS data may be restricted or vary by registrar, privacy protections, and regional policies; results may differ across sources.
• If you deploy in environments with restricted network egress, ensure DNS resolution and port 43 (WHOIS) access are allowed.
• When wiring into Cursor or Roo Code, you may expose these tools as part of the Available Tools list and rely on the agent to invoke them as domain-related questions arise.
• For rate limiting or abuse concerns, consider adding usage controls or caching at the client level where feasible.