Compute Connector
REMOTE · COMPUTE.CLOUDFORBOTS.COM
Low on memory? Your bot sends heavy jobs to cloud sandboxes on your own provider keys. Flat fee.
Available components
Last scanned (2 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1166 tokens (~145/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_provider_key" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://compute.cloudforbots.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=compute.cloudforbots.com | CN=YR2,O=Let's Encrypt,C=US | 17 Oct 2026 | 15 Jan 2027 | RSA 2048 | SHA256-RSA | 69d5289f5b5fc69c1fad05198bb3661d041 |
| SANs: compute.cloudforbots.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of compute.cloudforbots.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cloudforbots.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://compute.cloudforbots.com/mcp | Verified | 200 | |
| http (plaintext) | http://compute.cloudforbots.com/mcp | HTTPS enforced | 308 | https://compute.cloudforbots.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_memory ~217
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.
| Name | Type | Req | Description |
|---|---|---|---|
| floor_mb | number | – | Keep at least this much free. Default 2048. |
| free_mb | number | yes | Free or available memory right now, in MB (Linux: the "available" column of free -m). |
| host | string | – | Optional name of the machine, e.g. "my-laptop". |
| job | string | – | The command or a short description, e.g. "npm run build" or "playwright crawl of 40 pages". |
| job_mb | number | – | Optional: your own estimate of the job's peak memory in MB. Without it we use a rough guess by job type. |
| total_mb | number | – | – |
No output schema declared.
No examples provided.
delete_provider_key ~38
Pro, owner only: delete a saved provider key by name. Jobs on that key stop working at once.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
list_providers ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
provider_setup ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | vercel, e2b, daytona, modal or workers. |
No output schema declared.
No examples provided.
run_job ~299
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cmd | string | yes | Shell command, run with bash -lc, e.g. "git clone https://github.com/you/app && cd app && npm ci && npm test". |
| env | object | – | Optional non-secret environment variables for the command (strings). |
| files | array | – | Optional input files written before cmd runs: [{path, content, encoding?: "base64"}]. 50 files, 500 KB total. |
| free_mb | number | – | Optional: memory free on your machine now, for the weekly report. |
| provider | string | – | Name of a saved provider key (default: your default key, else vercel). |
| runtime | string | – | Vercel only: node24 (default), node22, node26 or python3.13. |
| template | string | – | E2B only: template id, default base. |
| timeout_s | integer | – | 1-240 seconds, default 120. |
No output schema declared.
No examples provided.
save_provider_key ~267
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_url | string | – | Daytona: API base, default https://app.daytona.io/api. |
| bridge_url | string | – | Modal / Workers Sandbox: https URL of the bridge you deployed. |
| make_default | boolean | – | – |
| name | string | – | Label for this key, default the provider name. Use it in run_job provider. |
| project_id | string | – | Vercel: project id or name the sandboxes bill to. |
| provider | string | yes | vercel, e2b, daytona, modal or workers. |
| skip_check | boolean | – | Save without the read-only check (not recommended). |
| team_id | string | – | Vercel: team id (team_...). |
| token | string | yes | The provider API key or token (or your bridge token). |
No output schema declared.
No examples provided.
usage_and_upgrade ~37
Show today's usage for your key or IP and the $9/month upgrade link. Free tier: 500 calls/day. Not metered.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
weekly_report ~58
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Compute Connector MCP server?
Compute Connector is a hosted endpoint at https://compute.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.
remote · compute.cloudforbots.com
claude mcp add --transport http com-botrecipe-compute 'https://compute.cloudforbots.com/mcp'
What is the Compute Connector MCP server?
Compute Connector is an MCP server listed in the public MCP registry as com.botrecipe/compute. Low on memory? Your bot sends heavy jobs to cloud sandboxes on your own provider keys. Flat fee. This page covers its hosted endpoint (https://compute.cloudforbots.com/mcp).
Is the Compute Connector MCP server safe to use?
Compute Connector scores 63 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 Compute Connector MCP server expose?
Compute Connector exposes 8 tools: check_memory, run_job, save_provider_key, list_providers, delete_provider_key, and 3 more. Their descriptions and schemas cost roughly 1,038 tokens of context every time the server is loaded.
Does the Compute Connector MCP server require authentication?
No. We connected to Compute Connector without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Compute Connector MCP server still maintained?
Compute Connector 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.