xiatian-pay-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XIATIAN_API_KEY | No | API key for the hosted platform service (托管平台API密钥，可选) | |
| XIATIAN_WX_APPID | No | WeChat application ID (微信应用AppID) | |
| XIATIAN_WX_MCHID | No | WeChat Pay merchant ID (微信支付商户号) | |
| XIATIAN_ALIPAY_APPID | No | Alipay application ID (支付宝AppID) | |
| XIATIAN_PLATFORM_URL | No | Base URL of the hosted platform service (托管平台URL) | |
| XIATIAN_WX_APIV3_KEY | No | WeChat Pay APIv3 key (微信支付APIv3密钥) | |
| XIATIAN_WX_CERT_SERIAL | No | WeChat Pay API certificate serial number (微信支付API证书序列号) | |
| XIATIAN_WX_PRIVATE_KEY_PATH | No | File path to the WeChat Pay private key (微信支付商户私钥文件路径) | |
| XIATIAN_WX_PLATFORM_CERT_PATH | No | File path to the WeChat Pay platform certificate (微信支付平台证书文件路径) | |
| XIATIAN_ALIPAY_PUBLIC_KEY_PATH | No | File path to the Alipay public key (支付宝公钥文件路径) | |
| XIATIAN_ALIPAY_PRIVATE_KEY_PATH | No | File path to the Alipay private key (支付宝应用私钥文件路径) |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wechat_build_authorizationA | 微信支付V3：离线构造 Authorization 请求头（RSA-SHA256 签名），不发起网络请求。用于自建 HTTP 调用。 |
| wechat_create_native_orderA | 微信支付V3 Native 扫码下单：execute=false 仅返回已签名的请求规格；true 真实调用微信 API 返回 code_url（二维码内容）。 |
| wechat_create_jsapi_orderB | 微信支付V3 JSAPI 下单（微信内/小程序）：返回 prepay_id 与 wx.invoke("getBrandWCPayRequest") 调起参数。 |
| wechat_verify_callbackA | 微信支付V3 异步通知验签：用微信支付平台证书校验 Wechatpay-Signature。返回 {valid:boolean}。 |
| wechat_decrypt_callbackB | 微信支付V3 回调 resource 解密：AES-256-GCM，密钥为 APIv3。返回交易明文 JSON。 |
| alipay_sign_paramsA | 支付宝：对业务参数做 RSA2 签名，返回带 sign 的完整参数（可直接 POST 到网关）。 |
| alipay_precreateA | 支付宝当面付预下单：execute=false 仅返回已签名请求规格；true 真实调用返回 qr_code 二维码链接。 |
| alipay_build_pay_urlA | 支付宝生成支付跳转链接（离线，不发起请求）：product=page 电脑网站 alipay.trade.page.pay；wap 手机网站 alipay.trade.wap.pay。 |
| alipay_verify_notifyA | 支付宝异步通知验签：传入全部回调参数（含 sign），用支付宝公钥校验。返回 {valid:boolean}。 |
| platform_create_orderA | 夏天pay托管平台：免商户凭证建单（需要环境变量 XIATIAN_PLATFORM_URL + XIATIAN_API_KEY）。返回订单号与收银台链接。 |
| platform_query_orderA | 夏天pay托管平台：按订单号查询实时支付状态（pending/success/failed/expired/refunded）。 |
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 11 tools
Provider prefixes (wechat_, alipay_, platform_) cleanly separate the three domains, and each tool has a distinct action. Minor ambiguity exists because wechat_create_native_order and alipay_precreate both have an execute=false mode that returns signed request specs, overlapping somewhat with the dedicated signing utilities.
Names generally follow a provider_verb_noun snake_case pattern, such as platform_create_order, wechat_decrypt_callback, and alipay_verify_notify. The pattern is slightly weakened by alipay_precreate (verb only) and the mix of verbs like build, sign, create, and precreate, but the names remain readable and predictable.
11 tools is well-scoped for a multi-provider payment server, covering WeChat Pay, Alipay, and the hosted platform with no obvious redundancy. Each tool earns its place and the count supports practical agent workflows without overwhelming selection.
The server covers order creation, querying, signing, and callback verification well, but lacks refund or close/cancel operations for both WeChat Pay and Alipay. This leaves a notable gap in the common payment lifecycle, forcing agents to handle refunds outside the MCP server.