Run Budget Guard
REMOTE · BUDGET.CLOUDFORBOTS.COM
Hard dollar, token, call and time caps shared by every sub-agent in one agent run.
Available components
Last scanned (9 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 784 tokens (~130/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- Tool “usage_and_upgrade” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://budget.cloudforbots.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=budget.cloudforbots.com | CN=YR2,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | RSA 2048 | SHA256-RSA | 5875a55b19a14ce26a1a7fc1c758c95d082 |
| SANs: budget.cloudforbots.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of budget.cloudforbots.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cloudforbots.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://budget.cloudforbots.com/mcp | Verified | 200 | |
| http (plaintext) | http://budget.cloudforbots.com/mcp | HTTPS enforced | 308 | https://budget.cloudforbots.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
budget_status ~84
See spend vs limits, remaining budget, whether the run is stopped and why, and the last 20 ledger events. Set close=true when the run finishes.
| Name | Type | Req | Description |
|---|---|---|---|
| close | boolean | – | – |
| handle | string | yes | The budget handle from open_budget (looks like bg_<id>.<secret>). Pass it to every sub-agent so they all spend from the same budget. |
No output schema declared.
No examples provided.
open_budget ~231
Open a hard budget for one agent run before it starts: max dollars, tokens, calls and/or wall-clock seconds. Returns a handle. Give the handle to every sub-agent; they all draw from the same ledger, so one runaway loop or fork cannot exceed the run cap.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | What this run is for, e.g. "nightly code cleanup". |
| max_calls | integer | – | Cap on model/tool calls for the whole run. |
| max_seconds | integer | – | Wall-clock cap in seconds from now. |
| max_tokens | integer | – | Token cap (input + output) for the whole run. |
| max_usd | number | – | Dollar cap for the whole run (your own estimates per call). |
| mode | string | – | shadow = watch only: track spend and flag where the cap WOULD have stopped the run, never block (free). enforce = return allowed=false at the cap (Pro). Default: enforce on Pro, shadow on free. |
| ttl_hours | integer | – | Handle lifetime (free max 24, Pro max 168). Default 24. |
No output schema declared.
No examples provided.
record ~99
After a call, report the actual usage minus what you reserved (positive if it cost more, negative to give back an overestimate). Keeps the ledger honest without blocking.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | The budget handle from open_budget (looks like bg_<id>.<secret>). Pass it to every sub-agent so they all spend from the same budget. |
| note | string | – | – |
| tokens | integer | – | – |
| usd | number | – | – |
No output schema declared.
No examples provided.
reserve ~174
Call BEFORE each model call, tool call or sub-agent spawn with your estimate. Returns allowed=true and deducts it, or allowed=false with the limit that tripped. When allowed is false, stop, do not retry, and return your partial result to the user. Atomic, so parallel sub-agents cannot both slip under the cap.
| Name | Type | Req | Description |
|---|---|---|---|
| calls | integer | – | Number of calls to reserve (default 1). |
| handle | string | yes | The budget handle from open_budget (looks like bg_<id>.<secret>). Pass it to every sub-agent so they all spend from the same budget. |
| note | string | – | Short note, e.g. "web_search #12". |
| tokens | integer | – | Estimated tokens of the next call. |
| usd | number | – | Estimated cost of the next call in USD. |
No output schema declared.
No examples provided.
usage_and_upgrade ~46
Show today's usage for your key or IP and the $49/month All Access upgrade link (cloudforbots.com/offer). Free tier: 500 calls/day. Not metered.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
weekly_report ~60
Draft a plain-English report of the last 7 days for your key (or IP): runs, spend, runs that went over their cap, and dollars spent after a cap would have stopped them. Read-only; sends nothing. Show it to your user.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Run Budget Guard MCP server?
Run Budget Guard is a hosted endpoint at https://budget.cloudforbots.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · budget.cloudforbots.com
claude mcp add --transport http com-botrecipe-budget 'https://budget.cloudforbots.com/mcp'
What is the Run Budget Guard MCP server?
Run Budget Guard is an MCP server listed in the public MCP registry as com.botrecipe/budget. Hard dollar, token, call and time caps shared by every sub-agent in one agent run. This page covers its hosted endpoint (https://budget.cloudforbots.com/mcp).
Is the Run Budget Guard MCP server safe to use?
Run Budget Guard scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Run Budget Guard MCP server expose?
Run Budget Guard exposes 6 tools: open_budget, reserve, record, weekly_report, budget_status, usage_and_upgrade. Their descriptions and schemas cost roughly 694 tokens of context every time the server is loaded.
Does the Run Budget Guard MCP server require authentication?
No. We connected to Run Budget Guard without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Run Budget Guard MCP server still maintained?
Run Budget Guard is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.