mcp-registry/com.botrecipe/compute · v1.0.0
As of 2026-10-22 02:03 UTC, the Botrecipe Compute MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Low on memory? Your bot sends heavy jobs to cloud sandboxes on your own provider keys. Flat fee.
Claude Code
claude mcp add --transport http botrecipe-compute-mcp-server https://compute.cloudforbots.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"botrecipe-compute-mcp-server": {
"type": "http",
"url": "https://compute.cloudforbots.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
3 parameter(s) across 3 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.botrecipe%2Fcompute/fixes
{
"name": "check_memory",
"description": "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.",
"inputSchema": {
"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"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "delete_provider_key",
"description": "Pro, owner only: delete a saved provider key by name. Jobs on that key stop working at once.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}{
"name": "list_providers",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.botrecipe/compute"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.botrecipe/compute"}) over MCP.
run_job ~432 tokenssave_provider_key ~368 tokenscheck_memory ~285 tokensprovider_setup ~113 tokensweekly_report ~84 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.botrecipe%2Fcompute?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.botrecipe%2Fcompute?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.botrecipe%2Fcompute.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.botrecipe%2Fcompute.svg :target: https://glimind.com/server/mcp-registry%2Fcom.botrecipe%2Fcompute?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3276aff3c2334063…, first seen 2026-10-17, included at leaf 17623 of 42,854. Version history · verify what your client received.
Compare: most reliable devops servers · most reliable security servers · most reliable knowledge servers · most reliable code servers · most reliable productivity servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 02:03 UTC, the Botrecipe Compute MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Botrecipe Compute MCP server advertises 8 tools, including check_memory, delete_provider_key, list_providers, provider_setup, run_job.
Point your MCP client at this streamable-http endpoint: https://compute.cloudforbots.com/mcp
Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.