Peer Cash MCP
Official# Moved to peer-cli
Peer Cash MCP is now part of the canonical
[`zkp2p/peer-cli`](https://github.com/zkp2p/peer-cli) runtime. This repository is
archived and receives no fixes or releases.
Use the custody-separated Cash profile:
```bash
npx -y github:zkp2p/peer-cli#v0.1.0 mcp --profile cash
```
The tool names and custody boundary are preserved: `peer_cash_*` tools prepare
unsigned transaction plans and never accept private keys, sign, or broadcast.
- [Peer Cash agent documentation](https://agents.peer.xyz/docs/reference/peer-cash)
- [Migration and runtime source](https://github.com/zkp2p/peer-cli)
The published `peer-cash-mcp` npm package is historical. Do not start new
integrations on it.
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: capabilities, estimate, prepare deposit, finalize, access policy, order read, list, withdraw, and top-up. The descriptions further clarify boundaries, preventing misselection.
All tools follow a consistent peer_cash_ prefix with snake_case naming. The pattern is uniform—verb or noun forms like prepare, finalize, order—and there is no mixing of conventions.
With 9 tools, the server is well-scoped for its domain. Each tool covers a distinct operation in the payment lifecycle without redundancy, fitting the ideal 3-15 range.
The toolset covers the full workflow: capabilities discovery, rate estimation, deposit preparation, finalization, access policy management, order retrieval/listing, withdrawal, and top-up. No obvious gaps hinder typical use cases.