RDAP API
REMOTE · RDAPAPI.IO · SCANNED SEP 21
Normalized JSON for any domain across 1,200+ TLDs, reading WHOIS where no RDAP server exists.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1291 tokens (~184/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the RDAP API MCP server?
RDAP API is a hosted endpoint at https://rdapapi.io/mcp/rdap, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · rdapapi.io
claude mcp add --transport http io-rdapapi-rdap 'https://rdapapi.io/mcp/rdap'
{
"mcpServers": {
"io-rdapapi-rdap": {
"url": "https://rdapapi.io/mcp/rdap"
}
}
} {
"servers": {
"io-rdapapi-rdap": {
"type": "http",
"url": "https://rdapapi.io/mcp/rdap"
}
}
} [mcp_servers.io-rdapapi-rdap] url = "https://rdapapi.io/mcp/rdap"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-rdapapi-rdap": {
"type": "remote",
"url": "https://rdapapi.io/mcp/rdap",
"enabled": true
}
}
} openclaw mcp add io-rdapapi-rdap --url 'https://rdapapi.io/mcp/rdap' --transport streamable-http
mcp_servers:
io-rdapapi-rdap:
url: "https://rdapapi.io/mcp/rdap" {
"McpServers": {
"io-rdapapi-rdap": {
"Transport": "http",
"Url": "https://rdapapi.io/mcp/rdap"
}
}
} assistant mcp add io-rdapapi-rdap -t streamable-http -u 'https://rdapapi.io/mcp/rdap'
{
"mcpServers": {
"io-rdapapi-rdap": {
"type": "http",
"url": "https://rdapapi.io/mcp/rdap"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ip-lookup” rewrote its description, which is the text the model reads security
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://rdapapi.io/mcp/rdap
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rdapapi.io | CN=YE2,O=Let's Encrypt,C=US | 17 Aug 2026 | 15 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 67f1221ef4c6ab25882deefada995c00707 |
| SANs: *.rdapapi.io, rdapapi.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of rdapapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| rdapapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp", error="invalid_token"
Bearer realm="mcp", error="invalid_token"| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rdapapi.io/mcp/rdap | Verified | 200 | |
| http (plaintext) | http://rdapapi.io/mcp/rdap | HTTPS enforced | 301 | https://rdapapi.io/mcp/rdap |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
asn-lookup Asn Lookup Tool ~56
Look up normalized RDAP data (holder, country, status, registration dates) for an autonomous system number.
| Name | Type | Req | Description |
|---|---|---|---|
| asn | string | yes | Autonomous system number, e.g. "15169" or "AS15169". |
No output schema declared.
No examples provided.
bulk-domain-lookup Bulk Domain Lookup Tool ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | The domain names to look up, e.g. ["example.com", "example.net"]. Between 1 and 10 per call. Unicode (IDN) names are accepted. |
| follow | boolean | – | Follow the registrar RDAP link for richer data on thin registries such as .com and .net. Slower; defaults to false. |
| whois | boolean | – | Set false to refuse the WHOIS fallback for every domain in the batch, so a TLD with no RDAP server returns not_supported. Defaults to true. |
No output schema declared.
No examples provided.
domain-lookup Domain Lookup Tool ~135
Look up normalized RDAP registration data (registrar, status, dates, nameservers, contacts) for a domain name.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain name to look up, e.g. "example.com". Unicode (IDN) names are accepted. |
| follow | boolean | – | Follow the registrar RDAP link for richer data on thin registries such as .com and .net. Slower; defaults to false. |
| whois | boolean | – | Set false to refuse the WHOIS fallback, so a TLD with no RDAP server errors instead of answering over port 43. Defaults to true. |
No output schema declared.
No examples provided.
entity-lookup Entity Lookup Tool ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | RIR entity handle, e.g. "GOGL" (ARIN) or "ORG-RIEN1-RIPE" (RIPE). |
No output schema declared.
No examples provided.
ip-lookup Ip Lookup Tool ~115
Look up normalized RDAP allocation data (network range, holder, country, status, geofeed URL) for an IP address or CIDR block.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | IPv4 or IPv6 address, e.g. "8.8.8.8" or "2001:4860:4860::8888". |
| prefix | integer | – | Optional CIDR prefix length, e.g. 24. Must be 0-32 for IPv4 or 0-128 for IPv6. |
No output schema declared.
No examples provided.
nameserver-lookup Nameserver Lookup Tool ~50
Look up normalized RDAP data (IP addresses, status, sponsoring registrar) for a nameserver hostname.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Nameserver hostname, e.g. "ns1.example.com". |
No output schema declared.
No examples provided.
tlds Tlds Tool ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | – | List only the TLDs served by this host, RDAP or WHOIS, e.g. "rdap.verisign.com". Ignored when "tld" is given. |
| since | string | – | List only the TLDs added after this ISO 8601 date, e.g. "2026-01-01". Ignored when "tld" is given. |
| tld | string | – | A single TLD to describe, e.g. "com" or ".io". Omit to list every supported TLD by name. |
No output schema declared.
No examples provided.
What is the RDAP API MCP server?
RDAP API is an MCP server listed in the public MCP registry as io.rdapapi/rdap. Normalized JSON for any domain across 1,200+ TLDs, reading WHOIS where no RDAP server exists. This page covers its hosted endpoint (https://rdapapi.io/mcp/rdap).
Is the RDAP API MCP server safe to use?
RDAP API scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the RDAP API MCP server expose?
RDAP API exposes 7 tools: domain-lookup, bulk-domain-lookup, ip-lookup, asn-lookup, nameserver-lookup, and 2 more. Their descriptions and schemas cost roughly 803 tokens of context every time the server is loaded.
Does the RDAP API MCP server require authentication?
Yes. RDAP API asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the RDAP API MCP server still maintained?
RDAP API is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.