Compute Connector MCP server

• check_memoryFree

  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.

• delete_provider_keywrite actionFree

  Pro, owner only: delete a saved provider key by name. Jobs on that key stop working at once.

• list_providersFree

  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.

• provider_setupFree

  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_jobwrite actionFree

  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_keyFree

  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.

• usage_and_upgradeFree

  Show today's usage for your key or IP and the $9/month upgrade link. Free tier: 500 calls/day. Not metered.

• weekly_reportFree

  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.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 558ms20/20
• Tool poisoning8 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 2 write-action tools with no auth3/15
• Maintenanceno repository listed3/15
• Maintainer identityverified namespace with website, no repo4/10

Safety score

60/100

higher than 15% of 48,255 servers

Tools

8

the typical server has 7

Tools that change things

25%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

678 ms

faster than 20% of 30,031 servers

Compute Connector: common questions

Is Compute Connector MCP server safe?

With care: it is graded C, so read the findings first (60/100). Read the Compute Connector safety report

How do I install Compute Connector?

It runs remotely at compute.cloudforbots.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Compute Connector need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Compute Connector maintained?

The latest release is v1.0.0.

Is Compute Connector up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

How does Compute Connector compare with other MCP servers?

safety score 60/100 (higher than 15% of 48,255 servers); tools 8 (the typical server has 7); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.