Peer Cash MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PEER_CASH_API_KEY | No | Curator API key when the selected environment requires one. | |
| PEER_CASH_RPC_URL | No | Custom Base RPC URL for reads and receipt finalization. | |
| PEER_CASH_REFERRER | No | Analytics-only ERC-8021 attribution code. | |
| PEER_CASH_ENVIRONMENT | No | The environment to use: production, preproduction, or staging. Defaults to production. | production |
| PEER_CASH_REFERRAL_CODE | No | Six-character Peer integration referral code. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| peer_cash_capabilitiesA | Return the live Base USDC destination, payout platforms, fiat currencies, payee hints, amount bounds, and pricing model. Call this before naming a rail or currency. |
| peer_cash_estimateA | Estimate fiat received for Base USDC at the live Chainlink oracle rate. This is not a locked quote; the binding rate resolves when a buyer fills. |
| peer_cash_prepareA | Prepare unsigned Base USDC approval and createDeposit transactions. The MCP server never accepts a private key or submits a transaction. Show the plan and obtain explicit approval before host-side signing. |
| peer_cash_finalizeA | Read a confirmed Base createDeposit receipt and resolve the resumable Peer deposit id. Call only after the host confirms the createDeposit transaction returned by peer_cash_prepare. |
| peer_cash_prepare_access_policyA | Prepare the unsigned verified-buyer access-policy transaction required for Venmo, Cash App, or PayPal orders. Use only after finalization when peer_cash_prepare returned accessPolicyRequired=true. |
| peer_cash_orderA | Return one order state, amounts, fills, and next actions from its deposit id. Brief ORDER_NOT_FOUND responses after finalization may be indexer lag; retry this read, never the deposit transaction. |
| peer_cash_ordersA | List orders owned by a maker wallet, optionally limited to orders that still need attention. |
| peer_cash_prepare_withdrawA | Prepare unsigned transactions to withdraw unmatched funds. Omit amount to close the order; pass a Base USDC base-unit amount for a partial withdrawal. |
| peer_cash_prepare_top_upA | Prepare unsigned approval and addFunds transactions to add Base USDC to a live order. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.