MCP server

Give an AI agent normalized domain, IP, ASN, nameserver and entity lookups over the Model Context Protocol. Same API key as the REST API, same quota, no separate billing.

Connect

The server speaks streamable HTTP. Point any MCP client at the endpoint below and authenticate with your API key as a bearer token. Connecting and listing the tools works without a key, so you can inspect the server first; every lookup needs one.

Endpoint

https://rdapapi.io/mcp/rdap

In Claude Code:

Terminal

claude mcp add --transport http rdapapi https://rdapapi.io/mcp/rdap \
  --header "Authorization: Bearer YOUR_API_KEY"

Or, for a client that reads a JSON config — Cursor and most others supporting remote servers:

MCP client config

{
  "mcpServers": {
    "rdapapi": {
      "type": "http",
      "url": "https://rdapapi.io/mcp/rdap",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Claude Desktop's config file accepts stdio servers only, so connect this one through a custom connector or an mcp-remote bridge rather than pasting the JSON above.

Tools

Tool	Arguments	Returns
`domain-lookup`	domain (required), follow (optional)	Registrar, status, key dates, nameservers, contacts
`ip-lookup`	ip (required), prefix (optional)	Network range, holder, country, status
`asn-lookup`	asn (required)	Holder, country, registration dates
`nameserver-lookup`	host (required)	IP addresses, status, sponsoring registrar
`entity-lookup`	handle (required)	Registrar, registrant or contact record

Quota and billing

Each successful lookup counts once against your monthly plan quota, on the same terms as the equivalent REST endpoint. A "not found" is a real answer and counts too. Protocol traffic that every client sends on connect — initialize, tools/list — is free, and invalid arguments are rejected before anything is billed.

An MCP call and a REST call draw on one shared quota, so you can mix both without tracking two budgets.

Get your API key

Plans start at $9/mo with a 7-day free trial. See pricing