whoismd-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WHOISMD_API_KEY | Yes | Your `pg_live_...` API key. Never hard-code. | |
| WHOISMD_API_BASE | No | Overrides the API base URL (for testing). | https://whoismd.com/api |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoismd_lookupA | Perform a full domain intelligence lookup against the public WhoisMD API: WHOIS/RDAP registration data, DNS records (A, AAAA, MX, NS, TXT), SSRF-safe IP resolution, and a deterministic 0-100 threat risk score. Returns a comprehensive JSON report. |
| whoismd_bulkA | Run batch domain intelligence lookups for up to 100 distinct domains via the public WhoisMD API. Each entry is analyzed concurrently with bounded parallelism. Returns per-domain success/failure results with risk scores. |
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 are clearly distinct: one handles a single domain lookup, the other handles batch processing of many domains. There is no ambiguity in their purposes.
Both tools follow a consistent verb_noun pattern using snake_case with the same whoismd_ prefix: whoismd_lookup and whoismd_bulk. The naming is predictable and uniform.
With only two tools, the server is quite thin for a domain intelligence service. While each tool is useful, the absence of operations like historical data, reverse WHOIS, or alerting makes the count feel borderline minimal.
The server covers basic single and bulk lookups, but lacks other common domain intelligence operations such as historical WHOIS, reverse IP lookups, or real-time monitoring. These gaps may limit its usefulness for advanced workflows.