mcp-server-whois
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| raw_whois_lookupA | Queries authoritative registries directly via socket port 43 to obtain live WHOIS records without API limits. |
| analyze_registration_lifecycleB | Parses domain creation date and expiry date to evaluate domain maturity and renewal status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.