mcpbeat Sign in

Sandbox Timer MCP Server

by botrecipe Your server? Claim it
not responding

Sandbox Timer is listed as active in the registry but did not answer our last check. It exposes 5 tools.

Flags idle agent sandboxes (E2B, Vercel, Daytona, Modal), shows idle cost, returns kill calls.

Uptime history 23 days of history · worst day 41%
23 days agonow
37.4%
Uptime 24h
34 of 91 checks
5
Tools
read from the server
346 ms
Response time
average over 24h
open, no key
Access
streamable-http

Sandbox Timer does not always answer

Over the last week it answered 54.1% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add timer --transport http https://timer.cloudforbots.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://timer.cloudforbots.com/mcp
~/.codex/config.toml
[mcp_servers.timer]
url = "https://timer.cloudforbots.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "timer": {
      "url": "https://timer.cloudforbots.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "timer": {
      "type": "http",
      "url": "https://timer.cloudforbots.com/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

idle
idle_report
Which sandboxes were flagged idle and what idle time cost, per provider, from what track_sessions has seen. Without an API key pass fleet. With a key: every fleet on it. Free shows 7 days, Pro 30.
set_idle_rules
Pro: save the rules track_sessions applies to a fleet: idle_minutes threshold, max_lifetime_minutes, default rates_per_hour by provider, and alert_webhook. Free returns a preview of the rules and saves nothing (pass the same values on each track_sessions call instead).
track
track_sessions
Send your agent's running sandbox sessions (up to 200; call it on a heartbeat, e.g. every 5 minutes) and get back which are idle past your threshold or over their max lifetime, the dollars idle time has cost at the hourly rates you pass, and what to do. Pro acts: returns a ready-to-run kill call per idle sandbox for its provider (E2B kill, Vercel Sandbox stop, Daytona stop, Modal terminate) and POSTs one alert per sandbox to your webhook. Free watch-only returns would_kill and sends nothing. We never hold provider keys and never kill anything ourselves: your agent runs the call with its own key.
usage
usage_and_upgrade
Show today's usage for your key or IP and the $9/month upgrade link. Free tier: 500 calls/day. Not metered.
weekly
weekly_report
Plain-English summary of the last 7 days: sandboxes watched, how many sat idle, dollars idle time cost at your rates, kill calls returned (Pro) or that would have been (free). Read-only; sends nothing. Needs a free API key.

Endpoints

URLTransportStateLatencyChecked
https://timer.cloudforbots.com/mcp streamable-http answering 21 ms 11 min ago

Alternatives to Sandbox Timer

same job, measured the same way
KillerSkills
by cyligence-karim

Security verdicts for agent skills and MCP servers, from sandbox runs, before you install them.

3 070 installs/wk local only
Ephemeral
by ephemer

Run AI agent tasks in isolated sandboxes with a cost cap, saved workflows and scoped connections.

19 tools answering
RepoGates
by repogates

Trust verdicts on repos, models, VS Code and Docker Desktop extensions and agent skills.

answering
Argon
by argon-lab

Versioned MongoDB sandboxes for AI agents: branch, time-travel, merge, and undo over MCP.

441 installs/wk local only
Plzebo
by wkoverfield

Cost-parity bench for agent loops: $/success and time across model mixes, with verifiable receipts.

56 installs/wk local only
zoomfort
by zoomfort

Receive-only inbox for AI agent sign-ups: one call returns the verification code. Never sends.

answering
Agent Data Tools: Everyday data
by nutshell2000

25 tools: weather, time zones, sun and moon, earthquakes, countries. 25 free calls.

25 tools answering
Agentboard Skills
by jai-rathore

Don't redo web tasks: find a verified workflow, replay it (often 0 model calls). Failures shown.

12 tools answering

Sandbox Timer — questions

Answers built from our own checks of this server.

What can Sandbox Timer do?
It exposes 5 tools, read directly from the server on our last check. Among them: idle_report, set_idle_rules, track_sessions, usage_and_upgrade, weekly_report. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Sandbox Timer working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 34 of 91 checks got a reply (37.4%), average response time 346 ms. The bar chart above shows every period we have measured.
The registry lists Sandbox Timer as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Sandbox Timer?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Sandbox Timer need an API key?
No. Sandbox Timer completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Sandbox Timer?
It answers our handshake in 346 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.