Agent Wallet MCP

Name: Agent Wallet MCP
Author: dingdawg

dingdawg/agent-wallet-demo

Updated August 6, 2026
dingdawg/agent-wallet-demo

Agent Wallet is a MCP server that provides AI agents a policy-governed USDC wallet with caps and signed receipts.

About

Agent Wallet MCP exposes a governed USDC wallet to coding agents through the Model Context Protocol. developers experimenting with paid APIs, on-chain micropayments, or agent marketplaces can cap risk with policy gates and spending limits rather than handing agents raw keys. Each action can produce Ed25519-signed receipts, which helps when you need a paper trail for support, accounting, or safety reviews. The published npm identifier is dingdawg-agent-wallet at version 1.0.6 with stdio transport. Treat it as financial infrastructure you integrate during Build: define policies in your product, register the MCP server, and test on staging before any real funds. It complements generic payment SDKs by framing controls specifically for autonomous spend.

Governed USDC wallet for AI agents with policy gates and spending caps
Ed25519-signed receipts for auditable agent transactions
npm stdio package dingdawg-agent-wallet at server version 1.0.6
MCP server.schema.json 2025-12-11 metadata for registry discovery
Demo-oriented repo agent-wallet-demo on GitHub for integration patterns

Agent Wallet MCP by the numbers

Data as of Aug 10, 2026 (Skillselion catalog sync)

terminal

claude mcp add dingdawg-agent-wallet -- npx -y dingdawg-agent-wallet

Add your badge

Show developers this MCP server is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/mcp/tool/io.github.dingdawg/agent-wallet.svg)](https://skillselion.com/mcp/tool/io.github.dingdawg/agent-wallet)

Package	dingdawg-agent-wallet
Transport	STDIO
Auth	None
Last updated	August 6, 2026
Repository	dingdawg/agent-wallet-demo ↗

What it does

Give autonomous agents a USDC wallet with policy gates, spending caps, and signed receipts instead of unchecked API spend.

Who is it for?

Best when you're adding agentic checkout, API prepay, or on-chain spend with hard policy boundaries.

Skip if: Products with no autonomous spending, or teams that only need manual Stripe dashboards without agent wallets.

What you get

After integration, agent payments run through governed USDC flows with spending limits and Ed25519-signed receipts you can verify.

MCP tools for capped USDC agent spending
Ed25519-signed transaction receipts for audit and debugging

By the numbers

Server version 1.0.6 via npm identifier dingdawg-agent-wallet
stdio MCP transport; schema 2025-12-11
GitHub demo: github.com/dingdawg/agent-wallet-demo

README.md

dingdawg-agent-wallet — live demo

Shows governed agent wallet enforcement in action: allow, deny, step-up, allowlist — all in 5 seconds. No API keys. No blockchain required.

What it demonstrates

▶ provision_wallet
  wallet_id:    demo-wallet-abc123
  daily_cap:    $200 USDC
  per_call_cap: $100 USDC

▶ governed_spend — $25 USDC (allowed)
  ✓ AUTHORIZED
  receipt_id:      6aba84a6-...
  daily_remaining: $175 USDC
  next_step:       wallet.sendToken({ assetId: "usdc", amount: "25", destination: "0xVendorABC123" })

▶ governed_spend — $150 USDC (exceeds per-call cap)
  ✗ DENIED
  reason:      Amount 150 USDC exceeds per-call cap 100 USDC
  receipt_id:  cd7a7aa8-... (denial is logged too)

▶ governed_spend — $75 USDC (step-up required)
  ⚠ STEP-UP REQUIRED
  reason: Amount 75 USDC > step-up threshold 50 USDC — MFA required
  fix:    Pass approval_token from your authorization flow

▶ governed_spend — unknown recipient (not in allowlist)
  ✗ DENIED
  reason: Recipient 0xUnknownAddress not in allowlist

▶ wallet_audit
  chain_verified: true ✓
  total_receipts: 5
  [17:02:18] DENY  $10 USDC    governed_spend
  [17:02:18] DENY  $75 USDC    governed_spend
  [17:02:18] DENY  $150 USDC   governed_spend
  [17:02:18] ALLOW $25 USDC    governed_spend
  [17:02:18] ALLOW              provision_wallet

Every action — allow AND deny — produces an immutable receipt. chain_verified: true means the full chain is tamper-evident — any modification is detectable.

Run it

git clone https://github.com/DingDawg/agent-wallet-demo
cd agent-wallet-demo
npm install
node demo.mjs

The package

dingdawg-agent-wallet — 5 MCP tools that wrap any agent wallet with policy enforcement and an immutable audit trail.

npm install dingdawg-agent-wallet

Tool	What it does
`provision_wallet`	Create wallet with spend policy (daily cap, per-call cap, allowlist)
`governed_spend`	Policy check → authorize → immutable receipt
`governed_receive`	Accept payment with tamper-evident receipt
`wallet_policy`	Update limits and allowlists at runtime
`wallet_audit`	Full receipt chain — `chain_verified: true`

Coinbase AgentKit gives your agent a wallet. DingDawg gives it a conscience.

Why this matters

AI agents can now hold USDC and spend autonomously. The infrastructure exists. What doesn't: who enforces what the agent is allowed to spend, on what, for whom — and proves it happened correctly.

governed_spend authorizes then returns the exact agentkit_call SDK method to execute on-chain
Every denial is logged — you can prove what your agent didn't do
chain_verified: true means the audit trail is tamper-evident — any modification is detectable

npm · DingDawg