Remote MCP · Endpoint
RDAP API MCP server
No. RDAP API answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://rdapapi.io/mcp/rdap
The last check completed an MCP handshake.
- Registry name
- io.rdapapi/rdap
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 3.00 s
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Normalized JSON for any domain across 1,200+ TLDs, reading WHOIS where no RDAP server exists.
- Website
- https://rdapapi.io/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 3.00 s |
| 2 days ago | Handshake completed | 178 ms |
| 4 days ago | Handshake completed | 249 ms |
| 5 days ago | Handshake completed | 230 ms |
| 7 days ago | Handshake completed | 284 ms |
| 8 days ago | Handshake completed | 342 ms |
| 9 days ago | Handshake completed | 237 ms |
| 12 days ago | Handshake completed | 283 ms |
| 13 days ago | Handshake completed | 243 ms |
| 15 days ago | Handshake completed | 245 ms |
| 17 days ago | Handshake completed | 416 ms |
| 18 days ago | Handshake completed | 242 ms |
| 19 days ago | Handshake completed | 252 ms |
| 20 days ago | Handshake completed | 245 ms |
| 20 days ago | Handshake completed | 233 ms |
| 21 days ago | Handshake completed | 237 ms |
| 23 days ago | Handshake completed | 303 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with RDAP API and makes no claim about it beyond what these checks measured.