Budget & cost control for AI agents — per-agent spend caps + rate limits before each call.
Spend caps, rate coordination, idempotency, and a human-in-the-loop gate for AI agents — enforced before the call, not after the invoice. One MCP endpoint, settled via x402 (USDC on Base). No proxy, no self-hosting, no infrastructure to deploy. Listed on the Official MCP Registry as . Agents cost 10–12× more than estimated in production. System prompts, retry loops, and tool calls multiply fast —…
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
budget_clearNo description publishedThis tool published no description. Forge does not invent one.
set_envelopeNo description publishedThis tool published no description. Forge does not invent one.
get_balanceNo description publishedThis tool published no description. Forge does not invent one.
reconcileNo description publishedThis tool published no description. Forge does not invent one.
set_rate_envelopeNo description publishedThis tool published no description. Forge does not invent one.
rate_checkNo description publishedThis tool published no description. Forge does not invent one.
idempotency_checkNo description publishedThis tool published no description. Forge does not invent one.
request_approvalNo description publishedThis tool published no description. Forge does not invent one.
check_approvalNo description publishedThis tool published no description. Forge does not invent one.
0 of 9 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Spend caps, rate coordination, idempotency, and a human-in-the-loop gate for AI agents — enforced before the call, not after the invoice. One MCP endpoint, settled via x402 (USDC on Base). No proxy, no self-hosting, no infrastructure to deploy. Listed on the Official MCP Registry as . Agents cost 10–12× more than estimated in production. System prompts, retry loops, and tool calls multiply fast — a runaway agent can generate a $47,000 bill in 11 days. The usual fix, self-hosting a gateway like…
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.