lfwin-payment-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAYMENT_API_KEY | Yes | Your API key for the payment service | |
| PAYMENT_SIGN_KEY | Yes | Your sign key for the payment service |
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 |
|---|---|
| create_payment_orderA | Create a cashier payment order. Amount is in yuan and merchant_order_no is the merchant's own unique order number. After success, display pay_qrcode_markdown, the returned image content block, pay_qrcode_image data URL, or pay_qrcode_base64 with pay_qrcode_mime_type as the QR code. If QR rendering fails, show pay_url/qrcode as the fallback payment link. Save order_no/query_order_no when present. If order_no is null, save merchant_order_no plus order_time and use both for query_payment_order polling. |
| query_payment_orderA | Query payment order status. Prefer platform order_no/orderid when create_payment_order returned it. If order_no is null, pass merchant_order_no plus order_time returned by create_payment_order. Pass either order_no or the merchant pair. |
| refund_payment_orderA | Create a refund request by platform order_no/orderid. mch_refund_no is the merchant refund number and must be unique per refund. Successful submission means accepted/processing, not final refund success; call query_refund_status to confirm. |
| query_refund_statusA | Query refund status by platform order_no/orderid. Pass mch_refund_no when available to locate a specific partial refund. Only REFUNDED is final success; REFUNDING/PROCESSING means query again later. |
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 targets a distinct operation: creating an order, querying an order, creating a refund, and querying refund status. No overlap in purpose.
All tool names follow a consistent verb_noun pattern: create_payment_order, query_payment_order, query_refund_status, refund_payment_order.
4 tools cover the essential payment operations well. Slightly minimal but appropriate for a focused payment MCP.
Core create/query/refund operations are present, but missing common operations like order cancellation or list orders, which may cause some workflow gaps.