RDAP API

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

使うべきか

品質と安全性

A
説明の品質
96%
スキーマの完全性
99%
命名の品質
54%
ポイズニングのリスク
100%
権限の一致
100%
プロトコルへの準拠
100%

検出事項(7)

  • LOWTool 'domain-lookup' description lacks action verbdomain-lookup 内
  • LOWTool 'domain-lookup' doesn't follow camelCase/snake_casedomain-lookup 内
  • LOWTool 'bulk-domain-lookup' doesn't follow camelCase/snake_casebulk-domain-lookup 内
  • LOWTool 'ip-lookup' doesn't follow camelCase/snake_caseip-lookup 内
  • LOWTool 'asn-lookup' doesn't follow camelCase/snake_caseasn-lookup 内
  • LOWTool 'nameserver-lookup' doesn't follow camelCase/snake_casenameserver-lookup 内
  • LOWTool 'entity-lookup' doesn't follow camelCase/snake_caseentity-lookup 内

ツール定義とプロトコルへの準拠に関する自動分析に基づいています。

コンテキストコスト

~1,039トークン数(ツール定義)
~1.0 KB一般的なレスポンスサイズ
注意への影響は中程度(128k コンテキストの 0.81%)

これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。

インストール

ワンクリックインストール

これを `claude_desktop_config.json` ファイルに追加してください:

{
  "mcpServers": {
    "rdap": {
      "url": "https://rdapapi.io/mcp/rdap"
    }
  }
}

リモートエンドポイント

https://rdapapi.io/mcp/rdapstreamable-http

できること

ツール一覧

ツール(7)

🟢 読み取り専用🟡 書き込み🔴 削除⚪ 不明
⚪domain-lookup(domain, follow, whois)

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

入力スキーマ

{
  "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.

入力スキーマ

{
  "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.

入力スキーマ

{
  "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.

入力スキーマ

{
  "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.

入力スキーマ

{
  "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.

入力スキーマ

{
  "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.

入力スキーマ

{
  "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"
    }
  }
}

コミュニティ

このサーバーを評価する

エビデンス

最近の観測

検証済みバージョンは記録されていませんツール 7 件
検証済みバージョンは記録されていませんツール 7 件