RDAP MCP Server

The RDAP MCP Server provides a lightweight, protocol‑first interface for retrieving authoritative registration data for domains, IP addresses, and autonomous system numbers (ASNs). By leveraging the RDAP standard defined by ICANN, it enables AI assistants to query up‑to‑date registry information without the need for legacy WHOIS clients or custom parsers. This is especially valuable as many top‑level domains (e.g., ) have phased out the WHOIS protocol in favor of RDAP, making a dedicated RDAP service essential for accurate, real‑time lookups.

The server exposes three intuitive tools—, , and —each mapping a single query parameter to the corresponding RDAP endpoint. Developers can invoke these tools from within an AI workflow, passing a domain name or IP address and receiving a structured JSON payload that includes registrant details, status flags, and related resources. The simplicity of the API means it can be integrated into a wide range of use cases, from automated compliance checks to dynamic content generation that references domain ownership or IP geolocation.

Key capabilities of the RDAP MCP Server include:

• Protocol compliance: Uses the official RDAP specifications, ensuring compatibility with all registries that support it.
• Cross‑resource support: Handles domains, IP blocks, and ASNs in a single unified service.
• Stateless Docker deployment: Runs as a containerized MCP server, making it trivial to spin up in CI/CD pipelines or cloud functions.
• Built‑on existing tooling: Forked from the proven whois-mcp project, it inherits a mature tool‑registration framework while adding RDAP support.

Typical scenarios where this server shines are:

• Security audits: Quickly resolve IPs to their registries for threat intelligence or incident response.
• Domain portfolio management: Automate checks on domain status, expiry dates, and ownership changes.
• Network engineering: Enrich routing tables with ASN registration data for better policy enforcement.

Integrating the RDAP MCP Server into an AI workflow is straightforward. An assistant can send a JSON request to the tool, receive the parsed registration data, and then use that information to answer user queries or trigger downstream processes. Because the server adheres to MCP’s resource‑tool paradigm, it fits seamlessly into any existing model context setup without requiring custom adapters.

In summary, the RDAP MCP Server fills a critical gap for developers needing reliable, up‑to‑date registry information within AI applications. Its focus on RDAP compliance, combined with a minimalistic Docker‑friendly deployment model, makes it an ideal choice for modern, cloud‑native workflows that demand accurate domain and network metadata.