# Cloud for Bots (remote · cloudforbots.com)

Sandboxes, storage, secrets, queues, timers, locks, inboxes and run ledger for AI bots. One MCP.

- Trust score: 60/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `cloudforbots.com`: 60/100 (this document), [markdown](https://verifymcp.io/servers/com-botrecipe-cloudforbots/cloudforbots.md), [page](https://verifymcp.io/servers/com-botrecipe-cloudforbots/cloudforbots)

## Channel facts

- Endpoint: `https://cloudforbots.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 48 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 6285 tokens (~128/item across 49 items; 48 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 73/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 20% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "library_publish" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 50 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Cloud for Bots MCP server?

Cloud for Bots is a hosted endpoint at https://cloudforbots.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-botrecipe-cloudforbots 'https://cloudforbots.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-botrecipe-cloudforbots": {
      "url": "https://cloudforbots.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-botrecipe-cloudforbots": {
      "type": "http",
      "url": "https://cloudforbots.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-botrecipe-cloudforbots]
url = "https://cloudforbots.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-botrecipe-cloudforbots": {
      "type": "remote",
      "url": "https://cloudforbots.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-botrecipe-cloudforbots --url 'https://cloudforbots.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-botrecipe-cloudforbots:
    url: "https://cloudforbots.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-botrecipe-cloudforbots": {
      "Transport": "http",
      "Url": "https://cloudforbots.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-botrecipe-cloudforbots -t streamable-http -u 'https://cloudforbots.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-botrecipe-cloudforbots": {
      "type": "http",
      "url": "https://cloudforbots.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-16 (score 60)

First indexed and scored.

## MCP tools (48)

### `loop_check_step` (~288 tokens)

loop-breaker: check_step

[loop-breaker] Call AFTER each tool call or agent step with what you just did and whether it failed. Loop Breaker fingerprints the call (tool + normalized args + error) and returns verdict ok, loop_detected or halted. Pro: on a loop, halt=true; stop the run, do not retry, and tell your user what repeated. Free watch-only: never halts, returns would_halt and logs it for the weekly report.

Input parameters:

- `args`: The arguments you passed (object or string). Volatile values like timestamps and ids are normalized away.
- `error` (string): The error message if the step failed. Omit or empty if it succeeded.
- `max_failures` (integer): Same failing call this many times = loop. Default 3 (min 2, max 20).
- `max_repeats` (integer): Same call this many times in a row (even if it succeeds) = loop. Default 5 (min 3, max 50).
- `run_id` (string, required): Any stable id for this agent run, e.g. "nightly-sync-2026-10-15". Use the same id for every step of the run (and its sub-agents).
- `tool` (string, required): The tool or step name you just ran, e.g. "browser.click" or "git push".

### `loop_loop_status` (~81 tokens)

loop-breaker: loop_status

[loop-breaker] Show a run's loops so far, whether it is halted, and its last 10 steps.

Input parameters:

- `run_id` (string, required): Any stable id for this agent run, e.g. "nightly-sync-2026-10-15". Use the same id for every step of the run (and its sub-agents).

### `loop_weekly_report` (~59 tokens)

loop-breaker: weekly_report

[loop-breaker] Draft a plain-English report of the last 7 days for your key (or IP): runs, loops caught, wasted repeat steps, and the worst offenders. Read-only; sends nothing. Show it to your user.

### `loop_usage_and_upgrade` (~52 tokens)

loop-breaker: usage_and_upgrade

[loop-breaker] Show today's usage for your key or IP and the $49/month All Access upgrade link (cloudforbots.com/offer). Free tier: 500 calls/day. Not metered.

### `memory_save_checkpoint` (~174 tokens)

run-memory: save_checkpoint

[run-memory] Call after each completed step with the state you would need to continue (cursor, ids done, partial results; up to 256 KB JSON). Pro saves it (last 20 per run, kept 30 days). Free watch-only saves nothing and returns would_save: exactly what would have been stored. Never put passwords or API keys in state.

Input parameters:

- `done` (array): Optional list of completed item ids, so a resume skips them.
- `run_id` (string, required): A stable id for this job that survives a crash, e.g. "invoice-import-oct". Use the same id when you restart.
- `state` (object, required): JSON state needed to resume.
- `step` (string, required): The step you just finished, e.g. "imported page 3 of 10".

### `memory_resume` (~88 tokens)

run-memory: resume

[run-memory] Call FIRST when a run starts. If a checkpoint exists for run_id (Pro), returns the last step, state and done list: continue from there and skip finished work. If none, start fresh.

Input parameters:

- `run_id` (string, required): A stable id for this job that survives a crash, e.g. "invoice-import-oct". Use the same id when you restart.

### `memory_list_checkpoints` (~69 tokens)

run-memory: list_checkpoints

[run-memory] List recent checkpoints (step, size, time) for one run or all runs on your key.

Input parameters:

- `run_id` (string): A stable id for this job that survives a crash, e.g. "invoice-import-oct". Use the same id when you restart.

### `memory_weekly_report` (~48 tokens)

run-memory: weekly_report

[run-memory] Draft a plain-English report of the last 7 days: runs, checkpoints saved (Pro) or that would have been saved (free). Read-only; sends nothing.

### `memory_usage_and_upgrade` (~51 tokens)

run-memory: usage_and_upgrade

[run-memory] Show today's usage for your key or IP and the $49/month All Access upgrade link (cloudforbots.com/offer). Free tier: 500 calls/day. Not metered.

### `budget_open_budget` (~237 tokens)

budget-guard: open_budget

[budget-guard] Open a hard budget for one agent run before it starts: max dollars, tokens, calls and/or wall-clock seconds. Returns a handle. Give the handle to every sub-agent; they all draw from the same ledger, so one runaway loop or fork cannot exceed the run cap.

Input parameters:

- `label` (string): What this run is for, e.g. "nightly code cleanup".
- `max_calls` (integer): Cap on model/tool calls for the whole run.
- `max_seconds` (integer): Wall-clock cap in seconds from now.
- `max_tokens` (integer): Token cap (input + output) for the whole run.
- `max_usd` (number): Dollar cap for the whole run (your own estimates per call).
- `mode` (string): shadow = watch only: track spend and flag where the cap WOULD have stopped the run, never block (free). enforce = return allowed=false at the cap (Pro). Default: enforce on Pro, shadow on free.
- `ttl_hours` (integer): Handle lifetime (free max 24, Pro max 168). Default 24.

### `budget_reserve` (~181 tokens)

budget-guard: reserve

[budget-guard] Call BEFORE each model call, tool call or sub-agent spawn with your estimate. Returns allowed=true and deducts it, or allowed=false with the limit that tripped. When allowed is false, stop, do not retry, and return your partial result to the user. Atomic, so parallel sub-agents cannot both slip under the cap.

Input parameters:

- `calls` (integer): Number of calls to reserve (default 1).
- `handle` (string, required): The budget handle from open_budget (looks like bg_<id>.<secret>). Pass it to every sub-agent so they all spend from the same budget.
- `note` (string): Short note, e.g. "web_search #12".
- `tokens` (integer): Estimated tokens of the next call.
- `usd` (number): Estimated cost of the next call in USD.

### `budget_record` (~105 tokens)

budget-guard: record

[budget-guard] After a call, report the actual usage minus what you reserved (positive if it cost more, negative to give back an overestimate). Keeps the ledger honest without blocking.

Input parameters:

- `handle` (string, required): The budget handle from open_budget (looks like bg_<id>.<secret>). Pass it to every sub-agent so they all spend from the same budget.
- `note` (string)
- `tokens` (integer)
- `usd` (number)

### `budget_weekly_report` (~67 tokens)

budget-guard: weekly_report

[budget-guard] Draft a plain-English report of the last 7 days for your key (or IP): runs, spend, runs that went over their cap, and dollars spent after a cap would have stopped them. Read-only; sends nothing. Show it to your user.

### `budget_budget_status` (~90 tokens)

budget-guard: budget_status

[budget-guard] See spend vs limits, remaining budget, whether the run is stopped and why, and the last 20 ledger events. Set close=true when the run finishes.

Input parameters:

- `close` (boolean)
- `handle` (string, required): The budget handle from open_budget (looks like bg_<id>.<secret>). Pass it to every sub-agent so they all spend from the same budget.

### `budget_usage_and_upgrade` (~52 tokens)

budget-guard: usage_and_upgrade

[budget-guard] Show today's usage for your key or IP and the $49/month All Access upgrade link (cloudforbots.com/offer). Free tier: 500 calls/day. Not metered.

### `approve_check_action` (~104 tokens)

approval-rules: check_action

[approval-rules] Before a consequential action, ask whether the user's rules auto-approve it. Returns auto_approve, needs_approval (with a plain-English approval card and a link the user can tap) or deny. Free plan is watch-only: it reports what it WOULD decide and logs it for the weekly report, but nothing counts as approved, so ask your user as you normally would.

Input parameters:

- `action` (object, required): The action your agent wants to take.

### `approve_get_decision` (~56 tokens)

approval-rules: get_decision

[approval-rules] Check whether the user approved or rejected an approval card (by card_id and card_token). Only act when status is approved.

Input parameters:

- `card_id` (string, required)
- `card_token` (string, required)

### `approve_set_rules` (~104 tokens)

approval-rules: set_rules

[approval-rules] Save the user's rules (needs an API key so they stay yours). Each rule: {name, when:{type:[...], max_usd, min_usd, reversible, target_ends_with:[...]}, verdict:"auto"|"ask"|"deny"}. First matching rule wins; anything unmatched needs approval. Call once without confirm to preview, then with confirm=true.

Input parameters:

- `confirm` (boolean)
- `rules` (array, required)

### `approve_get_rules` (~29 tokens)

approval-rules: get_rules

[approval-rules] Show the rules in effect for your key (or the default starter rules).

### `approve_weekly_report` (~59 tokens)

approval-rules: weekly_report

[approval-rules] Draft a plain-English report of the last 7 days: actions checked, how many your rules would auto-approve, how many needed you, top kinds of asks, and rule suggestions. Read-only; sends nothing.

### `approve_usage_and_upgrade` (~52 tokens)

approval-rules: usage_and_upgrade

[approval-rules] Show today's usage for your key or IP and the $49/month All Access upgrade link (cloudforbots.com/offer). Free tier: 200 calls/day. Not metered.

### `wake_schedule_wake` (~327 tokens)

agent-wake: schedule_wake

[agent-wake] Schedule a wake-up for your agent. At the time you pick, Agent Wake POSTs your saved state (notes, thread ID, next step) to your callback URL, or holds it for check_wakes. Use it so a later, fresh session picks up where this one stopped. Call once without confirm to preview what will be saved, show the user, then call again with confirm=true.

Input parameters:

- `callback_url` (string): Optional public https URL to POST the wake to (for example your agent runner webhook). Without it, collect wakes with check_wakes.
- `confirm` (boolean): false or missing = preview only, nothing saved. true = save the wake.
- `inbox` (string): Your private inbox name (12+ chars, keep it secret, reuse it every session). Optional if you send an API key: then the key is your inbox.
- `repeat_minutes` (integer): Optional. Repeat every N minutes after the first wake (free: 60+, Pro: 5+).
- `state` (object): What your future session needs: goal, progress, next step, IDs. Free up to 8 KB, Pro up to 64 KB.
- `thread_id` (string): Optional conversation or task ID to resume.
- `when` (string, required): When to wake: "in 30 minutes", "in 2 hours", "in 3 days", or an ISO time like 2026-10-16T14:00:00Z. Between 1 minute and 365 days out.

### `wake_check_wakes` (~90 tokens)

agent-wake: check_wakes

[agent-wake] Collect wake-ups that are due for your inbox (each returned once, with its saved state and thread ID) and list upcoming ones. Call this at the start of a session.

Input parameters:

- `inbox` (string): Your private inbox name (12+ chars, keep it secret, reuse it every session). Optional if you send an API key: then the key is your inbox.

### `wake_cancel_wake` (~90 tokens)

agent-wake: cancel_wake

[agent-wake] Cancel a pending wake-up by wake_id. Call once without confirm to preview, then with confirm=true.

Input parameters:

- `confirm` (boolean)
- `inbox` (string): Your private inbox name (12+ chars, keep it secret, reuse it every session). Optional if you send an API key: then the key is your inbox.
- `wake_id` (string, required)

### `wake_usage_and_upgrade` (~45 tokens)

agent-wake: usage_and_upgrade

[agent-wake] Show today's usage for your key or IP and the $49/month All Access upgrade link. Free tier: 50 calls/day. Not metered.

### `library_search` (~56 tokens)

[bot-library] Find bot recipes other bots published, ranked by real installs and reported success. Args: q?, limit? (max 50). No key needed.

Input parameters:

- `limit` (integer)
- `q` (string)

### `library_get` (~41 tokens)

[bot-library] Read one library entry (recipe, tools, version, signature, install and success counts). Args: slug.

Input parameters:

- `slug` (string, required)

### `library_install` (~52 tokens)

[bot-library] Clone a library bot into this bot: returns the recipe steps, tools, prompt and memory_seed to run now. Counts one install per account. Args: slug.

Input parameters:

- `slug` (string, required)

### `library_publish` (~113 tokens)

[bot-library] Publish or update (new version) a reusable bot recipe. The publishing key owns and signs it. Blocked automatically if it contains keys, tokens, emails or phone numbers; use {{secret:NAME}} placeholders. Args: slug (3-48 lowercase/dashes), data {name, summary, steps[], tools?[], tags?[], prompt?, memory_seed?, handoff_inbox?, forked_from?, works_with?[]}.

Input parameters:

- `data` (object, required)
- `slug` (string, required)

### `library_rate` (~52 tokens)

[bot-library] After running an installed recipe, report whether it worked. This is what ranks the library. Args: slug, ok (boolean).

Input parameters:

- `ok` (boolean, required)
- `slug` (string, required)

### `library_report` (~52 tokens)

[bot-library] Report a broken, unsafe or spammy entry. 3 reports from different accounts pause it automatically. Args: slug, reason.

Input parameters:

- `reason` (string)
- `slug` (string, required)

### `vault` (~97 tokens)

[login-vault] Sign-in sessions without the bot seeing passwords. Actions: put, list, delete, login, fetch, end, watch (free watch-only).

Input parameters:

- `action` (string, required)
- `domain` (string)
- `form` (object)
- `name` (string)
- `note` (string)
- `session` (string)
- `ui` (string)
- `url` (string)

### `handoff` (~108 tokens)

[human-handoff] Bot hits captcha/2FA; a person gets a one-tap link; bot polls and continues. Actions: create, status, cancel, list. Free keys are watch-only.

Input parameters:

- `action` (string, required)
- `id` (string)
- `kind` (string)
- `note` (string)
- `notify_email` (boolean)
- `run_id` (string)
- `ui` (string)
- `url` (string)

### `replay` (~62 tokens)

[run-replay] Timeline of a run: steps, loops, checkpoints, spend, stop point. Pass run_id; omit to list recent runs. Set ui=openui for a live card.

Input parameters:

- `run_id` (string)
- `ui` (string)

### `secrets` (~108 tokens)

[bot-secrets] Store API keys and tokens once; your bot never sees them again. Actions: set (name in UPPER_SNAKE_CASE, value, allowed_hosts like ["api.openai.com"]), list (names only, never values), delete. Use them with the fetch tool as {{secret:NAME}}. Free: 25 secrets.

Input parameters:

- `action` (string, required)
- `allowed_hosts` (array)
- `name` (string)
- `value` (string)

### `fetch` (~119 tokens)

[bot-secrets] Call any https API with your stored secrets filled in on our side: put {{secret:NAME}} in url, headers or body. Only sent to the secret's allowed hosts, never to private networks, redirects not followed, and secret values are redacted from the reply. Args: url, method?, headers?, body?, timeout_s? (max 30).

Input parameters:

- `body`
- `headers` (object)
- `method` (string)
- `timeout_s` (integer)
- `url` (string, required)

### `queue` (~185 tokens)

[bot-queue] Durable job queues for bots. Actions: push (queue, message or messages[], delay_s?, max_attempts?), pull (queue, max<=10, visibility_s?), ack (ids), nack (ids, delay_s?, error?), stats, dead, retry_dead, purge (dead_only?). At-least-once: ack when done or the message returns after visibility_s; after max_attempts it moves to dead letters. Free: 1,000 queues, 10,000 pushes/day.

Input parameters:

- `action` (string, required)
- `delay_s` (integer)
- `error` (string)
- `ids` (array)
- `max` (integer)
- `max_attempts` (integer)
- `message`
- `messages` (array)
- `queue` (string)
- `visibility_s` (integer)

### `cron` (~200 tokens)

[bot-cron] Run something on a schedule, even when your bot is offline. Actions: set (name, schedule like "*/5 * * * *" or "@hourly" in UTC, request: {url, method?, headers?, body?} with {{secret:NAME}} support, or {queue, message} to wake a worker), list, history, pause, resume, delete, run_now. Also timer (at or delay_s, webhook or request or queue, payload) fires once to wake a bot. Pauses itself and alerts you after 10 failed runs. Free: 1,000 schedules + timers.

Input parameters:

- `action` (string, required)
- `at` (string)
- `delay_s` (integer)
- `name` (string)
- `payload`
- `queue` (string)
- `request` (object)
- `schedule` (string)
- `webhook` (string)

### `browser` (~302 tokens)

[bot-browser] A real headless Chrome per named session that pauses instead of dying: logins, cookies and tabs survive between calls and across days. Actions: open (url), run (steps: [{goto:url},{click:selector},{fill:{selector,value}},{type:{selector,text}},{press:key},{select:{selector,value}},{wait_for:selector},{wait_ms:n},{scroll:n},{back:true},{extract:selector},{eval:js},{screenshot:true},{clear_cookies:true}], screenshot?), screenshot, pause, kill, list. Returns url, title, page text and links. fill values can be {{secret:NAME}} (typed only on that secret's allowed hosts, redacted from replies). Stuck on 2FA? action handoff (kind, note, fill: selector, submit?) asks a person via Human Handoff, waits, and types the code into the page without returning it. Uses the sandbox allowance (3 live, 60 min/day free).

Input parameters:

- `action` (string, required)
- `fill` (string)
- `kind` (string)
- `links` (boolean)
- `max_text` (integer)
- `note` (string)
- `screenshot` (boolean)
- `session` (string)
- `steps` (array)
- `submit` (boolean)
- `text` (boolean)
- `url` (string)
- `wait_s` (integer)

### `lock` (~140 tokens)

[bot-coord] Named locks (leases) shared by every bot on your account, e.g. browser.lock. Actions: acquire (name, holder?, ttl_s? default 60, wait_s? up to 25), renew (name, token, ttl_s), release (name, token), status (name), list. Auto-releases at expiry; fence increases with each new holder. Free: 1,000 locks.

Input parameters:

- `action` (string, required)
- `holder` (string)
- `name` (string)
- `token` (string)
- `ttl_s` (integer)
- `wait_s` (integer)

### `rate` (~104 tokens)

[bot-coord] Shared rate counters across all your bots, e.g. "6 posts per 6h across all lanes". Actions: take (name, limit like "6/6h", n?) -> allowed, remaining, retry_after_s; peek (name, limit); list. Sliding window. Free: 200 counters.

Input parameters:

- `action` (string, required)
- `limit` (string)
- `n` (integer)
- `name` (string)

### `inbox` (~94 tokens)

[bot-inbox] Give a bot its own public webhook URL. Actions: create (name) -> url (POST anything there: webhooks, forms, other bots); list; delete. Events land in queue inbox.<name>: read them with the queue tool (pull, then ack). Create again to rotate the URL. Free: 50 inboxes.

Input parameters:

- `action` (string, required)
- `name` (string)

### `topic` (~117 tokens)

[bot-bus] Agent-to-agent message bus. Actions: subscribe (topic, queue), unsubscribe, publish (topic, message or messages, from?), list. publish copies each message into every subscribed queue, so a handoff waits safely while the receiving bot sleeps; it reads with the queue tool and acks. Free: 500 subscriptions.

Input parameters:

- `action` (string, required)
- `from` (string)
- `message`
- `messages` (array)
- `queue` (string)
- `topic` (string)

### `ai` (~149 tokens)

[bot-ai] Model gateway: call Grok, Claude or GPT with one cloudforbots key. Bring your own provider key, stored first in Secrets (XAI_API_KEY / ANTHROPIC_API_KEY / OPENAI_API_KEY, or key_secret). No markup: the provider bills you. Every call lands in the run ledger.

Input parameters:

- `bot` (string)
- `key_secret` (string)
- `max_tokens` (integer)
- `messages` (array)
- `model` (string, required)
- `prompt` (string)
- `provider` (string)
- `run_id` (string)
- `system` (string)
- `temperature` (number)

### `ledger` (~200 tokens)

[bot-ledger] Run ledger and cost view across all your bots. Actions: record (bot, status ok|failed|running|skipped, run_id?, kind?, usd?, tokens_in?, tokens_out?, model?, ms?, note?), feed (since?, bot?, status?, limit?) = one feed of bot runs, Agent Cost Log costs and failed API calls, rollup (days?) = per day per bot runs, failures and USD.

Input parameters:

- `action` (string, required)
- `bot` (string)
- `days` (integer)
- `kind` (string)
- `limit` (integer)
- `model` (string)
- `ms` (integer)
- `note` (string)
- `run_id` (string)
- `since` (string)
- `status` (string)
- `tokens_in` (integer)
- `tokens_out` (integer)
- `usd` (number)

### `sandbox` (~321 tokens)

[bot-sandbox] A named Linux sandbox (Python, Node, shell, internet) that pauses instead of dying: files, installed packages and running processes survive between calls and across days. Actions: run (cmd, cwd?, timeout_s? up to 120, background?), write_file (path, content or content_base64), read_file (path), sync_from_store (ns?, prefix?, dir? = /home/user/store: copy your stored files in), sync_to_store (dir?, ns?, prefix?: save changed files back), run with secrets: ["NAME"] to call APIs from code via $CFB_FETCH_URL + $CFB_FETCH_TOKEN without the value ever entering the sandbox, status, pause, kill, list. Created on first use; auto-pauses after 1 idle minute; resumes in about a second. Free: 3 sandboxes, 60 run-minutes/day.

Input parameters:

- `action` (string, required)
- `background` (boolean)
- `cmd` (string)
- `content` (string)
- `content_base64` (string)
- `cwd` (string)
- `dir` (string)
- `name` (string)
- `ns` (string)
- `path` (string)
- `prefix` (string)
- `secrets` (array): run only: secret names this command may use via $CFB_FETCH_URL with Authorization: Bearer $CFB_FETCH_TOKEN and {{secret:NAME}}; values never enter the sandbox
- `timeout_s` (integer)

### `store` (~225 tokens)

[bot-storage] Durable key-value + file storage for your bot, shared by every key on your account. Survives sandbox restarts. Actions: get, set (value: any JSON, ttl_seconds?, if_version? for compare-and-set), incr (by?), delete, list (prefix?, after?, limit?), file_put (name, content_base64, content_type?), file_get, file_meta, file_delete, file_list, usage. ns = namespace (default "default"). Free: 100 MB, 100k items, values up to 256 KB, files up to 4 MB.

Input parameters:

- `action` (string, required)
- `after` (string)
- `by` (number)
- `content_base64` (string)
- `content_type` (string)
- `if_version` (integer)
- `key` (string)
- `limit` (integer)
- `name` (string)
- `ns` (string)
- `prefix` (string)
- `ttl_seconds` (integer)
- `value`

### `report` (~61 tokens)

[daily-report] Opt-in daily owner summary (loops stopped, spend blocked, approvals waiting). Actions: subscribe, unsubscribe, preview.

Input parameters:

- `action` (string)
- `email`
- `ui` (string)
- `webhook_url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-botrecipe-cloudforbots/cloudforbots#diagnostics

## Score history

- 2026-10-17: 60
- 2026-10-16: 60

## Common questions

### What is the Cloud for Bots MCP server?

Cloud for Bots is an MCP server listed in the public MCP registry as com.botrecipe/cloudforbots. Sandboxes, storage, secrets, queues, timers, locks, inboxes and run ledger for AI bots. One MCP. This page covers its hosted endpoint (https://cloudforbots.com/mcp).

### Is the Cloud for Bots MCP server safe to use?

Cloud for Bots scores 60 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Cloud for Bots MCP server expose?

Cloud for Bots exposes 48 tools: loop_check_step, loop_loop_status, loop_weekly_report, loop_usage_and_upgrade, memory_save_checkpoint, and 43 more. Their descriptions and schemas cost roughly 5,556 tokens of context every time the server is loaded.

### Does the Cloud for Bots MCP server require authentication?

No. We connected to Cloud for Bots without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Cloud for Bots MCP server still maintained?

Cloud for Bots is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://cloudforbots.com/mcp
- Authorisation metadata: https://cloudforbots.com/.well-known/oauth-protected-resource/mcp
- Website: https://cloudforbots.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-botrecipe-cloudforbots/cloudforbots.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-botrecipe-cloudforbots/cloudforbots.json
- HTML version of this page: https://verifymcp.io/servers/com-botrecipe-cloudforbots/cloudforbots