Log inSubmit server
Rdap logo

Rdap

Query public RDAP records for domains, IPs, ASNs, entities, and nameservers through MCP or HTTP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Rdap

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "rdap": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-rdap"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Rdap MCP server queries public registry RDAP services for domain, IP, ASN, entity, and nameserver records. It discovers endpoints through IANA bootstrap data, with bundled fallback bases for several omitted TLDs, and accepts an optional registry base for supported queries. Reach for it when an agent needs structured registration data or domain availability checks without credentials. It runs as a hosted MCP endpoint, a local stdio server, or through HTTP tool calls.

Use cases

  • Check whether a domain has a registration record
  • Inspect registrar and domain lifecycle details
  • Look up IP, netblock, or ASN allocation data
  • Resolve registry entities and nameserver records

Key features

  • Domain registration and availability lookups
  • IP and netblock allocation queries
  • ASN allocation queries
  • Entity and nameserver lookups
  • IANA bootstrap discovery with TLD fallbacks
  • Hosted, local stdio, and HTTP access

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · @pipeworx/mcp-rdap (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads470Package downloads in the last 30 days.
Last commit26d agoMost recent push to the default branch.

How Rdap works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Rdap

Rdap is an MCP server that connects AI clients to public RDAP registry services. Its main tools query domains, IP addresses, ASNs, registry entities, and nameservers. It uses IANA bootstrap data plus selected TLD fallbacks, requires no API key, and can run through a hosted gateway or as a local stdio process.

Run `npx -y @pipeworx/mcp-rdap` as a local stdio server, or add that command and argument to your MCP client's server configuration. You can instead configure the hosted URL `https://gateway.pipeworx.io/rdap/mcp`.

Configure Cursor with either the hosted Rdap gateway URL or the local `npx -y @pipeworx/mcp-rdap` command.

Yes, the domain tool treats a registry 404 as a structured unregistered result. Availability checks can be misleading when a TLD has no public RDAP service or when an incorrect fallback endpoint is used, so verify custom `base` endpoints carefully.

No, the described RDAP requests use public registry services and require no authentication. The standalone package also runs without a Pipeworx account or gateway round-trip.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewRdap AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/rdap?style=directory)](https://allmcps.com/mcp/rdap)
HTML Embed
<a href="https://allmcps.com/mcp/rdap"><img src="https://allmcps.com/api/badge/rdap?style=directory" alt="Rdap on AllMCPs" /></a>