Skip to main content
Glama
ant-intl

Antom MCP Server

Official
by ant-intl
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CLIENT_IDYesMerchant client ID for identity verification
GATEWAY_URLNoAntom API gateway URLhttps://open-sea-global.alipay.com
ALIPAY_PUBLIC_KEYYesAlipay RSA public key for response verification
PAYMENT_NOTIFY_URLNoPayment result notification callback URL
MERCHANT_PRIVATE_KEYYesMerchant RSA private key for request signing
PAYMENT_REDIRECT_URLNoThe user is redirected to after the payment is completed/

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_sessionA

The tool is used to create a payment session which helps you complete the payment process and eliminate intermediate page redirections throughout the entire payment process.

    Args:
        payment_request_id: The unique ID assigned by a merchant to identify a payment request. Maximum length: 64 characters
        order_amount_currency: The transaction currency that is specified in the contract. A 3-letter currency code that follows the ISO 4217 standard.Maximum length: 3 characters
        order_amount_value: The amount to charge as a positive integer in the smallest currency unit. (That is, 100 cents to charge $1.00, or 100 to charge JPY 100, a 0-decimal currency).Value range: 1 - unlimited
        order_description: Summary description of the order, which is used for user consumption records display or other further actions.Maximum length: 256 characters
query_payment_detailA

The tool is used to inquire about the transaction status and other information about a previously submitted payment request.

    Args:
        payment_request_id: The unique ID that is assigned by a merchant to identify a payment request.Maximum length: 64 characters
cancel_paymentA

The tool is used to cancel the payment if the payment result is not returned after a long time. The cancellation cannot be performed if being out of the cancellable period specified in the contract.

    Args:
        payment_request_id: The unique ID that is assigned by a merchant to identify a payment request.Maximum length: 64 characters
create_refundA

The tool is used to initiate a refund against a successful payment. The refund can be full or partial. A transaction can have multiple refunds as long as the total refund amount is less than or equal to the original transaction amount. If the refund request is out of the refund window determined in the contract, the refund request will be declined.

    Args:
        refund_request_id: The unique ID assigned by the merchant to identify a refund request.Maximum length: 64 characters
        payment_id: The unique ID assigned by Antom for the original payment to be refunded.Maximum length: 64 characters
        refund_amount_currency: The currency used for the corresponding payment of the refund. The value is a 3-letter currency code that follows the ISO 4217 standard.
        refund_amount_value: The amount to charge as a positive integer in the smallest currency unit. (That is, 100 cents to charge $1.00, or 100 to charge JPY 100, a 0-decimal currency).Value range: 1 - unlimited
query_refund_detailB

The tool is used to inquire about the refund status of a previously submitted refund request.

    Args:
        refund_request_id: The unique ID assigned by the merchant to identify a refund request.Maximum length: 64 characters

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

A4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool handles a distinct payment operation: creating a payment session, canceling a pending payment, creating a refund, querying payment details, and querying refund details. There is no overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., cancel_payment, create_payment_session, create_refund). This provides a predictable and clear naming convention.

Tool Count5/5

With 5 tools, the server is well-scoped for payment processing. The count is neither too few nor too many, covering core payment lifecycle operations without unnecessary clutter.

Completeness5/5

The tool set covers the essential payment operations: initiation, cancellation, refund, and status queries for both payments and refunds. No obvious gaps exist for a typical payment processing workflow.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources