The default changed in v1.3.0 from all to essentials, which matters if you relied on the commerce or webhook tools appearing without a flag. Everything the agent does lands on a hash-chained ledger — the signed receipt is the artifact a regulated buyer actually verifies.
The MCP server bundled with @mnemopay/sdk. It sits above the payment rail and below the agent runtime: a charter declares what the agent may spend, FiscalGate reserves funds before the call, and every action hashes into a Merkle-chained ledger.
- 14 tools by default in the essentials group, about 1K tokens
- Memory — remember, recall, forget, reinforce, consolidate
- Wallet — balance, profile, history, logs
- Transactions — charge, settle, refund, dispute, receipt_get
- 95 tools in total, opted into by group: memory, wallet, tx, commerce, hitl, payments, webhooks, reputation, security, governance, identity, skills, spatial, agent_os, organization_admin and operator
- Signed receipts on the audit chain, and Article 12 audit bundles replaying every event, refusal and memory write
- An agent reputation score from 300 to 850, built from payment history, credit utilisation, history length, behaviour diversity and fraud record
- Six payment rails behind one interface — Stripe, Paystack, Lightning, Stripe MPP, x402 and Google AP2
Npx -y --package=@mnemopay/sdk mnemopay-mcp, or claude mcp add mnemopay -s user -- npx -y @mnemopay/sdk. MNEMOPAY_API_KEY and MNEMOPAY_PERSIST_DIR (default ~/.mnemopay) are both optional; a free sandbox key is available without a card. Pass --tools or set MNEMOPAY_TOOLS to widen past the default group. A hosted server at api.mcp.mnemopay.com runs the same surface without the local SDK.
One command plus a key — npx @mnemopay/sdk init, then supply credentials