_ registry / mcp streamable-http · checked 2h ago

compute-connector

https://compute.cloudforbots.com

Registry code: 6da755d367dc84ef

api record

More compute for your bot. When the machine your agent runs on is low on memory, Compute Connector warns it and sends the heavy job (builds, installs, test suites, headless browsers) to a cloud sandbox on your own provider account: Vercel Sandbox by default, or E2B, Daytona, Modal and Workers Sandbox. You bring the keys and pay the provider directly; we charge a flat connector fee and never resell compute. Free 500 calls/day, then $9/month. No model inside: bring your own model. Works with Claude, Codex, ChatGPT, Grok Bot.

endpoint
https://compute.cloudforbots.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is compute-connector live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is compute-connector free to use?
Yes — the hub reached it with no key and no payment.
What tools does compute-connector have?
8 tools: run_job, delete_provider_key, usage_and_upgrade, save_provider_key, provider_setup, weekly_report, list_providers, check_memory.
Is compute-connector safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
302ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
2 open 6 never probed 2 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_providers open 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • check_memory open 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "free_mb"
  ],
  "properties": {
    "job": {
      "type": "string",
      "description": "The command or a short description, e.g. \"npm run build\" or \"playwright crawl of 40 pages\"."
    },
    "host": {
      "type": "string",
      "description": "Optional name of the machine, e.g. \"my-laptop\"."
    },
    "job_mb": {
      "type": "number",
      "description": "Optional: your own estimate of the job's peak memory in MB. Without it we use a rough guess by job type."
    },
    "free_mb": {
      "type": "number",
      "description": "Free or available memory right now, in MB (Linux: the \"available\" column of free -m)."
    },
    "floor_mb": {
      "type": "number",
      "description": "Keep at least this much free. Default 2048."
    },
    "total_mb": {
      "type": "number"
    }
  }
}
    arguments 31 lines
  • run_job unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "cmd"
  ],
  "properties": {
    "cmd": {
      "type": "string",
      "description": "Shell command, run with bash -lc, e.g. \"git clone https://github.com/you/app && cd app && npm ci && npm test\"."
    },
    "env": {
      "type": "object",
      "description": "Optional non-secret environment variables for the command (strings)."
    },
    "files": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "path"
        ],
        "properties": {
          "path": {
            "type": "string"
          },
          "content": {
            "type": "string"
          },
          "encoding": {
            "type": "string"
          }
        }
      },
      "description": "Optional input files written before cmd runs: [{path, content, encoding?: \"base64\"}]. 50 files, 500 KB total."
    },
    "free_mb": {
      "type": "number",
      "description": "Optional: memory free on your machine now, for the weekly report."
    },
    "runtime": {
      "type": "string",
      "description": "Vercel only: node24 (default), node22, node26 or python3.13."
    },
    "provider": {
      "type": "string",
      "description": "Name of a saved provider key (default: your default key, else vercel)."
    },
    "template": {
      "type": "string",
      "description": "E2B only: template id, default base."
    },
    "timeout_s": {
      "type": "integer",
      "description": "1-240 seconds, default 120."
    }
  }
}
    arguments 57 lines
  • delete_provider_key unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • usage_and_upgrade unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • save_provider_key unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "provider",
    "token"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Label for this key, default the provider name. Use it in run_job provider."
    },
    "token": {
      "type": "string",
      "description": "The provider API key or token (or your bridge token)."
    },
    "api_url": {
      "type": "string",
      "description": "Daytona: API base, default https://app.daytona.io/api."
    },
    "team_id": {
      "type": "string",
      "description": "Vercel: team id (team_...)."
    },
    "provider": {
      "type": "string",
      "description": "vercel, e2b, daytona, modal or workers."
    },
    "bridge_url": {
      "type": "string",
      "description": "Modal / Workers Sandbox: https URL of the bridge you deployed."
    },
    "project_id": {
      "type": "string",
      "description": "Vercel: project id or name the sandboxes bill to."
    },
    "skip_check": {
      "type": "boolean",
      "description": "Save without the read-only check (not recommended)."
    },
    "make_default": {
      "type": "boolean"
    }
  }
}
    arguments 44 lines
  • provider_setup unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "provider"
  ],
  "properties": {
    "provider": {
      "type": "string",
      "description": "vercel, e2b, daytona, modal or workers."
    }
  }
}
    arguments 12 lines
  • weekly_report unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 6da755d367dc84ef.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6da755d367dc84ef/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/6da755d367dc84ef/badge.svg)](https://brick.blue/agent/6da755d367dc84ef?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on cloudforbots.com 10 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

2 more sit on this domain. All of them.