# Rdap [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/pipeworx-io/mcp-rdap  
**GitHub Stars:** 0  
**npm Downloads (last month):** 470  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/rdap

## Description
RDAP — Registration Data Access Protocol (domains, IPs, ASNs) via IANA bootstrap

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "rdap": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-rdap"]
  }
}
```

## Documentation

## What Rdap MCP server does

The Rdap MCP server exposes Registration Data Access Protocol lookups to MCP clients. RDAP is the structured-JSON successor to WHOIS, and the responses come from public registry services rather than a private data store. Queries cover domain registration details, IP or netblock allocation, autonomous system numbers, registry entities, and nameserver records.

The Rdap MCP server is useful for investigations and automation that need registrar information, registration and expiration dates, domain status, nameservers, allocation records, or registry handles. A missing domain is represented as a result such as `{registered: false}` rather than treated as a transport failure, which supports availability checks.

## How it works

For domain and related registry lookups, the service consults IANA RDAP bootstrap data to identify the relevant registry endpoint. It also includes fallback bases for selected TLDs missing from that bootstrap file, including `.io`, `.de`, `.us`, `.me`, `.ch`, `.li`, `.sg`, `.my`, and `.ws`.

Coverage is not universal. Some delegated TLDs do not publish a public RDAP service, and an omitted TLD can be different from an unregistered domain. In those cases, the domain tool returns a structured result indicating that the TLD is absent from the IANA bootstrap data and can suggest supplying a known registry endpoint through `base`.

## Setup and configuration

The Rdap MCP server can be added as a hosted endpoint at `https://gateway.pipeworx.io/rdap/mcp`, or run locally with `npx -y @pipeworx/mcp-rdap`. The local process communicates over stdin and stdout and does not require a Pipeworx account. The hosted endpoint requires no authentication for the described public RDAP queries.

A client can also use the full Pipeworx gateway at `https://gateway.pipeworx.io/mcp`. The pack endpoint lists the Rdap tools together with shared gateway meta-tools, while the standalone process exposes only the pack's tools. HTTP callers can invoke tools such as `rdap_domain` through the gateway's `/v1/tools/` interface.

## Tools and capabilities

The Rdap MCP server provides these pack-specific operations:

- `domain(name | domain, base?)` retrieves domain registration data and handles registry 404 responses as availability information.
- `ip(address | ip)` looks up an IP address or netblock allocation.
- `asn(number)` retrieves an autonomous system allocation record.
- `entity(handle, base?)` looks up a registry entity by handle.
- `nameserver(host, base?)` retrieves a nameserver or glue record where the registry supports it.

The optional `base` argument allows a caller to provide a registry RDAP endpoint when automatic discovery does not cover the TLD. Registry endpoints should be validated carefully: a base that does not serve a TLD may return a normal RDAP 404 and incorrectly resemble an available domain.

## Limitations and notes

No API key or other authentication is described for the public registry requests. Results depend on the availability, accuracy, and coverage of individual RIR and registry RDAP services. The bundled fallback list is intended to address known IANA bootstrap omissions, not to provide every TLD with RDAP coverage.

The hosted connection also exposes shared Pipeworx tools, and its exact tool list may change. The local package avoids those shared tools and does not provide cross-catalog `ask_pipeworx` routing. For TLDs with no public RDAP service, the appropriate alternative may be the registry's own WHOIS page or another registry-provided endpoint.

_Full upstream README: https://allmcps.com/mcp/rdap/readme_