Skip to main content
Glama
phuocdu

agentpay-vn

by phuocdu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AGENTPAY_API_KEYYesYour AgentPay API key (start with ap_test_ for sandbox or ap_live_ for production). Get one from the admin dashboard or platform operator.
AGENTPAY_BASE_URLNoBase URL for the AgentPay API. Typically the default is fine for hosted version.https://agentpay.servicesai.vn/v1

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_payment_requestA

Create a VietQR payment request.

Args: amount: Amount in VND, minimum 1 000. description: Short description for the payer (e.g. "Order #123 — 2 kg coffee"). ttl_minutes: QR validity window in minutes (5–1 440, default 60). metadata_note: Internal note from the agent (order id, conversation id, etc.) — echoed back in webhook events.

Returns: id, pay_code, QR image URL, and checkout page URL. Send qr_image_url or checkout_url to the payer, then call await_settlement(id) to wait for the money to arrive.

check_paymentA

Check the current status of a payment request.

Returns: One of: pending | settled | underpaid | expired | cancelled, along with the amount received so far. Only treat a payment as complete when status=settled.

await_settlementA

Wait for a payment request to be settled (polls on behalf of the agent).

Polls every 5 seconds until status != pending or the timeout is reached (maximum 600 s). Call this after sending the QR to the payer. If the timeout expires while still pending, ask the user whether to keep waiting or cancel.

Args: payment_request_id: The id returned by create_payment_request. timeout_seconds: How long to wait in seconds (10–600, default 180).

list_recent_paymentsB

List the most recently settled transactions (quick reconciliation).

Args: limit: Number of transactions to return (1–50, default 10).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a distinct and clear purpose: creating a payment request, checking status, awaiting settlement, and listing recent payments. No two tools overlap in functionality, ensuring an agent can easily select the correct one.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (create_payment_request, check_payment, await_settlement, list_recent_payments). The naming is predictable and unambiguous.

Tool Count4/5

Four tools is a reasonable number for a focused payment processing server. While it covers core operations, it is slightly lean; adding a cancel tool might improve completeness, but the count is appropriate.

Completeness4/5

The tool set covers the main lifecycle of a payment request: create, check, await, and list. Missing an explicit cancel/expire function, but the await tool handles timeouts gracefully. Minor gap, but overall sufficient for typical workflows.

Maintenance

ActivityInactive
ResponsivenessResponsive

Resources