WHOIS and RDAP MCP retrieves domain, IP and ASN registration data through a Go service with a Streamable HTTP endpoint.
WHOIS and RDAP MCP retrieves domain, IP and ASN registration data through a Go service with a Streamable HTTP endpoint.
The service exposes its existing WHOIS and RDAP lookup interface through MCP at /mcp. An assistant can request registration data for a domain, an internationalized domain name, an IP address, a CIDR prefix or an autonomous system number. Returned records support checks such as expiry information and DNSSEC status, subject to what the upstream registry actually provides.
The documented endpoint uses stateless Streamable HTTP with JSON responses. It does not require an SSE client. The repository supplies a public demonstration URL and instructions for self-hosted instances. Authentication depends on the deployment: instances with configured API keys require an authorization or API-key header.
The single-lookup tool is the basic interface. Batch lookup requires the operator to enable it, applies a configured maximum item count and accounts for each query in the rate limit. Do not assume the public demo offers unrestricted bulk requests just because the project implements a batch tool.
Start with a domain whose registration details you can verify elsewhere. Compare the registry fields, expiry value and DNSSEC result with the response, and account for server caching. Redacted registrant information is an upstream limitation, not a reason to infer missing identity details. For operational use, choose a deployment with suitable availability and access controls.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| whois_lookup | Retrieve WHOIS/RDAP-style data for a domain, IP, CIDR or ASN. |
| whois_batch_lookup | Query several identifiers when batch lookup is enabled by the operator. |
{
"mcpServers": {
"whois": {
"url": "https://whois.ddnsip.cn/mcp"
}
}
}The documented public demo is a separate deployment from an instance you operate. Check its availability and limits.
A Streamable HTTP MCP client. API-key headers are needed only for deployments that enable authentication.
Retrieve public web pages as readable Markdown with the reference Fetch MCP server, including pagination for longer responses.
Use Firecrawl MCP to retrieve website content and extract information for research through Firecrawl’s API-backed web tools.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Automates browsers and APIs, enabling Large Language Models (LLMs) to interact with web pages for tasks like screenshot capture and JavaScript
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.