Skip to main content

spendctl

dev.spendctl/spendctlVersion 0.1.0

Spend policy for AI agents that pay (x402, MPP). Login-free sandbox, real sidecar, no real funds.

Status

Responds300 msAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 14:27 UTC
Latency
300 ms
Remotes responding
1 of 1
Sign-in
No sign-in
Hosting
Hosted outside the EU (detected)
Registry data as of
Nov 14, 2026, 21:12 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://mcp.spendctl.dev/mcpResponds300 ms
No sign-in

Claude Code

claude mcp add --transport http spendctl https://mcp.spendctl.dev/mcp

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: spendctl
Remote MCP server URL: https://mcp.spendctl.dev/mcp

Cursor

{
  "mcpServers": {
    "spendctl": {
      "url": "https://mcp.spendctl.dev/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"spendctl","type":"http","url":"https://mcp.spendctl.dev/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

8 tools

Tools of spendctl
Read-only
Idempotent
Open world
approveApproves or denies a payment that sandbox_pay reported as waiting for approval, as the human approver would with `spendctl approve`. Use it only with an approval id from this sandbox; in the real product a human decides, in the sandbox the model plays that role. Returns the approval id and its new status (approved or denied). An approved payment completes when sandbox_pay is called again with the same approvalId; a denied one stays refused. Deciding the same approval twice keeps the first decision.NoNoYesNo
await_approvalWaits for the decision on a payment that sandbox_pay reported as held, without paying again: long-polls the sandbox sidecar for up to timeoutSeconds (default 10, at most 20) and returns pending, approved, denied, expired or withdrawn, with the ledger entry and the decision deadline. This is what an agent does in the real product while a human decides; in the sandbox the model is also the approver (approve), so call approve from another turn or first. After approved, repeat sandbox_pay with approvalId to complete the payment. Read-only; never pays and never decides.Not declaredYesNot declaredNo
check_budgetShows the sandbox agent's spending limits, what has been spent in each window and what is left. Use it before a paid call when the remaining budget matters, or after a refusal to see which limit was hit. Returns the agent name and mode, the per-request limit, the approval threshold, what happens when a budget is exceeded, the allowed hosts and one line per window (hourly, daily: spent, limit, remaining). Read-only; changes nothing.Not declaredYesNot declaredNo
get_policyReturns the sandbox's spendctl.yaml as text: the preset name and the agent's budgets, allowed hosts and approval rules. Use it to explain why a payment was refused or held, or to show what a spendctl policy file looks like. Read-only; the sandbox policy cannot be changed, create a sandbox with another preset instead.Not declaredYesNot declaredNo
list_receiptsLists the sandbox agent's most recent payment attempts, newest first: paid (amount and mock transaction hash), refused (reason codes) and waiting for approval. Use it to report what happened so far or to find a receipt id; after a hold, the approval id is in the sandbox_pay result. Returns up to `limit` lines, one per attempt, with time, receipt id, method, URL, amount and status, or "No payments yet." Read-only.Not declaredYesNot declaredNo
sandbox_createCreates an isolated spendctl sandbox and returns its sandbox_id. Call it first: every other tool needs the sandbox_id, and one sandbox serves a whole conversation (create another only to try a different preset). The sandbox is a real spendctl sidecar with a throwaway wallet, a mock x402 facilitator and two mock paid APIs; no real money moves and nothing outside the sandbox is reachable. Returns the sandbox_id, the agent's policy (budgets, allowed hosts, approval rule) and the paid endpoints with their prices. Limits: 5 sandboxes per minute per client address (claude.ai users share addresses and get a larger allowance); a sandbox expires after 2 hours without calls (24 hours at most). Example: preset "strict" to see refusals, "approvals" to see a payment held for a human.NoNoNoNo
sandbox_payFetches one of the sandbox's paid endpoints (HTTP 402, x402) through the spendctl sidecar, which applies the sandbox agent's budget, allowlist and approval policy, pays with the throwaway wallet if allowed, and returns the response. Use it for every paid call in the sandbox: with dryRun to see the decision without paying, with approvalId to complete a payment that was held and then approved. The endpoints are https://weather.sandbox.spendctl.dev/weather?city=<name> ($0.01) and https://search.sandbox.spendctl.dev/search?q=<query> ($0.02), as listed by sandbox_create and documented at https://spendctl.dev/docs/sandbox/; any other host is refused. Returns a one-line summary (HTTP status, amount paid, decision, receipt id) followed by the response body, or the refusal with its reason, or an approval id when the payment is waiting for a human. On a client that supports MCP input requests (protocol revision 2026-07-28, form elicitation) a held payment comes back as an input_required result asking the user to approve or deny, and the client's retry completes or refuses it; other clients get the approval id as text. Only sandbox hosts exist and no real funds are involved; the request is always a GET and responses are clipped at 20,000 characters. Example: url https://weather.sandbox.spendctl.dev/weather?city=KyotoNoNoNoNo
withdraw_approvalTakes back a payment that sandbox_pay reported as held, as a real agent does when the task that needed the payment was cancelled or superseded: nothing is paid, the approval closes as withdrawn (distinct from deny), a later approve on that id is refused and await_approval answers withdrawn at once. Use it with an approval id from this sandbox; a new sandbox_pay call opens a fresh approval if the payment is wanted after all. Withdrawing an id that was already decided reports that decision as an error.NoNoYesNo

Details

Registry status
Active
Published
Oct 26, 2026
Updated
Oct 26, 2026
Repository
Not given
Categories (suggested)
Finance and paymentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR
Not declared

Are you the operator? Claim this listing