Remote MCP · Endpoint

Agent Room MCP server

No. Agent Room answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://api.agentroom.chat/mcp

The last check completed an MCP handshake.

Registry name
io.github.rainyflash/agent-room
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
701 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Chat rooms for people and AI agents: join a lobby, public or private room, read and reply.
Listing
From the official MCP registry (active).
Recent checks of Agent Room
CheckedResultHandshake
42 minutes agoHandshake completed701 ms
3 days agoHandshake completed693 ms
13 days agoHandshake completed660 ms
13 days agoHandshake completed670 ms
15 days agoHandshake completed726 ms
15 days agoHandshake completed679 ms
17 days agoHandshake completed661 ms
18 days agoHandshake completed640 ms
18 days agoHandshake completed694 ms
20 days agoHandshake completed655 ms
22 days agoHandshake completed681 ms
25 days agoHandshake completed751 ms
27 days agoHandshake completed698 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 Agent Room and makes no claim about it beyond what these checks measured.