_ registry / mcp streamable-http · checked 1h ago

run-budget-guard

https://budget.cloudforbots.com

Registry code: 3200b272d9b1df32

api record

Spending caps for one AI agent run, shared by every sub-agent. Free watch-only mode tracks spend and drafts a weekly report of runs that went over; Pro enforces the cap with a clear STOP before the next model or tool call. $9 a month. Free 500 calls/day, then $9/month. No model inside: bring your own model. Works with Claude, Codex, ChatGPT, Grok Bot.

endpoint
https://budget.cloudforbots.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is run-budget-guard live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is run-budget-guard free to use?
Yes — the hub reached it with no key and no payment.
What tools does run-budget-guard have?
6 tools: budget_status, open_budget, reserve, record, weekly_report, usage_and_upgrade.
Is run-budget-guard safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
508ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • budget_status unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "handle"
      ],
      "properties": {
        "close": {
          "type": "boolean"
        },
        "handle": {
          "type": "string",
          "description": "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."
        }
      }
    }
    arguments 15 lines
  • open_budget unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "mode": {
          "enum": [
            "shadow",
            "enforce"
          ],
          "type": "string",
          "description": "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."
        },
        "label": {
          "type": "string",
          "description": "What this run is for, e.g. \"nightly code cleanup\"."
        },
        "max_usd": {
          "type": "number",
          "description": "Dollar cap for the whole run (your own estimates per call)."
        },
        "max_calls": {
          "type": "integer",
          "description": "Cap on model/tool calls for the whole run."
        },
        "ttl_hours": {
          "type": "integer",
          "description": "Handle lifetime (free max 24, Pro max 168). Default 24."
        },
        "max_tokens": {
          "type": "integer",
          "description": "Token cap (input + output) for the whole run."
        },
        "max_seconds": {
          "type": "integer",
          "description": "Wall-clock cap in seconds from now."
        }
      }
    }
    arguments 37 lines
  • reserve unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "handle"
      ],
      "properties": {
        "usd": {
          "type": "number",
          "description": "Estimated cost of the next call in USD."
        },
        "note": {
          "type": "string",
          "description": "Short note, e.g. \"web_search #12\"."
        },
        "calls": {
          "type": "integer",
          "description": "Number of calls to reserve (default 1)."
        },
        "handle": {
          "type": "string",
          "description": "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."
        },
        "tokens": {
          "type": "integer",
          "description": "Estimated tokens of the next call."
        }
      }
    }
    arguments 28 lines
  • record unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "handle"
      ],
      "properties": {
        "usd": {
          "type": "number"
        },
        "note": {
          "type": "string"
        },
        "handle": {
          "type": "string",
          "description": "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."
        },
        "tokens": {
          "type": "integer"
        }
      }
    }
    arguments 21 lines
  • weekly_report unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • usage_and_upgrade unknown never probed

    Show today's usage for your key or IP and the $9/month upgrade link. Free tier: 500 calls/day. Not metered.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3200b272d9b1df32.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3200b272d9b1df32/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/3200b272d9b1df32/badge.svg)](https://brick.blue/agent/3200b272d9b1df32?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on cloudforbots.com 3 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.