# RDAP API

> Normalized JSON for any domain across 1,200+ TLDs, reading WHOIS where no RDAP server exists.

- name: io.rdapapi/rdap
- version: 1.3.0
- connection class: R0 (autonomous)
- trust: 82/100 flags: no-repository
- quality: 87/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.rdapapi%2Frdap
- tools: https://api.protogrid.dev/v1/servers/io.rdapapi%2Frdap/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "rdap": {
      "type": "http",
      "url": "https://rdapapi.io/mcp/rdap",
      "headers": {
        "Authorization": "Bearer ${RDAP_TOKEN}"
      }
    }
  }
}
```

Placeholders to fill: `${RDAP_TOKEN}`.

## Trust

- hygiene: 80
- liveness: 99
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-97% +updated-10d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 87/100 (good)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 7 of 7 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: domain-lookup (idempotentHint); bulk-domain-lookup (idempotentHint); tlds (idempotentHint); …
- pass `tools.token_cost`: about 1,088 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history recorded for 1 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 7, about 1,088 tokens to load them all
- tool set hash: f89343ca71e35ebc97ba0e05ac3d39af
- badge: [![protogrid quality](https://protogrid.dev/badge/io.rdapapi/rdap.svg)](https://protogrid.dev/servers/io.rdapapi/rdap)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://rdapapi.io/mcp/rdap (streamable-http, auth none, reachable true, uptime30d 0.9652174)

## Packages

_none_

## Tools (7)

- `asn-lookup`: Look up normalized RDAP data (holder, country, status, registration dates) for an autonomous system number.
- `bulk-domain-lookup`: Look up normalized RDAP registration data for several domain names in one pooled call. Requires a Pro or Business plan; every domain in the batch counts against the quota.
- `domain-lookup`: Look up normalized RDAP registration data (registrar, status, dates, nameservers, contacts) for a domain name.
- `entity-lookup`: Look up normalized RDAP data for an RIR entity handle — an organization or contact identifier such as "GOGL" or "ORG-RIEN1-RIPE". Only ARIN, RIPE, APNIC, LACNIC and AFRINIC handles resolve; a domain's registrar or registrant comes from domain-lookup instead.
- `ip-lookup`: Look up normalized RDAP allocation data (network range, holder, country, status, geofeed URL) for an IP address or CIDR block.
- `nameserver-lookup`: Look up normalized RDAP data (IP addresses, status, sponsoring registrar) for a nameserver hostname.
- `tlds`: List the TLDs this API can query, or describe one: which RDAP server answers for it, since when it has been supported, and how often that server fills each field. Metadata, so it never counts against the monthly quota.