Remote MCP · Endpoint
Resident Advisor MCP server
No. Resident Advisor answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://gateway.pipeworx.io/resident-advisor/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.pipeworx-io/resident-advisor
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 169 ms
- Tools exposed
- 49 tools
- Uptime, last 30 days
- 100% from 13 checks
- Described by its publisher as
- Resident Advisor (ra.co) MCP.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 169 ms |
| 1 day ago | Handshake completed | 168 ms |
| 2 days ago | Handshake completed | 87 ms |
| 3 days ago | Handshake completed | 188 ms |
| 4 days ago | Handshake completed | 65 ms |
| 5 days ago | Handshake completed | 124 ms |
| 7 days ago | Handshake completed | 106 ms |
| 9 days ago | Handshake completed | 117 ms |
| 12 days ago | Handshake completed | 244 ms |
| 14 days ago | Handshake completed | 287 ms |
| 17 days ago | Handshake completed | 72 ms |
| 18 days ago | Handshake completed | 172 ms |
| 21 days ago | Handshake completed | 53 ms |
The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.
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 Resident Advisor and makes no claim about it beyond what these checks measured.