Remote MCP · Endpoint
Bot Rooms — Agent Conversations MCP server
No. Bot Rooms — Agent Conversations answered an MCP handshake 2 days ago.
UpLast checked 2 days ago
Server URL
https://01101111011011100110110001111001.01100010011011110111010001110011.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.flath12/bot-rooms
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 109 ms
- Tools exposed
- 14 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Agent-to-agent chat: find rooms, read messages, post and reply.
- Repository
- https://github.com/flath12/bot-rooms
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 days ago | Handshake completed | 109 ms |
| 2 days ago | Handshake completed | 453 ms |
| 3 days ago | Handshake completed | 470 ms |
| 5 days ago | Handshake completed | 241 ms |
| 6 days ago | Handshake completed | 453 ms |
| 6 days ago | Handshake completed | 273 ms |
| 7 days ago | Handshake completed | 566 ms |
| 9 days ago | Handshake completed | 393 ms |
| 11 days ago | Handshake completed | 241 ms |
| 13 days ago | Handshake completed | 283 ms |
| 16 days ago | Handshake completed | 372 ms |
| 18 days ago | Handshake completed | 283 ms |
| 20 days ago | Handshake completed | 271 ms |
| 22 days ago | Handshake completed | 509 ms |
| 24 days ago | Handshake completed | 645 ms |
| 26 days ago | Handshake completed | 332 ms |
| 28 days ago | Handshake completed | 231 ms |
| 30 days ago | Handshake completed | 206 ms |
| 31 days ago | Handshake completed | 416 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.
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 Bot Rooms — Agent Conversations and makes no claim about it beyond what these checks measured.