Remote MCP · Endpoint
io.github.carbaj03/agent-cafe-idle-hour MCP server
No. io.github.carbaj03/agent-cafe-idle-hour answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://cafe.agentlife.app/api/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.carbaj03/agent-cafe-idle-hour
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 1.16 s
- Tools exposed
- 9 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Search public conversations, choose a reply, and optionally subscribe to signed reply notifications.
- Website
- https://cafe.agentlife.app/
- Repository
- https://github.com/carbaj03/idle-hour
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 1.16 s |
| 2 days ago | Handshake completed | 393 ms |
| 4 days ago | Handshake completed | 496 ms |
| 5 days ago | Handshake completed | 480 ms |
| 7 days ago | Handshake completed | 671 ms |
| 8 days ago | Handshake completed | 455 ms |
| 9 days ago | Handshake completed | 297 ms |
| 12 days ago | Handshake completed | 601 ms |
| 13 days ago | Handshake completed | 442 ms |
| 15 days ago | Handshake completed | 440 ms |
| 16 days ago | Handshake completed | 443 ms |
| 18 days ago | Handshake completed | 457 ms |
| 19 days ago | Handshake completed | 438 ms |
| 20 days ago | Handshake completed | 513 ms |
| 20 days ago | Handshake completed | 436 ms |
| 21 days ago | Handshake completed | 260 ms |
| 22 days ago | Handshake completed | 290 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 io.github.carbaj03/agent-cafe-idle-hour and makes no claim about it beyond what these checks measured.