mcp-server-whois
mcp-server-whois
Model Context Protocol (MCP) server for authoritative raw WHOIS lookups, domain age calculation, and registrar detection.
β‘ Features & Tools
raw_whois_lookup: Queries authoritative registries directly via socket port 43 to obtain live WHOIS records without API limits.analyze_registration_lifecycle: Parses domain creation date and expiry date to evaluate domain maturity and renewal status.
Related MCP server: mcp-server-domain-appraisal
π Quick Start (Running with AI Clients)
Claude Desktop Integration
Add this snippet to your claude_desktop_config.json:
{
"mcpServers": {
"whois": {
"command": "npx",
"args": ["-y", "mcp-server-whois"]
}
}
}Cursor IDE / Windsurf Integration
Under MCP Settings, add a new stdio transport:
Command:
npx -y mcp-server-whois
π¦ Local Installation & Development
npm install -g mcp-server-whoisOr run directly via stdio:
npx mcp-server-whoisπ License
MIT License. Developed for the global AI agent and domain ecosystem.
Available Tools
2 toolsanalyze_registration_lifecycleB
Parses domain creation date and expiry date to evaluate domain maturity and renewal status.
Inputs: expiry_year (required), creation_year (required).
raw_whois_lookupA
Queries authoritative registries directly via socket port 43 to obtain live WHOIS records without API limits.
Inputs: domain (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 2 tools
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.
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.
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.
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
Related MCP Connectors
Domain intel for AI agents: RDAP registration, DNS, email deliverability, tech stack.
Domain intel for AI agents: RDAP registration, DNS, email deliverability, tech stack.
Domain intel for agents: DNS, RDAP age/registrar, CT certs, security headers, tech stack, sitemaps.
71Domain age and RDAP lookup: registration date, age, expiry, registrar, status and nameservers.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to perform real-time WHOIS and RDAP lookups, domain availability checks, and TLD infrastructure exploration using native protocols without API keys.8MIT
- AlicenseAqualityCmaintenanceModel Context Protocol (MCP) server providing automated domain valuation, authoritative WHOIS lookup, and comparable sales analysis for AI agents3MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to look up domain registration data through RDAP, including registration date, age, expiry, registrar, status, and nameservers.MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to generate brandable business names and verify each candidate across TLDs with real registry lookups, ranking results by availability. Also checks individual or bulk domains for registration status, expiry, DNS, email and TLS details via RDAP, WHOIS and DNS probes.4MIT