mcp-server-whois
# mcp-server-whois
[](https://www.npmjs.com/package/mcp-server-whois)
[](https://opensource.org/licenses/MIT)
[](https://modelcontextprotocol.io)
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.
---
## 🚀 Quick Start (Running with AI Clients)
### Claude Desktop Integration
Add this snippet to your `claude_desktop_config.json`:
```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
```bash
npm install -g mcp-server-whois
```
Or run directly via stdio:
```bash
npx mcp-server-whois
```
---
## 📄 License
MIT License. Developed for the global AI agent and domain ecosystem.
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.