RDAP API
Normalized JSON for any domain across 1,200+ TLDs, reading WHOIS where no RDAP server exists.
Sollte ich dies verwenden
Qualität und Sicherheit
Befunde (7)
- LOWin domain-lookup
- LOWin domain-lookup
- LOWin bulk-domain-lookup
- LOWin ip-lookup
- LOWin asn-lookup
- LOWin nameserver-lookup
- LOWin entity-lookup
Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.
Kontextkosten
Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.
Installieren
Installation mit einem Klick
Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:
{
"mcpServers": {
"rdap": {
"url": "https://rdapapi.io/mcp/rdap"
}
}
}Remote-Endpunkte
https://rdapapi.io/mcp/rdapstreamable-httpWas es kann
Tool-Inventar
Tools (7)
⚪domain-lookup(domain, follow, whois)
Look up normalized RDAP registration data (registrar, status, dates, nameservers, contacts) for a domain name.
Eingabe-Schema
{
"type": "object",
"properties": {
"domain": {
"description": "The domain name to look up, e.g. \"example.com\". Unicode (IDN) names are accepted.",
"type": "string"
},
"follow": {
"description": "Follow the registrar RDAP link for richer data on thin registries such as .com and .net. Slower; defaults to false.",
"default": false,
"type": "boolean"
},
"whois": {
"description": "Set false to refuse the WHOIS fallback, so a TLD with no RDAP server errors instead of answering over port 43. Defaults to true.",
"default": true,
"type": "boolean"
}
},
"required": [
"domain"
]
}⚪bulk-domain-lookup(domains, follow, whois)
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.
Eingabe-Schema
{
"type": "object",
"properties": {
"domains": {
"description": "The domain names to look up, e.g. [\"example.com\", \"example.net\"]. Between 1 and 10 per call. Unicode (IDN) names are accepted.",
"minItems": 1,
"maxItems": 10,
"items": {
"type": "string"
},
"type": "array"
},
"follow": {
"description": "Follow the registrar RDAP link for richer data on thin registries such as .com and .net. Slower; defaults to false.",
"default": false,
"type": "boolean"
},
"whois": {
"description": "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.",
"default": true,
"type": "boolean"
}
},
"required": [
"domains"
]
}⚪ip-lookup(ip, prefix)
Look up normalized RDAP allocation data (network range, holder, country, status, geofeed URL) for an IP address or CIDR block.
Eingabe-Schema
{
"type": "object",
"properties": {
"ip": {
"description": "IPv4 or IPv6 address, e.g. \"8.8.8.8\" or \"2001:4860:4860::8888\".",
"type": "string"
},
"prefix": {
"description": "Optional CIDR prefix length, e.g. 24. Must be 0-32 for IPv4 or 0-128 for IPv6.",
"type": "integer"
}
},
"required": [
"ip"
]
}⚪asn-lookup(asn)
Look up normalized RDAP data (holder, country, status, registration dates) for an autonomous system number.
Eingabe-Schema
{
"type": "object",
"properties": {
"asn": {
"description": "Autonomous system number, e.g. \"15169\" or \"AS15169\".",
"type": "string"
}
},
"required": [
"asn"
]
}⚪nameserver-lookup(host)
Look up normalized RDAP data (IP addresses, status, sponsoring registrar) for a nameserver hostname.
Eingabe-Schema
{
"type": "object",
"properties": {
"host": {
"description": "Nameserver hostname, e.g. \"ns1.example.com\".",
"type": "string"
}
},
"required": [
"host"
]
}⚪entity-lookup(handle)
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.
Eingabe-Schema
{
"type": "object",
"properties": {
"handle": {
"description": "RIR entity handle, e.g. \"GOGL\" (ARIN) or \"ORG-RIEN1-RIPE\" (RIPE).",
"type": "string"
}
},
"required": [
"handle"
]
}🟢tlds(tld, server, since)
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.
Eingabe-Schema
{
"type": "object",
"properties": {
"tld": {
"description": "A single TLD to describe, e.g. \"com\" or \".io\". Omit to list every supported TLD by name.",
"type": "string"
},
"server": {
"description": "List only the TLDs served by this host, RDAP or WHOIS, e.g. \"rdap.verisign.com\". Ignored when \"tld\" is given.",
"type": "string"
},
"since": {
"description": "List only the TLDs added after this ISO 8601 date, e.g. \"2026-01-01\". Ignored when \"tld\" is given.",
"type": "string"
}
}
}Community
Nachweis