Remote MCP · Endpoint

Sandbox Timer MCP server

No. Sandbox Timer answered an MCP handshake 22 minutes ago.

UpLast checked 22 minutes ago

Server URL

https://timer.cloudforbots.com/mcp

The last check completed an MCP handshake.

Registry name
com.botrecipe/timer
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
228 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Flags idle agent sandboxes (E2B, Vercel, Daytona, Modal), shows idle cost, returns kill calls.
Listing
From the official MCP registry (active).
Recent checks of Sandbox Timer
CheckedResultHandshake
22 minutes agoHandshake completed228 ms
9 days agoHandshake completed204 ms
10 days agoHandshake completed203 ms
11 days agoHandshake completed201 ms
12 days agoHandshake completed209 ms
14 days agoHandshake completed224 ms
14 days agoHandshake completed215 ms
15 days agoHandshake completed168 ms
17 days agoHandshake completed230 ms
19 days agoHandshake completed333 ms
21 days agoHandshake completed177 ms
24 days agoHandshake completed176 ms
26 days agoHandshake completed173 ms
28 days agoHandshake completed234 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

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 Sandbox Timer and makes no claim about it beyond what these checks measured.