Remote MCP · Endpoint
com.remote-mcp/registry-mcp MCP server
No. com.remote-mcp/registry-mcp answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://registry-mcp.remote-mcp.com/
The last check completed an MCP handshake.
- Registry name
- com.remote-mcp/registry-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 461 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- An MCP server that serves informtaion from the official MCP registry
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 461 ms |
| 2 days ago | Handshake completed | 613 ms |
| 4 days ago | Handshake completed | 436 ms |
| 5 days ago | Handshake completed | 453 ms |
| 7 days ago | Handshake completed | 325 ms |
| 8 days ago | Handshake completed | 698 ms |
| 9 days ago | Handshake completed | 508 ms |
| 12 days ago | Handshake completed | 338 ms |
| 13 days ago | Handshake completed | 357 ms |
| 15 days ago | Handshake completed | 425 ms |
| 16 days ago | Handshake completed | 433 ms |
| 17 days ago | Handshake completed | 333 ms |
| 18 days ago | Handshake completed | 402 ms |
| 19 days ago | Handshake completed | 561 ms |
| 20 days ago | Handshake completed | 570 ms |
| 21 days ago | Handshake completed | 400 ms |
| 22 days ago | Handshake completed | 576 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 com.remote-mcp/registry-mcp and makes no claim about it beyond what these checks measured.