@pipeworx/rdap

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/rdap’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 5

RDAP MCP — Registration Data Access Protocol queries for domains, IPs, ASNs and nameservers. The structured-JSON successor to WHOIS, answered by the registry’s own service. Keyless.

Tools

• domain(name | domain, base?) — domain registration record: registrar, registration/expiry dates, nameservers, status. A registry 404 is an answer, not an error — it comes back as {registered: false}, which is what makes availability sweeps work.
• ip(address | ip) — IP / netblock allocation record
• asn(number) — ASN allocation record
• entity(handle, base?) — registry entity by handle (e.g. registrant id)
• nameserver(host, base?) — nameserver (glue) record, where the registry supports it

Auth

None. Every endpoint queried is a public registry RDAP service.

TLD coverage — and the gap in IANA’s bootstrap

Server discovery normally goes through IANA’s RDAP bootstrap (https://data.iana.org/rdap/dns.json, cached 24h). That file is incomplete. As of publication 2026-07-23 it lists 1,200 of the 1,438 delegated TLDs; the 238 it omits are almost entirely ccTLDs that never registered their RDAP endpoint with IANA. Measured against the Majestic Million on 2026-08-30, those 238 TLDs carry 23.4% of the world’s most-linked domains — including .io, .de, .us, .me and .ru.

So the pack carries FALLBACK_BASES (see src/index.ts): registry RDAP endpoints for TLDs IANA omits. IANA is still consulted first, so the map goes quiet on its own the day a registry is added upstream. Currently covered beyond IANA:

Adding a TLD to that map — read this first. Verify by fetching <base>/domain/<a-name-you-know-is-REGISTERED> and requiring HTTP 200 with a real record. rdap.identitydigital.services returns a well-formed RDAP 404 for TLDs it does not serve, so a 404 there is indistinguishable from “this domain is unregistered”. A wrong base URL therefore does not error — it reports every registered domain in that TLD as available. That is the failure this pack is built to avoid.

Many ccTLDs run no public RDAP service at all. Probed 2026-08-30, the conventional rdap.* hostnames for .ru, .it, .eu, .se and .co do not resolve (NXDOMAIN), so there is nothing to add to the map for them. For those, domain returns {found: false, reason: "tld_not_in_iana_bootstrap"} with a message saying the gap is IANA’s rather than ours, plus a hint: pass the registry’s own endpoint as base if you know it, otherwise use that registry’s WHOIS page. It deliberately does not throw — an upstream registry gap is not a Pipeworx defect and should not book as one.

Data sources

• IANA RDAP bootstrap: https://data.iana.org/rdap/dns.json (+ ipv4, ipv6, asn)
• IANA delegated-TLD list: https://data.iana.org/TLD/tlds-alpha-by-domain.txt
• Individual RIR / registry RDAP servers reached via the above

Tools

• rdap_domain — Domain registration record from RDAP — the registry’s raw record (registrar, registration/expiry dates, nameservers, status) plus a normalised summary block that also follows the registrar’s own rec
• rdap_ip — WHICH COMPANY OWNS THIS IP — the one tool to call for “who owns ”, “what network is in”, “ASN / network range / owner of ”. Returns an owner block with ASN, owner name, network range (
• asn — ASN allocation record.
• rdap_entity — Entity by handle. Pass base RDAP url to skip bootstrap.
• nameserver — Nameserver (glue) record from RDAP — the registry’s record for a host like “ns1.example.com”, with its IP addresses and status. Answers “what are the IPs behind this nameserver” and “is this nameserve