Sdk
Give autonomous agents persistent memory, wallet rails, scored trust (Agent FICO), and Merkle-audited identity so paid agent workflows are buildable without bespoke ledger code.
Overview
com.mnemopay/sdk is a MCP server for the Build phase that connects agents to MnemoPay memory, wallet, payments, Agent FICO (300–850), Merkle audit, and identity over stdio.
What is this MCP server?
- Memory and wallet for AI agents with real payment rails (publisher description)
- Agent FICO trust scoring on a 300–850 scale per metadata
- Merkle audit trail and identity surfaces for agent commerce
- stdio MCP via npx @mnemopay/sdk mnemopay-mcp; MNEMOPAY_API_KEY and optional MNEMOPAY_PERSIST_DIR (~/.mnemopay)
- SDK MCP package version 1.4.2
- Agent FICO scale documented as 300–850
- stdio MCP via npx @mnemopay/sdk and mnemopay-mcp
Community signal: 5 GitHub stars.
What problem does it solve?
Shipping an agent that must remember deals and move money forces you to bolt together wallets, audit logs, and trust signals without a unified MCP surface.
Who is it for?
Indie agent builders prototyping payable, memoryful agents who want MCP-native MnemoPay instead of custom payment glue.
Skip if: Simple SaaS billing pages, non-agent products, or regulated fintech launches that need full compliance review beyond an SDK experiment.
What do I get? / Deliverables
Your agent gains MnemoPay-backed memory, wallet, and payment tools with scored trust and auditable identity hooks from one MCP install.
- Agent-accessible MnemoPay wallet and memory operations via MCP
- Local persistence directory for ledger and memory when configured
- Hooks for Agent FICO and Merkle-audited identity flows per SDK capabilities
Recommended MCP Servers
Journey fit
Wallet, memory, and agent identity are Build-time agent-tooling primitives—not a Launch SEO task—when you compose payable agents. Agent-tooling is where MCP servers extend what agents can do; MnemoPay SDK targets memory plus payments plus audit in one stdio package.
How it compares
MCP agent wallet and memory rails, not a Stripe dashboard skill or passive documentation generator.
Common Questions / FAQ
Who is com.mnemopay/sdk for?
Solo developers building AI agents that need persistent memory, wallets, payments, and trust scoring via MnemoPay’s MCP entrypoint.
When should I use com.mnemopay/sdk?
Use it during Build agent-tooling when your agent must hold state, execute payments, and expose auditable identity before you ship agent commerce features.
How do I add com.mnemopay/sdk to my agent?
Export MNEMOPAY_API_KEY (and optional MNEMOPAY_PERSIST_DIR), register stdio MCP with npx @mnemopay/sdk mnemopay-mcp, then reload tools in Claude Code or Cursor.