Self-hosted WHOIS and RDAP API for AI-driven investigations
whois, from KincaidYang, is a self-hosted MCP server that exposes WHOIS and RDAP registration data to AI agents. The tool functions as a WHOIS/RDAP API and MCP-compatible service allowing assistants to query domains, IPv4 and IPv6 addresses, CIDR blocks, and ASNs directly inside chat clients. It includes a raw WHOIS text mode, regularly updated IANA server lists, and deployment options via Go binaries or Docker for local control. Intended users are cybersecurity researchers, network administrators, and AI developers who need verifiable registration data inside automated workflows.
What tasks can you actually use it for?
The app is built for discovery and verification of registration records. It accepts queries for domain names, IPv4 and IPv6 addresses, CIDR blocks, and Autonomous System Numbers, and returns registration fields such as ownership and expiration details. AI agents connected over MCP can run these lookups inside chat sessions, which helps automate routine checks like ownership confirmation and initial footprinting.
How reliable and useful are its outputs for investigations?
Outputs come in both structured and raw forms, which affects how you validate results. The tool supports RDAP for structured responses and a raw WHOIS text mode for the original server output, letting analysts choose parsed or original records. Regular updates to the IANA server list extend TLD coverage, yet registry records themselves still require independent verification during incident response.
Does it fit into existing AI security workflows?
The integration model is suitable for teams that operate MCP-capable clients and host services. The server runs from Go binaries or Docker and is compatible with MCP clients such as Claude Desktop, Cursor, and Windsurf, so it fits into agent-driven pipelines. It can be configured with authentication for public exposure, and it is described as lightweight and tuned for high-performance network lookups, which reduces resource friction during repeated queries.
A practical choice for teams prepared to host and maintain a registry data source
The tool suits security teams and AI developers who accept the operational overhead of a self-hosted service and need direct programmatic access to registration records inside model workflows. Expect to operate and secure the service, and to treat returned registry information as evidence that requires independent confirmation during investigations.
