Run Budget Guard MCP server
com.botrecipe/budgetbotrecipe.comstreamable-httpv1.0.1Scanned
Hard dollar, token, call and time caps shared by every sub-agent in one agent run.
6 tools: 4 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 3 findings, 3 high
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Run Budget Guard MCP server can do
The Run Budget Guard MCP server is published by botrecipe.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (4 tools: open_budget, reserve, record and weekly_report), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 3 findings, 3 of them high severity (model-directed-text). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 17, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 4Claude Code: ask
open_budgetOpen a hard budget for one agent run before it starts: max dollars, tokens, calls and/or wall-clock seconds.No findings
Why it is in this group
- The name "open_budget" says "open": a word for a change.
Description, as the server wrote it 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.
recordAfter a call, report the actual usage minus what you reserved (positive if it cost more, negative to give back an overestimate).1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Findings
- High
The input schema at properties.handle.description contains "<secret>", a tag of the kind used to mark instructions for the model.
What this check looks forMatched text
inputSchema.properties.handle.description: "...le from open_budget (looks like bg_<id>.<secret>). Pass it to every sub-agent so they al..."
Description, as the server wrote it 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.
reserveCall BEFORE each model call, tool call or sub-agent spawn with your estimate.1 finding
Why it is in this group
- The description's first verb is "call": a word for a change.
Findings
- High
The input schema at properties.handle.description contains "<secret>", a tag of the kind used to mark instructions for the model.
What this check looks forMatched text
inputSchema.properties.handle.description: "...le from open_budget (looks like bg_<id>.<secret>). Pass it to every sub-agent so they al..."
Description, as the server wrote it 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.
weekly_reportDraft 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Only reads 2Show 2 read-only tools
budget_statusSee spend vs limits, remaining budget, whether the run is stopped and why, and the last 20 ledger events.1 finding
Why it is in this group
- The name "budget_status" says "status": a word for reading.
Findings
- High
The input schema at properties.handle.description contains "<secret>", a tag of the kind used to mark instructions for the model.
What this check looks forMatched text
inputSchema.properties.handle.description: "...le from open_budget (looks like bg_<id>.<secret>). Pass it to every sub-agent so they al..."
Description, as the server wrote it 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.
usage_and_upgradeShow today's usage for your key or IP and the $49/month All Access upgrade link (cloudforbots.com/offer).No findings
Why it is in this group
- The description's first verb is "show": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:22 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://budget.cloudforbots.com/mcp: tools/list returned 6 tools to an anonymous client, including open_budget (write), reserve (write), record (write), weekly_report (write)
Findings
Matches of fixed checks, with the text they matched.
- Highreserve
The input schema at properties.handle.description contains "<secret>", a tag of the kind used to mark instructions for the model.
What this check looks forMatched text
inputSchema.properties.handle.description: "...le from open_budget (looks like bg_<id>.<secret>). Pass it to every sub-agent so they al..."
- Highrecord
The input schema at properties.handle.description contains "<secret>", a tag of the kind used to mark instructions for the model.
What this check looks forMatched text
inputSchema.properties.handle.description: "...le from open_budget (looks like bg_<id>.<secret>). Pass it to every sub-agent so they al..."
- Highbudget_status
The input schema at properties.handle.description contains "<secret>", a tag of the kind used to mark instructions for the model.
What this check looks forMatched text
inputSchema.properties.handle.description: "...le from open_budget (looks like bg_<id>.<secret>). Pass it to every sub-agent so they al..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http budget https://budget.cloudforbots.com/mcpclaude mcp add --transport http budget https://budget.cloudforbots.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__budget__budget_status",
"mcp__budget__usage_and_upgrade"
],
"ask": [
"mcp__budget__open_budget",
"mcp__budget__reserve",
"mcp__budget__record",
"mcp__budget__weekly_report"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as budget. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.botrecipe/budget/verify?hash=5c29d2ba8e12010118d01efd687083a20694a2d750f510d35dafb0be3ec8ea9c" | jq -e '.changed == false'Pinned hash 5c29d2ba8e12, from Nov 17, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.botrecipe/budget/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.botrecipe/budget)Source: MCP Registry. Synced Oct 21, 2026, 17:52 UTC.
Run Budget Guard MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Run Budget Guard MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 3 findings (3 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Run Budget Guard MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Run Budget Guard MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Run Budget Guard MCP server have?
- 6 tools: 4 write, 2 read. open_budget, reserve, record, weekly_report, budget_status and usage_and_upgrade.
Does the Run Budget Guard MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Run Budget Guard MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Run Budget Guard MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.