
walletcap for Coinbase payments MCP
io.github.coriolislabsPublished by GitHub account coriolislabsv0.3.0Updated Nov 7, 2026
Spend limits for Coinbase's payments MCP: a per-payment cap and rolling 24h USDC budget per wallet
The publisher's own server: Payments Ai Mcp
Overview
Spend-limit guard for Coinbase payments MCP wallets: a per-payment cap and a rolling 24-hour USDC budget shared across processes on one host.
- What you can do
- Set, inspect and freeze a wallet's spend budget from the command line
- Reserve each USDC payment against one per-wallet budget inside a single write transaction
- Enforce a rolling 24-hour window that survives restarts, extra replicas and key changes
- Wrap payments in code through an openBudget helper that refuses amounts over the cap
- Guard x402, Coinbase CDP spend store, Agentic Wallet, AgentKit and Spend Permissions rails
- When to use it
- Use it when an AI agent pays in USDC from a wallet and you want a hard ceiling on what it can spend, especially when several processes or replicas share the same wallet and a restart must not hand the agent a fresh budget.
- Requirements
- Local process run with npx; Node 22.13 or newer. One SQLite file on a single host, shared by every process and by Python; not over NFS, SMB or Docker Desktop bind mounts. The owner sets the budget once with the set command before payments can be made.
Installation
In SourceWeft
- Open walletcap for Coinbase payments MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
walletcap
Spend limits for AI agent wallets that pay in USDC: a per-payment cap and a rolling 24-hour budget that holds across restarts, replicas on one host and payment rails.
One spend budget per wallet for AI agents: counted across every process, replica, key, permission and payment rail on one host that pays from it. A restart, a second replica, one more key or the next calendar period cannot hand the agent a fresh budget.
npx walletcap-crash-test puts Coinbase's agent spend controls through a restart, 10 replicas,
a shared store and a payee who asks for EURC, then puts walletcap through the same events,
offline. In eight runs, CDP's controls let $1,600–$1,700 and 1,000 EURC past a $150 cap;
walletcap let $0.
The owner creates the budget once; opening it never creates one:
- Per wallet, not per process. Every payment from the wallet reserves against one number.
- Rolling window. "$150 a day" means any 24 hours; there is no boundary to straddle.
- Edits never reset the count. Raising $150 to $200 after spending $150 leaves $50.
- Fail closed. If the count can't be read, nothing pays; a missing file is not a new budget. Unknown outcomes keep counting.
- One SQLite file on one host, shared by every process there and by Python. Each payment reserves inside one write transaction, so replicas racing for the last dollar cannot both win. Not over NFS, SMB or Docker Desktop bind mounts, where SQLite's locks aren't reliable.
- x402 guard, Coinbase CDP spend store, Agentic Wallet wrapper, AgentKit recipe, and an on-chain cap for Spend Permissions.
- Node 22.13+, zero runtime dependencies, Apache-2.0.
Security: policy ·
threat model.
AccountCapSpender is unaudited; testnet only until an independent audit.
Source, Python package and full documentation · docs for x402, Coinbase CDP spend controls, AgentKit, the Agentic Wallet and payments MCP and Spend Permissions
Apache-2.0. Copyright 2026 Coriolis Labs Inc.
Source: js/README.md at commit 918232e
Tools
0Version history
1- v0.3.0LatestNov 7, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Payments integrations
Payments Ai Mcp
ai.payments.managedOfficial publisher
Remote MCP endpoint from Payments AI, a Merchant of Record, for launching products and branded checkouts for AI-built apps.

Qut Pay (Kaspi QR payments)
kz.qutOfficial publisher
Qut Pay MCP server for Kaspi QR payments in Kazakhstan: create, check, cancel and refund invoices, and simulate sandbox payments.

FawryPay cash payments (unofficial)
Published by GitHub account mohamedaly-cloud
Unofficial local MCP server that lets an assistant work with FawryPay Pay-at-Fawry cash payments in Egypt, including optional refund and cancel tools.

Toss Payments
Published by GitHub account groove79
Local MCP server for Toss Payments that lets an assistant look up payments, list transactions and settlements, and cancel or refund with human approval.

SelfPaidPal — Autonomous DeFi Payments
Published by GitHub account altoninelli
Local MCP server that lets an assistant check DeFi lending yields on Base, quote collateral needed to fund a payment from yield, and build unsigned EVM…