English Français العربية

Eclipse Agent Wallet MCP

Official registry Finance and payments

Policy-scoped agent wallet: caps, recipient allowlist, human approvals, kill switch, audit trail.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

OCI package ghcr.io/cyan-eclipse-technologies-llc/agent-wallet-mcp:2842d69a363c4412a4c1347878fd27b7ca9d9aeb
Claude Code 
claude mcp add eclipse-agent-wallet-mcp -e 'AGENT_WALLET_LEDGER=<AGENT_WALLET_LEDGER>' -- docker run -i --rm ghcr.io/cyan-eclipse-technologies-llc/agent-wallet-mcp:2842d69a363c4412a4c1347878fd27b7ca9d9aeb
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "eclipse-agent-wallet-mcp": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "ghcr.io/cyan-eclipse-technologies-llc/agent-wallet-mcp:2842d69a363c4412a4c1347878fd27b7ca9d9aeb"
            ],
            "env": {
                "AGENT_WALLET_LEDGER": "<AGENT_WALLET_LEDGER>"
            }
        }
    }
}

Environment variables

  • AGENT_WALLET_LEDGER Path to the wallet ledger JSON file. Defaults to ledger.json beside the server. Sandbox reference implementation: simulated test USDC only, no real funds.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Eclipse Agent Wallet MCP
  2. Why this exists
  3. Status
  4. Tools (10)
  5. Run it
  6. Roadmap
  7. License / attribution

Eclipse Agent Wallet MCP

Powered by Cyan Eclipse Technologies — https://cetech.ai Listed on Eclipse Bazaar (eclipsebazaar.com).

Why this exists

On November 24, 2026, Wells Fargo's Online Access Agreement Section 15 takes effect: anything your AI agent does with your bank account is legally you — "at your own risk," including transactions you did not want or intend, with no controls attached and no duty on the bank to watch.

This MCP server is the opposite design: an agent wallet where responsibility follows scope.

  • The human owner grants a written policy: per-transaction cap, daily cap, approval threshold, recipient allowlist, expiry, purpose.
  • The agent can spend only inside that scope. Outside it, payments are rejected — or routed to a human approval queue when they exceed only the approval threshold.
  • Every grant, payment, rejection, approval and revocation is written to an append-only audit log — the evidence of what was actually authorized.
  • A kill switch freezes the wallet instantly, with the revocation timestamped in the log. Revoking access to your bank means "notify us and wait"; here it is immediate and provable.

Status

v0.1.0 reference implementation. Sandbox only — balances are simulated test USDC in a local JSON ledger. No real funds, no private keys, no network calls. The policy engine is the product; production payment rails (x402, partner processors) plug in behind it without changing the tool surface.

Tools (10)

ToolWhat it does
create_walletCreate a wallet owned by a named human. Cannot spend until a policy is granted.
get_walletBalance, frozen state, today's spend, active policy.
set_policyOwner grants the spending scope; returns a plain-language liability receipt.
fund_walletSandbox faucet (simulated test USDC) for demos/tests.
check_paymentDry-run: returns allow / approve / deny with the reason. Agents call this before pay.
payExecute inside scope; reject outside it; queue for approval above the threshold.
approve_payment / deny_paymentOwner resolves a queued request.
audit_logThe full append-only trail.
revokeKill switch — freeze instantly.

Run it

python3 server.py            # MCP over stdio, stdlib only, no dependencies

State persists in ledger.json beside the server (override with AGENT_WALLET_LEDGER).

Use it with your Muse (custom connector / local MCP)

Point your agent's MCP configuration at the command python3 /path/to/server.py — any MCP client (Muse, Muse, Cursor) can drive it. A worked example session:

  1. create_wallet {owner_id: "you@example.com"} → wallet created, cannot spend.
  2. set_policy {per_tx_cap_usdc: "50.00", daily_cap_usdc: "120.00", approval_above_usdc: "20.00", allowlist: ["0xMerchantA"], purpose: "API credits"} → liability receipt issued.
  3. pay 10.00 to 0xMerchantA → executed. pay 60.00 → rejected (over cap). pay 30.00 → human approval required.
  4. revoke → frozen, timestamped. Agent's authority ends the second the owner says so.

Roadmap

  • v0.2: hosted HTTP transport + per-user API keys; policy templates (shopping, SaaS, research budgets).
  • v0.3: real rails behind the same policy engine — x402/USDC settlement, partner-processor fiat — only under the owner's granted scope.
  • v1.0: Eclipse Bazaar listing with live test-bench scorecard (policy-engine conformance suite runs against every release).

License / attribution

A Cyan Eclipse Technologies product. The "Powered by Cyan Eclipse Technologies" attribution travels with it.

Frequently asked questions

What is Eclipse Agent Wallet MCP?

Policy-scoped agent wallet: caps, recipient allowlist, human approvals, kill switch, audit trail.

How do I install Eclipse Agent Wallet MCP?

It runs on your machine. In Claude Code: claude mcp add eclipse-agent-wallet-mcp -e 'AGENT_WALLET_LEDGER=<AGENT_WALLET_LEDGER>' -- docker run -i --rm ghcr.io/cyan-eclipse-technologies-llc/agent-wallet-mcp:2842d69a363c4412a4c1347878fd27b7ca9d9aeb. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Eclipse Agent Wallet MCP need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Eclipse Agent Wallet MCP open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Eclipse Agent Wallet MCP?

It is published by CYAN-ECLIPSE-TECHNOLOGIES-LLC. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.