SnapEX Pay
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SNAPEX_API_KEY | No | Merchant API key starting with smk_. Optional: create_account makes one. | |
| SNAPEX_NO_SAVE | No | Set to 1 to not save credentials to disk. | |
| SNAPEX_BASE_URL | No | API base URL. | https://pay.snapex.pro |
| SNAPEX_CREDENTIALS_FILE | No | Where a key from create_account is saved (mode 600). | ~/.config/snapex-pay/credentials.json |
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 | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_accountA | Opens a new SnapEX Pay merchant account for you and returns a merchant API key with every scope (receive, pay out, convert, webhooks). No captcha, no email confirmation, no person needed. Call it once, only when you have no key yet (other tools answer "unauthorized"). On this MCP connection the new key is used automatically from now on; save api_key (shown once) and use it next time as "Authorization: Bearer <api_key>", or connect to mcp_personal_url. login and password (generated when omitted) let a person open the cabinet at cabinet_url. The account starts with a zero balance; money arrives only from payments to your invoices or addresses. Limited to a few accounts per IP per hour. |
| get_accountA | Returns the account behind the API key in use: login, the key prefix and scopes, cabinet_url for a person and mcp_personal_url (a secret MCP URL with this key built in, for clients that cannot send headers). Use it to check you are connected to the right account. |
| list_assetsA | Lists the coins and networks SnapEX Pay works with now: asset_id (the code other tools take), symbol, network, decimals, price_usd, payment (can be received), payout (can be paid out) and payout_min_usd. No key needed. Call it before creating invoices, payouts or conversions to pick valid asset codes. |
| get_fiat_ratesA | Fiat → USD rates used for invoices priced in another currency (create_invoice with price_amount + price_currency). Without currency returns all rates; with currency (ISO 4217, e.g. "EUR") returns one or not_found. No key needed. |
| get_feesA | What SnapEX Pay charges, no key needed. pricing: invoice_fee_percent (of a paid invoice; fee_on=customer puts it on the payer), invoice_min_usd/invoice_max_usd, static_address_fee_percent, payout_service_fee_percent; the network fee of a payout depends on the coin and is quoted by preview_payout, the smallest payout per coin is payout_min_usd in list_assets. data: recent cached route fee quotes (often empty; filter by route and asset codes). |
| list_static_address_networksA | Lists the coins/networks for which you can get a permanent deposit address (create_static_address): asset code (e.g. "usdt.trc20", "usdc.polygon", "btc"), symbol, network, available, and how a deposit is credited (always in USDT). No key needed. |
| get_balancesA | Returns the account balance. Every payment is credited in USDT (TRC20 accounting), whatever coin the payer used: available (can be paid out or converted now) and held (reserved by payouts in progress), each as a decimal string and in atomic units. |
| list_transactionsA | Ledger of the balance, newest first: every credit and debit (payments, payouts, fees, conversions) with amount, direction and time. Paginated with cursor. |
| create_invoiceA | Creates an invoice and returns pay_url — a hosted payment page where the payer picks a coin and pays; the amount is credited to your balance in USDT minus the fee. Give amount_usd, or price_amount + price_currency (converted at get_fiat_rates). Use environment "test" to try the whole flow without real money: a test invoice turns paid by itself about 10 seconds after a coin is selected (on its page or with select_invoice_payment_method); the real balance does not change. Then follow the status with get_invoice or webhooks (invoice.paid). To get a deposit address right away instead of a page, pass asset_id (and lock_method true), or call select_invoice_payment_method. |
| get_invoiceA | Returns one invoice with its status (open, awaiting, underpaid, paid, partially_paid, expired), pay_url, credit_usd, the selected coin and the payment attempts. Poll it every 15–30 s while the payer pays, or use webhooks. |
| list_invoicesA | Invoices of the account, newest first, optionally filtered by status and environment. Paginated with cursor. |
| get_invoice_payment_methodsA | Lists the coins and networks the payer can use for this invoice, with the amount to send in each. |
| select_invoice_payment_methodA | Chooses the coin for an invoice and returns the deposit address and exact amount to send (in the invoice payment attempt) — use it when you pass the address to the payer yourself instead of pay_url. |
| preview_paymentA | Low-level alternative to invoices: quotes a payment of an exact amount in one coin and how much USDT you will be credited. Returns credit_lock_id for create_payment (valid until expires_at). Most agents should use create_invoice instead. |
| create_paymentA | Creates a payment from a preview_payment quote and returns deposit_address (and deposit_memo when the network needs one) and the exact amount the payer must send before expires_at. |
| get_paymentA | One payment (from an invoice, a static address or create_payment): status (e.g. awaiting_deposit, detected, confirmed, expired), amounts expected/received/credited, deposit address. |
| list_paymentsA | Payments of the account, newest first, optionally filtered by status. Paginated with cursor. |
| create_static_addressA | Gets (or creates) a permanent deposit address for a coin/network and optional customer_ref: the same address comes back for the same customer_ref. Every transfer to it is credited to your balance in USDT as a separate payment — good for top-ups. Networks: list_static_address_networks. |
| list_static_addressesB | Permanent deposit addresses of the account, optionally for one customer_ref. Paginated with cursor. |
| list_static_address_depositsA | Transfers received on one permanent address with their status and credited USDT. Paginated with cursor. |
| preview_payoutA | Step 1 of sending money. Quotes a payout of amount USDT from your balance to an address in any coin with payout=true in list_assets: returns preview_id, to_amount (what the recipient gets), fee and expires_at. Nothing is sent yet and the quote is free; check the address and amounts, then call create_payout with preview_id before expires_at. An invalid address answers invalid_address. |
| create_payoutA | Step 2 of sending money: executes a preview_payout quote and sends real funds from your balance — irreversible once sent. destination_network and destination_address must be the ones of the preview. idempotency_key is required: reuse the same key when retrying after a timeout so the payout is never sent twice. Then follow get_payout (status until completed or failed, transaction_url) or webhooks payout.completed / payout.failed. |
| get_payoutA | One payout: status (e.g. processing, completed, failed; manual_review — SnapEX staff checks it), amounts, fee, transaction_hash and transaction_url in the destination network's explorer. |
| list_payoutsA | Payouts of the account, newest first, optionally filtered by status. Paginated with cursor. |
| preview_conversionA | Step 1 of converting assets held on the account into USDT. The balance is kept in USDT (every payment is credited in USDT), so this matters only for an account that still holds another asset; to exchange USDT into another coin, send a payout in that coin (preview_payout, e.g. to your own address). mode "single": convert amount of from_asset_id (to USDT, or to to_asset_id); mode "all_to_usdt": convert every non-USDT holding to USDT. Returns preview_id with the amounts and expires_at; nothing moves yet. Then create_conversion. |
| create_conversionA | Step 2: executes a preview_conversion quote before its expires_at; the balance changes at once. A preview runs once — calling again returns the same conversion. |
| get_conversionC | One conversion with its status and amounts. |
| list_conversionsB | Conversions of the account, newest first. Paginated with cursor. |
| list_webhooksB | Webhook endpoints of the account: endpoint_id, url, events, status. |
| create_webhookA | Registers a public HTTPS URL that receives a POST for each chosen event (JSON {id, type, created_at, data}). Returns secret (shown once): verify each delivery with HMAC-SHA256 of "." against the Webhook-Signature header ("v1="). Deliveries are at-least-once — dedupe by Webhook-Id. Up to 10 endpoints. |
| update_webhookA | Replaces the url and events of an endpoint, or disables/enables it (status). |
| rotate_webhook_secretA | Issues a new signing secret for an endpoint (shown once); the old one stops working at once. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| accept_crypto_payment | Create an invoice, give the payment link and wait until it is paid. |
| send_crypto_payout | Quote, check and send a payout from the balance. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| quickstart | Account, receiving, payouts, conversions, test mode and limits in one page. |
| webhooks | Event list, payload and how to verify Webhook-Signature. |
TDQS
Scored across 32 tools
The surface is segmented by resource (invoices, payments, payouts, conversions, static addresses, webhooks) and the preview_/create_ step pairs are explicitly labelled, so most tools are separable. The main friction is between invoices, payments and static-address deposits — three ways money arrives — though descriptions steer agents (e.g. 'most agents should use create_invoice instead' of preview_payment, and create_conversion is only for non-USDT holdings). get_payment being the read side for invoice, static address and standalone payments adds mild conceptual overlap but is coherently explained.
Every tool is snake_case with a verb-first prefix (get_, list_, create_, preview_, select_, update_, rotate_), and the prefix reliably signals read vs. write vs. quote. Sub-resources use consistent compound nouns (static_address, invoice_payment_method, webhook_secret) without abbreviations or style drift.
32 tools is heavy for a single MCP connection, but the server genuinely spans seven sub-domains (account, assets/rates, balances/ledger, invoices, payments, static addresses, payouts, conversions, webhooks), each with justified list/get/create operations. The preview→create pairing inflates the count, yet each pair earns its place as a safety step. Still, the bulk will make discovery and selection harder than a tighter 15–20 tool surface would.
Coverage is strong: account lifecycle, asset discovery, fees, balances, ledger, full invoice/payment/payout/conversion lifecycles, static addresses with deposit listing, and webhook management including secret rotation. Gaps are minor but real — no cancel/void invoice, no delete_webhook (only disable via update), and no explicit refund path. Agents can work around these, but cancellation of an open invoice appears absent.