SnapEX Pay MCP Server

by snapex Your server? Claim it

answering

SnapEX Pay is answering right now. Last checked 6 min ago. 373 installs a week from npm. It exposes 32 tools. Last commit 4 Nov 2026.

Crypto payments for AI agents: self-serve account, invoices, receiving, payouts, exchange.

Installs per day peak 312 · avg 10

a month agotoday

Uptime history 5 days of history

5 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

353 ms

Response time

average over 24h

373

Installs / week

npm and PyPI

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 3 November 2026. No other catalogue keeps this.

3 Nov a tool changed version

Nothing serious here today

Today is the operative word: we check SnapEX Pay every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add pay --transport http https://pay.snapex.pro/mcp

Settings → Connectors → Add custom connector, then paste this address

https://pay.snapex.pro/mcp

~/.codex/config.toml

[mcp_servers.pay]
url = "https://pay.snapex.pro/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "pay": {
      "url": "https://pay.snapex.pro/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "pay": {
      "type": "http",
      "url": "https://pay.snapex.pro/mcp"
    }
  }
}

Available tools 32

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

static

create_static_address

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_address_deposits

Transfers received on one permanent address with their status and credited USDT. Paginated with cursor.

list_static_address_networks

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.

list_static_addresses

Permanent deposit addresses of the account, optionally for one customer_ref. Paginated with cursor.

invoice

create_invoice

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_invoice

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.

get_invoice_payment_methods

Lists the coins and networks the payer can use for this invoice, with the amount to send in each.

preview

preview_conversion

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.

preview_payment

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.

preview_payout

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.

account

create_account

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_account

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.

conversion

create_conversion

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_conversion

One conversion with its status and amounts.

payment

create_payment

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_payment

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.

payout

create_payout

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_payout

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.

webhook

create_webhook

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 "<Webhook-Timestamp>.<raw body>" against the Webhook-Signature header ("v1=<hex>"). Deliveries are at-least-once — dedupe by Webhook-Id. Up to 10 endpoints.

update_webhook

Replaces the url and events of an endpoint, or disables/enables it (status).

assets

list_assets

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.

balances

get_balances

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.

conversions

list_conversions

Conversions of the account, newest first. Paginated with cursor.

fees

get_fees

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).

fiat

get_fiat_rates

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.

invoices

list_invoices

Invoices of the account, newest first, optionally filtered by status and environment. Paginated with cursor.

payments

list_payments

Payments of the account, newest first, optionally filtered by status. Paginated with cursor.

payouts

list_payouts

Payouts of the account, newest first, optionally filtered by status. Paginated with cursor.

rotate

rotate_webhook_secret

Issues a new signing secret for an endpoint (shown once); the old one stops working at once.

select

select_invoice_payment_method

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.

transactions

list_transactions

Ledger of the balance, newest first: every credit and debit (payments, payouts, fees, conversions) with amount, direction and time. Paginated with cursor.

webhooks

list_webhooks

Webhook endpoints of the account: endpoint_id, url, events, status.

Endpoints

URL	Transport	State	Latency	Checked
https://pay.snapex.pro/mcp	streamable-http	answering	316 ms	6 min ago

Alternatives to SnapEX Pay

same job, measured the same way

Poplin

by poplinmoney

Estimate payments abroad: fees, exchange rates, receiving accounts and payout coverage

11 tools answering

PayPing

by sepehr071

PayPing merchant account for agents: balance, sales, invoices; create invoices and payment links.

506 installs/wk local only

AgentBank

by useagentbank

Crypto banking services for AI agents: collect money and pay bank accounts in local currency.

answering

Xero

by wyre-ai

MCP server for Xero accounting — contacts, invoices, payments, accounts, and financial reports.

local only

Xero

by wyre-technology

MCP server for Xero accounting — contacts, invoices, payments, accounts, and financial reports.

local only

MCP Ebanx

by codespar

MCP server for EBANX — cross-border payments, payouts, exchange rates

180 installs/wk local only

MCP Xero

by codespar

MCP server for Xero — global cloud accounting: contacts, invoices, payments, items, reports

55 installs/wk local only

Alternative Payments

by wyre-technology

MCP server for Alternative Payments — customers, invoices, payment requests, payouts, webhooks.

local only

SnapEX Pay — questions

Answers built from our own checks of this server.

What can SnapEX Pay do?

It exposes 32 tools, read directly from the server on our last check. Among them: create_account, create_conversion, create_invoice, create_payment, create_payout, create_static_address and 26 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is SnapEX Pay mostly used for?

Its tools cluster around static, invoice and preview. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is SnapEX Pay working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 353 ms. The bar chart above shows every period we have measured.

How do I connect SnapEX Pay?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does SnapEX Pay need an API key?

No. SnapEX Pay completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 32 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is SnapEX Pay?

It answers our handshake in 353 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use SnapEX Pay?

The npm package snapex-pay-mcp was installed 373 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is SnapEX Pay open source?

The code is open source: it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at pay.snapex.pro, which runs on its operator's own terms.