mcp-registry/com.botrecipe/cloudforbots · v1.0.0
As of 2026-10-26 16:02 UTC, the Botrecipe Cloudforbots MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 25.5 hours.
Sandboxes, storage, secrets, queues, timers, locks, inboxes and run ledger for AI bots. One MCP.
Point your MCP client at this streamable-http endpoint: https://cloudforbots.com/mcp
48 of 48 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 →
48 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
150 parameter(s) across 28 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 →
8 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 →
7 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. 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. 28 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.botrecipe%2Fcloudforbots/fixes
{
"name": "approve_check_action",
"description": "[approval-rules] Before a consequential action, ask whether the user's rules auto-approve it. Returns auto_approve, needs_approval (with a plain-English approval card and a link the user can tap) or deny. Free plan is watch-only: it reports what it WOULD decide and logs it for the weekly report, but nothing counts as approved, so ask your user as you normally would.",
"inputSchema": {
"type": "object",
"required": [
"action"
],
"properties": {
"action": {
"type": "object",
"required": [
"type",
"summary"
],
"properties": {
"type": {
"type": "string",
"description": "Short verb: read, search, draft, send_email, send_message, post, purchase, payment, delete, deploy, change_settings, ..."
},
"target": {
"type": "string",
"description": "Who or what it touches: a recipient email, domain, file, repo."
},
"summary": {
"type": "string",
"description": "One plain sentence of what will happen, e.g. \"Buy a $3.99 domain renewal for example.com\"."
},
"amount_usd": {
"type": "number",
"description": "Money involved, if any."
},
"reversible": {
"type": "boolean",
"description": "Can it be undone easily?"
}
},
"description": "The action your agent wants to take."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "approval-rules: check_action"
}{
"name": "approve_get_decision",
"description": "[approval-rules] Check whether the user approved or rejected an approval card (by card_id and card_token). Only act when status is approved.",
"inputSchema": {
"type": "object",
"required": [
"card_id",
"card_token"
],
"properties": {
"card_id": {
"type": "string"
},
"card_token": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "approval-rules: get_decision"
}{
"name": "approve_get_rules",
"description": "[approval-rules] Show the rules in effect for your key (or the default starter rules).",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "approval-rules: get_rules"
}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/cloudforbots"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.botrecipe/cloudforbots"}) over MCP.
wake_schedule_wake ~413 tokensloop_check_step ~362 tokenssandbox ~352 tokensbudget_open_budget ~332 tokensapprove_check_action ~322 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%2Fcloudforbots?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.botrecipe%2Fcloudforbots?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.botrecipe%2Fcloudforbots.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.botrecipe%2Fcloudforbots.svg :target: https://glimind.com/server/mcp-registry%2Fcom.botrecipe%2Fcloudforbots?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:f03d2e9701e8337f…, first seen 2026-10-17, included at leaf 9922 of 73,973. Version history · verify what your client received.
Compare: most reliable ml servers · most reliable security servers · most reliable browser servers · most reliable other servers · most reliable finance 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-26 16:02 UTC, the Botrecipe Cloudforbots MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 25.5 hours.
Botrecipe Cloudforbots MCP server advertises 48 tools, including ai, approve_check_action, approve_get_decision, approve_get_rules, approve_set_rules.
Point your MCP client at this streamable-http endpoint: https://cloudforbots.com/mcp
Glimind scanned all 48 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.