Get started
The bounded agent
Put a gateway in front of any MCP server and your agent cannot exceed its scope, its budget, or its lifetime — and you can prove what it did.
auths-mcp is the bounded-agent MCP gateway. It sits between an agent and its tools, holds a scoped, budget-bound, instantly-revocable delegation for that agent, and refuses any tools/call that exceeds it — at the protocol boundary, before the tool runs.
The cap is a seatbelt, not a setting. With a $20 budget the agent cannot spend $20.01. Not shouldn't — cannot: the gateway reserves each charge against the cap before the rail is touched and refuses the call that would cross it.
The refusal is the product. Every call — allowed or refused — leaves a signed receipt, and anyone can re-derive the spend from the receipts alone, offline, without trusting you or us. See receipts.
Where to start
Wrap a filesystem server and watch a refusal in five minutes. No card, no wallet, nothing at risk.
Put a real model on real rails — Stripe and on-chain USDC — behind one cap it provably cannot cross.
What the gate refuses
Every tools/call runs one gate and fails closed. A call outside the granted scope is outside-agent-scope. A call that would cross the budget is usage-cap-exceeded. A call after the delegation expires is agent-expired. A call after you revoke is revoked. On any of them, the downstream tool is never invoked.
How each bound works — and why you can check the receipts yourself — is four short pages: the gate, budgets, custody, and receipts.