What it does
The server lets a named owner create a wallet and grant a written policy with per-transaction and daily caps, a recipient allowlist, an approval threshold, an expiry and a stated purpose. The agent can pay only inside that scope. Payments outside it are rejected, and payments above the approval threshold wait in a queue for the owner to approve or deny. Each grant, payment, rejection, approval and revocation is recorded in an append-only audit log. A revoke tool freezes the wallet at once and timestamps the change in the log. The tool set has ten tools, including a dry-run check that returns allow, approve or deny before a payment is made.
Developers building agents that make payments can use it to test how spending limits, approvals and audit records behave before connecting real payment rails. The publisher states that production payment rails are not included and would be added behind the same policy engine. An optional desk binding ties a wallet to a secp256k1 desk key held outside the server, and every spend must then carry a signature from that key, which the server verifies. Wallets without a binding work without it.
The server is run with python3 and configured as a local MCP server in an MCP client such as Cursor. Balances are simulated test USDC stored in a local ledger.json file beside the server, and that path can be overridden with an environment variable.
Limitations and requirements
Sandbox only: balances are simulated test USDC in a local JSON ledger, no real funds move and no network calls are made. Production payment rails are not included. Desk-bound wallets require a desk key held in envelope custody outside the server and a signature on every spend. The publisher states the desk extension has been benched separately from the base policy engine. Requires a Python 3 runtime and an MCP client that can run a local command.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
Eclipse Agent Wallet MCP
Policy-scoped agent wallet: caps, recipient allowlist, human approvals, kill switch, audit trail.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it