Compute Connector
by botrecipe.com · remote · no sign-in to list tools · v1.0.0 · published by com.botrecipe
Low on memory? Your bot sends heavy jobs to cloud sandboxes on your own provider keys. Flat fee.
Deletes · 1Changes · 5
8 tools: 1 can delete or cancel things, 5 change things and 2 only read.
Scanned Oct 21, 2026
- Deletes or cancels1Claude Code: deny: see these tools
- Can't be undone0Claude Code: ask
- Changes things5Claude Code: ask: see these tools
- Only reads2Claude Code: allow: see these tools
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http compute https://compute.cloudforbots.com/mcpTools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
8 tools
Deletes or cancels 1Claude Code: deny
delete_provider_keyPro, owner only: delete a saved provider key by name.No findings
Why it is in this group
- The name "delete_provider_key" says "delete": a word for removing or ending something.
Description, as the server wrote it Pro, owner only: delete a saved provider key by name. Jobs on that key stop working at once.
Changes things 5Claude Code: ask
check_memoryBefore a heavy job, send how much memory the machine your agent runs on has free (free -m, os.freemem()) and what you are about to run.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Before a heavy job, send how much memory the machine your agent runs on has free (free -m, os.freemem()) and what you are about to run. Get a memory warning and a verdict: run_local, or offload with the provider to use. Free watch-only logs would_offload for the weekly report; nothing runs.
provider_setupStep-by-step setup for one provider: where to get the key, what to pass to save_provider_key, links to its docs and price page, and for Modal or Workers Sandbox the bridge code to …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Step-by-step setup for one provider: where to get the key, what to pass to save_provider_key, links to its docs and price page, and for Modal or Workers Sandbox the bridge code to deploy on your own account.
run_jobPro: run a shell command in a fresh cloud sandbox on your own provider account (vercel (Vercel Sandbox, default), e2b, daytona, modal, workers (Workers Sandbox)) and get the exit c…No findings
Why it is in this group
- The name "run_job" says "run": a word for a change.
- The input takes a statement or command to run (input.cmd), which can change anything it can reach.
Description, as the server wrote it Pro: run a shell command in a fresh cloud sandbox on your own provider account (vercel (Vercel Sandbox, default), e2b, daytona, modal, workers (Workers Sandbox)) and get the exit code and the last 16 KB of stdout and stderr back. Send small input files with it. The sandbox is created for the job and stopped right after, so nothing idles on your bill. Free watch-only logs would_offload and runs nothing.
save_provider_keyPro, owner only: save one provider key, sealed with AES-256-GCM before it reaches the database.No findings
Why it is in this group
- The name "save_provider_key" says "save": a word for a change.
Description, as the server wrote it Pro, owner only: save one provider key, sealed with AES-256-GCM before it reaches the database. Providers: vercel (Vercel Sandbox, default), e2b, daytona, modal, workers (Workers Sandbox). Vercel needs team_id and project_id; Modal and Workers Sandbox need bridge_url (see provider_setup). The key is checked with a read-only call first and is never returned or logged. Free stores nothing.
weekly_reportPlain-English summary of the last 7 days: memory checks, low-memory warnings, jobs that would have been offloaded (free) or ran (Pro) by provider, minutes and failures.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Plain-English summary of the last 7 days: memory checks, low-memory warnings, jobs that would have been offloaded (free) or ran (Pro) by provider, minutes and failures. Read-only; sends nothing. Needs an API key.
Only reads 2Claude Code: allow
list_providersEvery provider this connects to, how each one runs, and (with your key) the provider keys you saved: name, provider, fingerprint, default, last used.No findings
Why it is in this group
- The name "list_providers" says "list": a word for reading.
Description, as the server wrote it Every provider this connects to, how each one runs, and (with your key) the provider keys you saved: name, provider, fingerprint, default, last used. Never shows a key.
usage_and_upgradeShow today's usage for your key or IP and the $9/month upgrade link.No findings
Why it is in this group
- The description's first verb is "show": a word for reading.
Description, as the server wrote it Show today's usage for your key or IP and the $9/month upgrade link. Free tier: 500 calls/day. Not metered.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http compute https://compute.cloudforbots.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__compute__list_providers",
"mcp__compute__usage_and_upgrade"
],
"ask": [
"mcp__compute__check_memory",
"mcp__compute__run_job",
"mcp__compute__save_provider_key",
"mcp__compute__provider_setup",
"mcp__compute__weekly_report"
],
"deny": [
"mcp__compute__delete_provider_key"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as compute. Review it before you use it.