vnpay-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VNPAY_TMN_CODE | Yes | Terminal code from VNPay | |
| VNPAY_PRODUCTION | No | Set to 'true' for production | |
| VNPAY_HASH_SECRET | Yes | Hash secret for HMAC-SHA512 signing |
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_urlC | Generate a VNPay payment URL. |
| query_transactionC | Query transaction status. |
| refundC | Refund a VNPay transaction. |
| get_bank_listA | Get list of supported banks. |
| create_tokenB | Create a card token for recurring payments. |
| pay_with_tokenC | Pay using a stored card token. |
| query_tokenB | Query card token information. |
| verify_ipnA | Verify a VNPay IPN callback signature. |
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 8 tools
Each tool targets a distinct operation: payment URL creation, token creation, bank list retrieval, token payment, token query, transaction query, refund, and IPN verification. No overlapping purposes; an agent can clearly differentiate them.
All tool names follow a consistent verb_noun pattern using lowercase with underscores (e.g., create_payment_url, get_bank_list, verify_ipn). The only exception is 'refund', which is a single-word verb but still aligns with the verb-first convention.
With 8 tools, the server is well-scoped for a VNPay integration. It covers essential payment operations without being overly large or too minimal, making it manageable for agents.
The tool set covers the core payment lifecycle: creating payments, recurring payments via tokens, querying transactions, refunds, and IPN verification. Minor gaps like token update/delete or transaction cancellation are absent but likely not needed for the domain.