@chainpayto/mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHAINPAY_API_KEY | Yes | 商户 API Key | |
| CHAINPAY_API_URL | No | API 地址（私有部署时修改） | https://api.chainpay.to |
| CHAINPAY_API_SECRET | Yes | API Secret 明文（不是哈希） |
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 |
|---|---|
| chainpay_get_supported_chainsA | Get all blockchain networks and tokens supported by ChainPay, including fee rates and minimum amounts. Call this before creating orders to get valid chain/token values. |
| chainpay_create_orderA | Create a new cryptocurrency payment order. Returns a payment URL and wallet address for the payer. Supported chains: TRON / BSC / POLYGON. Call chainpay_get_supported_chains first to check minimum amounts. |
| chainpay_get_orderA | Get details and current status of a specific payment order. |
| chainpay_list_ordersA | List payment orders with pagination and optional status filter. |
| chainpay_get_balanceA | Get the merchant account balance including total balance, frozen amount, and available balance. |
| chainpay_create_withdrawalA | Submit a withdrawal request to transfer funds to the merchant's bound withdrawal address. Requires a withdrawal address to be configured in the merchant dashboard. May require admin approval. |
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 6 tools
All tools have unique purposes with no overlap. Creating orders, creating withdrawals, checking balance, retrieving orders, listing orders, and fetching supported chains are all distinct operations.
All tools follow a consistent 'chainpay_verb_noun' pattern (e.g., create_order, get_balance, list_orders), with uniform snake_case naming.
Six tools is well-scoped for a cryptocurrency payment server, covering order management, withdrawal, balance, and chain info without being excessive.
Covers core order lifecycle (create, get, list) and balance/chain info, but lacks a tool to get withdrawal status or list withdrawals, which is a minor gap.