XPayr MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XPAYR_API_KEY | Yes | Your XPayr secret API key used to authenticate with the XPayr MCP server. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| xpayr_health_checkA | Check XPayr Gateway API v1 operational health, version, and server timestamp (public endpoint, no API key required). |
| xpayr_create_payment_sessionC | Create a non-custodial crypto payment session supporting Dual Checkout (Web3 1-Click Pay & Direct Transfer / QR from Binance/Bybit/OKX with on-chain explorer verification), multi-chain agnostic links, 1-year reusable payment links, and automated HTML invoice email delivery. |
| xpayr_get_payment_sessionA | Retrieve full details, metadata, settlement split amounts, checkout mode, and on-chain transaction hash for a specific XPayr payment session. |
| xpayr_list_payment_sessionsB | List merchant crypto payment sessions with optional filtering by status (pending, completed, expired, failed), currency, network, and pagination. |
| xpayr_get_public_payment_statusA | Poll real-time public checkout status, on-chain tx_hash, sender wallet address, block confirmations, and paid_at timestamp for any session (public endpoint, no API key required). |
| xpayr_apply_payment_couponA | Validate and apply a merchant discount coupon code to an active pending payment session and recalculate the effective crypto price. |
| xpayr_get_merchant_profileA | Retrieve authenticated merchant profile, business name, primary settlement wallet address, commission rate in basis points (50 bps = 0.5%), active API keys, and livemode status. |
| xpayr_get_merchant_balanceB | Query confirmed non-custodial settlement volume, transaction counts, total merchant received amounts, and platform fees grouped by currency and blockchain network. |
| xpayr_get_supported_networksA | List all active EVM, TRON, Solana, and Arc Mainnet/Testnet blockchain networks, chain IDs, RPC endpoints, smart-contract splitters, and supported tokens enabled for the current API key mode. |
| xpayr_get_webhook_configA | Inspect the merchant webhook callback URL, masked HMAC-SHA256 signing secret, and subscribed payment lifecycle events (payment.pending, payment.completed, payment.failed, payment.expired). |
| xpayr_set_webhook_endpointB | Configure or update the merchant HTTPS webhook receiver URL and generate a fresh 32-byte HMAC-SHA256 signing secret. |
| xpayr_send_test_webhookA | Dispatch a signed test.webhook event with HMAC-SHA256 headers to the configured merchant webhook URL to verify signature validation and delivery. |
| xpayr_create_ai_agentB | Provision a new merchant-managed AI commerce agent identity with scoped credentials and programmable spending guardrails. |
| xpayr_list_ai_agentsA | List all AI commerce agents managed by the merchant along with their status, assigned wallets, and spending policies. |
| xpayr_update_ai_agent_policyC | Upsert spending policy rules for an AI commerce agent, including maximum per-transaction USD amount, daily budget cap, auto-approve threshold, and allowed blockchain networks/tokens. |
| xpayr_submit_agent_payment_intentB | Submit an autonomous AI agent payment intent evaluated in real time against merchant spending policy guardrails (returns approved, pending_approval, or rejected). |
| xpayr_list_agent_payment_intentsC | List AI agent payment intents, policy evaluation decisions, and audit trail records for the merchant. |
| xpayr_bridge_agent_intent_to_checkoutB | Bridge an approved AI agent payment intent into a live executable XPayr payment session with hosted checkout URL and on-chain verification. |
| xpayr_approve_agent_intentB | Approve a pending AI agent payment intent from the merchant human-in-the-loop approval queue and optionally bridge it to a checkout session. |
| xpayr_reject_agent_intentA | Reject a pending AI agent payment intent in the merchant approval queue with an audit reason. |
| xpayr_calculate_gateway_fee_and_splitA | Deterministically calculate XPayr flat 0.5% (50 bps) gateway fee split, net merchant wallet settlement, exchange withdrawal underpayment tolerance (1%, max $0.50), and cost savings compared to BitPay (1%), Coinbase Commerce (1%), NOWPayments (0.5%-1%), and Stripe (2.9% + $0.30). Works offline without API keys. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_multichain_crypto_invoice | Create a universal multi-chain crypto payment link with Dual Checkout (Web3 + Direct Exchange QR) and optional HTML email invoice push. |
| autonomous_agent_payment_flow | Submit an AI agent payment intent, evaluate merchant spending policy guardrails, and bridge approved intents to an XPayr checkout session. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| XPayr Non-Custodial Crypto Gateway Capabilities & Supported Networks | Overview of XPayr Dual Checkout (Web3 1-Click + Direct QR), Multi-Chain Links, 0.5% flat fee model, supported EVM/TRON/Solana/Arc networks, and official documentation URLs. |
TDQS
Scored across 21 tools
Most tools target a distinct resource+action (sessions, AI agents, intents, webhooks, merchant, networks). The main soft spots are get_payment_session vs get_public_payment_status (both return session status/tx_hash, distinguished only by auth/polling context) and approve_agent_intent's optional 'bridge to checkout' behavior that overlaps with bridge_agent_intent_to_checkout.
All 21 tools use the same xpayr_ prefix plus snake_case verb_noun naming (create_payment_session, list_ai_agents, update_ai_agent_policy, reject_agent_intent). The only deviation is the noun-first xpayr_health_check, which is a trivial and conventional exception.
21 tools is on the heavy side but the server legitimately spans several sub-domains: payment sessions, AI agent commerce, webhooks, merchant account, and fee calculation. Each tool maps to an identifiable operation, though a few (coupon apply, fee calculator) could arguably be folded into broader session tools.
Core lifecycles are well covered: session create/get/list plus coupon and public status, full agent intent flow (submit, list, approve, reject, bridge), and webhook configure/test. Gaps exist around session cancellation/expiry management, coupon admin, and agent deletion/credential revocation, but these are workaround-able for the main payment flow.