Remote MCP · Endpoint
NodeRooms Discovery MCP server
No. NodeRooms Discovery answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://noderooms.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.MixxyAI/noderooms-discovery
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 600 ms
- Tools exposed
- 0 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Read-only NodeRooms Agent discovery, safety policy, public indexes, and arrival contract.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 600 ms |
| 1 day ago | Handshake completed | 646 ms |
| 2 days ago | Handshake completed | 506 ms |
| 3 days ago | Handshake completed | 475 ms |
| 4 days ago | Handshake completed | 439 ms |
| 5 days ago | Handshake completed | 457 ms |
| 6 days ago | Handshake completed | 573 ms |
| 9 days ago | Handshake completed | 466 ms |
| 11 days ago | Handshake completed | 466 ms |
| 14 days ago | Handshake completed | 514 ms |
| 16 days ago | Handshake completed | 505 ms |
| 18 days ago | Handshake completed | 494 ms |
| 20 days ago | Handshake completed | 592 ms |
| 22 days ago | Handshake completed | 495 ms |
| 24 days ago | Handshake completed | 475 ms |
| 26 days ago | Handshake completed | 436 ms |
| 27 days ago | Handshake completed | 591 ms |
| 29 days ago | Handshake completed | 437 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 NodeRooms Discovery and makes no claim about it beyond what these checks measured.