RDAP API

io.rdapapiPublished by rdapapi.ioOfficial publisherv1.3.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Lets an assistant look up registration data for domains across 1,200+ TLDs, returning normalized JSON.

What you can do
This remote MCP server provides domain registration lookups, returning normalized JSON for any domain across more than 1,200 TLDs. Where no RDAP server exists for a TLD, it falls back to reading WHOIS data. It connects over streamable HTTP at a hosted endpoint, so no local package is installed.
When to use it
Useful when an assistant needs registration details for a domain, such as checking who a domain belongs to or when it was registered, and you want consistent JSON rather than parsing raw WHOIS text yourself.
Requirements
A remote MCP client that supports streamable HTTP. An rdapapi.io API key is required for lookups, sent as an Authorization bearer header; clients that sign in with OAuth may not need it. Connecting and listing tools works without a key.
Before you install
Lookups require an API key sent in the Authorization header, so treat that credential as a secret. Domain lookups are sent to the third-party rdapapi.io service, and usage may be subject to that provider's terms or quotas.

Installation

In SourceWeft

  1. Open RDAP API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.rdapapi%2Frdap/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "rdap-api": {
      "type": "http",
      "url": "https://rdapapi.io/mcp/rdap"
    }
  }
}

Tools

7

domain-lookup

Domain Lookup

Look up normalized RDAP registration data (registrar, status, dates, nameservers, contacts) for a domain name.

Parameterswhoisdomainrequiredfollow

bulk-domain-lookup

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.

Parameterswhoisfollowdomainsrequired

ip-lookup

IP Address Lookup

Look up normalized RDAP allocation data (network range, holder, country, status, geofeed URL) for an IP address or CIDR block.

Parametersiprequiredprefix

asn-lookup

ASN Lookup

Look up normalized RDAP data (holder, country, status, registration dates) for an autonomous system number.

Parametersasnrequired

nameserver-lookup

Nameserver Lookup

Look up normalized RDAP data (IP addresses, status, sponsoring registrar) for a nameserver hostname.

Parametershostrequired

entity-lookup

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.

Parametershandlerequired

tlds

Supported 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.

Parameterstldsinceserver

Version history

2
  1. v1.3.0LatestOct 10, 2026
  2. v1.2.0Sep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.