Cloud for Bots
MCP server · cloudforbots.com · found in a public registry · checked since 2026-10-17
Live, handshake completed · latest check
GET https://cloudforbots.com/mcpThe name is the registry's label, not ours. Not reviewed by a person. See 14 endpoints from cloudforbots.com.
Our checks
An unpaid request daily, from eastern North AmericaLast 3 checks, oldest to newest; room for 27 more
3 passed, 0 failed, 27 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Details
Tools listed by the server
aiapprove_check_actionapprove_get_decisionapprove_get_rulesapprove_set_rulesapprove_usage_and_upgradeapprove_weekly_reportbrowserbudget_budget_statusbudget_open_budgetbudget_recordbudget_reservebudget_usage_and_upgradebudget_weekly_reportcronfetchhandoffinboxledgerlibrary_getlibrary_installlibrary_publishlibrary_ratelibrary_reportlibrary_searchlockloop_check_steploop_loop_statusloop_usage_and_upgradeloop_weekly_reportmemory_list_checkpointsmemory_resumememory_save_checkpointmemory_usage_and_upgradememory_weekly_reportqueueratereplayreportsandbox+8
- Tools
- 48
- This list since
- 2026-10-19
- First listed to us
- 2026-10-19
- List changes, 90 days
- 0
Names as the server reported them at our latest completed handshake (mcp-handshake/1); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- Credentials needed, by its MCP Registry entry (a secret header)
- Payment model
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Listing
In the capability tree: Other (not placed in a branch yet) (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/3, tree/3) on 2026-10-18. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/4): ✗ what it does is unclear to our placement; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:MIA |
Live, MCP endpoint answered HTTP 200 | 735 ms |
cloudflare:MIA |
Live, MCP endpoint answered HTTP 405 | 210 ms |
cloudflare:MIA |
Live, MCP endpoint answered HTTP 405 | 267 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/1) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. The registry's description is not republished.
- Limited evidence: monitored for 2 days (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_6b75b63471f272ec