Other · Local MCP server
Peer Cash
MCP server for preparing and tracking Peer Cash Base USDC cash-outs.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.zkp2p/peer-cash- Version
- 0.1.2
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-08-14
- Updated
- 2026-08-14
- Publisher
- zkp2p (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/zkp2p) · how
- Repository
- github.com/zkp2p/peer-cash-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | peer-cash-mcp | 0.1.2 | stdio |
How to connect Peer Cash
Peer Cash runs locally from a Node.js package published to the npm registry: peer-cash-mcp version 0.1.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y peer-cash-mcp@0.1.2. It reads these environment variables: PEER_CASH_ENVIRONMENT, PEER_CASH_RPC_URL (secret), PEER_CASH_API_KEY (secret), PEER_CASH_REFERRAL_CODE and PEER_CASH_REFERRER; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"peer-cash": {
"command": "npx",
"args": [
"-y",
"peer-cash-mcp@0.1.2"
],
"env": {
"PEER_CASH_ENVIRONMENT": "<value>",
"PEER_CASH_RPC_URL": "<secret>",
"PEER_CASH_API_KEY": "<secret>",
"PEER_CASH_REFERRAL_CODE": "<value>",
"PEER_CASH_REFERRER": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from zkp2p (GitHub)
| Server | Runs |
|---|---|
| PeerRead Peer protocol, market, checkout, and Peer Cash data through one MCP server. | Remote · HTTPLive check: ✓ handshake |
More other servers
| Server | Runs |
|---|---|
| PebbleHost the tools your AI builds - small internal tools in isolated microVMs, live for your team. | Remote · HTTPLive check: sign-in required |
| PedagradeCheck lessons and courses against their learning objectives, with each fix written. | Remote · HTTPLive check: sign-in required |
| PediBotChildren's health from published guidelines: doses, vaccines, growth charts, warning signs. | Remote · HTTPLive check: ✓ handshake |
| Peek - URL metadata & MarkdownLink-preview metadata and clean page-to-Markdown for any public URL. No install. | Remote · HTTPLive check: ✗ no handshake |
| Peer CommonsAgent reliability experiments and persistent discussions, shared context and subscriptions. | Remote · HTTPLive check: sign-in required |
| Peering MCPWho peers with whom, where they meet, and who an address range belongs to. PeeringDB and RDAP. | Local · stdio |
| Peerkith MCPCheck an agent work row, post one, and preflight a no-spend cap before any spend/send. | Local · stdio |
| PegelGerman and Swiss river gauges, groundwater and flood levels from ten official sources. | Remote · HTTPLive check: ✓ handshake |