pay-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NETWORK | No | Network: mainnet or testnet | mainnet |
| PRIVATE_KEY | Yes | Wallet private key (without 0x prefix) | |
| BASE_RPC_URL | No | Custom RPC endpoint | |
| MAX_GAS_LIMIT | No | Maximum gas limit | 100000 |
| GAS_MULTIPLIER | No | Gas estimate multiplier | 1.1 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pay_balanceA | Check USDC balance on Base. Returns the balance for your wallet or a specified address. |
| pay_sendB | Send USDC payment on Base. Transfers USDC to the specified address. |
| pay_requestA | Generate a payment request. Creates a payment link that others can use to send you USDC. |
| pay_historyA | Get recent USDC transaction history on Base. Shows both sent and received transfers. |
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 4 tools
Each tool has a distinct purpose: balance checking, sending, requesting, and viewing history. There is no overlap or ambiguity between them.
All tools share the 'pay_' prefix and use snake_case, which is consistent. However, 'pay_balance' and 'pay_history' are noun-based while 'pay_send' is verb-based, a minor deviation from a pure verb_noun pattern.
Four tools cover the core functionality of a simple USDC payment server without bloat. The count is well-scoped for the domain.
The toolset covers the essential lifecycle: checking balance, sending payments, requesting payments, and viewing transaction history. No critical operations are missing for a basic payment server.