Skip to main content
Glama
yanboishere

Infini Payment MCP Server

by yanboishere
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
INFINI_ENVNoThe Infini environment (sandbox or production)sandbox
INFINI_API_KEYYesYour Infini API key
INFINI_SECRET_KEYYesYour Infini secret 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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
create_payment_orderB
Create a new payment order in Infini.

Args:
    request_id: Unique request ID (UUID recommended)
    amount: Order amount (e.g., "100.00")
    client_reference: Client reference string
    order_desc: Order description
    merchant_alias: Custom merchant alias
    expires_in: Time to live in seconds (0 for default)
    success_url: Success redirect URL
    failure_url: Failure redirect URL
get_payment_orderC
Get payment order details by order ID.

Args:
    order_id: The order ID to query
list_payment_ordersC
List payment orders with optional filters.

Args:
    currency: Filter by currency (USDC/USDT)
    status: Filter by order status
    page: Page number (1 to n)
    page_size: Page size (default 10)
reissue_order_tokenC
Reissue checkout URL token for an existing order.

Args:
    order_id: The order ID to reissue token for
get_supported_currenciesB

Get list of all supported cryptocurrencies for creating orders.

withdraw_fundsB
Withdraw funds to external wallet.

Args:
    chain: Blockchain network name
    token_type: Token identifier
    amount: Amount to withdraw
    wallet_address: Destination wallet address
    note: Optional note
verify_webhook_signatureB
Verify webhook signature from Infini.

Args:
    body: Raw webhook body string
    signature: Signature from webhook header
    timestamp: Timestamp from webhook header
    webhook_secret: Webhook secret (uses INFINI_SECRET_KEY if not provided)

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.5/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: create_payment_order for creation, get_payment_order for retrieval, list_payment_orders for listing, reissue_order_token for token renewal, verify_webhook_signature for security, get_supported_currencies for currency info, and withdraw_funds for withdrawals. The descriptions reinforce these unique functions, eliminating any ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case, such as create_payment_order, get_payment_order, list_payment_orders, and verify_webhook_signature. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions.

Tool Count5/5

With 7 tools, the server is well-scoped for payment processing, covering core operations like order management, currency support, webhook verification, and fund withdrawals. Each tool serves a specific, necessary function without being excessive or insufficient for the domain.

Completeness4/5

The tool set provides strong coverage for payment order lifecycle (create, get, list, reissue) and essential utilities (currency info, webhook verification, withdrawals). A minor gap exists in lacking an update or cancel operation for orders, but agents can work around this by creating new orders or using existing tools effectively.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources