# SnapEX Pay [Verified] [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/snapexpay/snapex-pay-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 373  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/snapex-pay

## Description
SnapEX Pay MCP server lets an AI agent work with crypto payments without a person in the loop. The agent connects to https://pay.snapex.pro/mcp, opens a SnapEX Pay merchant account by itself (no captcha, no email) and gets an API key. Then it can create invoices with hosted payment pages, receive crypto on permanent deposit addresses, keep a USDT balance, send payouts in many coins and networks, and manage webhooks. Test mode runs the whole flow without real money. Payouts always start with a free preview and use an idempotency key, so a retry never pays twice. Remote server (Streamable HTTP) or local package: npx -y snapex-pay-mcp.

## Tools
Capabilities this server exposes over MCP:

- **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.
- **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.
- **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.
- **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).
- **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.
- **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.
- **list_transactions** — Ledger of the balance, newest first: every credit and debit (payments, payouts, fees, conversions) with amount, direction and time. Paginated with cursor.
- **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.
- **list_invoices** — Invoices of the account, newest first, optionally filtered by status and environment. Paginated with cursor.
- **get_invoice_payment_methods** — Lists the coins and networks the payer can use for this invoice, with the amount to send in each.
- **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.
- **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.
- **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.
- **list_payments** — Payments of the account, newest first, optionally filtered by status. Paginated with cursor.
- **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_addresses** — Permanent deposit addresses of the account, optionally for one customer_ref. Paginated with cursor.
- **list_static_address_deposits** — Transfers received on one permanent address with their status and credited USDT. Paginated with cursor.
- **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.
- **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.
- **list_payouts** — Payouts of the account, newest first, optionally filtered by status. Paginated with cursor.
- **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.
- **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.
- **list_conversions** — Conversions of the account, newest first. Paginated with cursor.
- **list_webhooks** — Webhook endpoints of the account: endpoint_id, url, events, status.
- **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).
- **rotate_webhook_secret** — Issues a new signing secret for an endpoint (shown once); the old one stops working at once.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "snapex-pay": {
    "command": "npx",
    "args": ["-y","snapex-pay-mcp"]
  }
}
```

## Documentation & README

# SnapEX Pay MCP server

[![Glama score](https://glama.ai/mcp/servers/snapexpay/snapex-pay-mcp/badges/score.svg)](https://glama.ai/mcp/servers/snapexpay/snapex-pay-mcp)
[![MCP Badge](https://lobehub.com/badge/mcp/snapexpay-snapex-pay-mcp)](https://lobehub.com/mcp/snapexpay-snapex-pay-mcp)
[![Listed on mcpservers.org](https://mcpservers.org/badge.svg)](https://mcpservers.org/servers/snapexpay/snapex-pay-mcp)
[![AllMCPs Verified](https://allmcps.com/api/badge/snapex-pay)](https://allmcps.com/mcp/snapex-pay?verify=85b7468c-2bf8-4e8c-82e9-604895e8115a)

MCP server for crypto payments: an AI agent opens its own merchant account and accepts, sends and exchanges crypto.

SnapEX Pay MCP server lets an AI agent work with crypto payments without a person in the loop. The agent connects to https://pay.snapex.pro/mcp, opens a SnapEX Pay merchant account by itself (no captcha, no email) and gets an API key. Then it can create invoices with hosted payment pages, receive crypto on permanent deposit addresses, keep a USDT balance, send payouts in many coins and networks, and manage webhooks. Test mode runs the whole flow without real money. Payouts always start with a free preview and use an idempotency key, so a retry never pays twice. Remote server (Streamable HTTP) or local package: npx -y snapex-pay-mcp.

- **Remote server (recommended, nothing to install):** `https://pay.snapex.pro/mcp` — Streamable HTTP.
- **Local stdio package:** `npx -y snapex-pay-mcp` — the same tools, a thin client of the same API.
- **Docker:** `docker build -t snapex-pay-mcp . && docker run -i --rm snapex-pay-mcp`.
- MCP Registry name: `pro.snapex/pay`.
- Docs for people: <https://pay.snapex.pro/mcp> · REST reference: <https://pay.snapex.pro/partner/merchant/docs> ·
  server card: <https://pay.snapex.pro/.well-known/mcp.json> · <https://pay.snapex.pro/llms.txt>
- Privacy policy: <https://pay.snapex.pro/privacy> · Terms: <https://pay.snapex.pro/terms> · Rules for merchants:
  <https://pay.snapex.pro/rules> · Support: <https://pay.snapex.pro/#chat>

## How an agent uses it

1. Connect without a key. The catalogue tools (`list_assets`, `get_fiat_rates`, `get_fees`, `list_static_address_networks`) work at once.
2. Call `create_account`. It returns `api_key` (shown once), a cabinet `login`/`password` for a person, and
   `mcp_personal_url`. The new key is used right away: on the remote server for the rest of the MCP session, in the
   stdio package for the process (and it is saved to `~/.config/snapex-pay/credentials.json` for the next runs).
3. Receive: `create_invoice` → give `pay_url` to the payer → `get_invoice` until `paid`. `environment: "test"` runs the
   whole flow without real money (a test invoice turns paid ~10 s after a coin is selected; the balance does not change).
4. Send: `preview_payout` (free quote) → `create_payout` with the `preview_id` and your own `idempotency_key` (irreversible; a retry with the same key never pays twice).
5. The balance is kept in USDT: to get another coin, pay out in that coin. `preview_conversion` → `create_conversion`
   converts other assets an older account still holds.

Every error answer says what to do next (`what_to_do`), e.g. `unauthorized` → call `create_account`; `rate_limited` → wait `retry_after_seconds`.

## Connect

### Claude Code

```bash
claude mcp add --transport http snapex-pay https://pay.snapex.pro/mcp
# with an existing key:
claude mcp add --transport http snapex-pay https://pay.snapex.pro/mcp --header "Authorization: Bearer smk_…"
```

### Cursor — `~/.cursor/mcp.json`

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

Add `"headers": { "Authorization": "Bearer smk_…" }` to keep one account across sessions.

### VS Code — `.vscode/mcp.json`

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

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

```json
{
  "mcpServers": {
    "snapex-pay": { "serverUrl": "https://pay.snapex.pro/mcp" }
  }
}
```

### Cline — `cline_mcp_settings.json`

```json
{
  "mcpServers": {
    "snapex-pay": { "type": "streamableHttp", "url": "https://pay.snapex.pro/mcp" }
  }
}
```

Step-by-step for AI installers: [`llms-install.md`](https://github.com/snapexpay/snapex-pay-mcp/blob/HEAD/llms-install.md).

### Gemini CLI

As an extension (this repository has `gemini-extension.json`):

```bash
gemini extensions install https://github.com/snapexpay/snapex-pay-mcp
```

or in `~/.gemini/settings.json`:

```json
{
  "mcpServers": {
    "snapex-pay": { "httpUrl": "https://pay.snapex.pro/mcp" }
  }
}
```

### Claude Desktop — `claude_desktop_config.json`

Remote server through `mcp-remote`:

```json
{
  "mcpServers": {
    "snapex-pay": { "command": "npx", "args": ["-y", "mcp-remote", "https://pay.snapex.pro/mcp"] }
  }
}
```

or the local package:

```json
{
  "mcpServers": {
    "snapex-pay": {
      "command": "npx",
      "args": ["-y", "snapex-pay-mcp"],
      "env": { "SNAPEX_API_KEY": "smk_…" }
    }
  }
}
```

(`SNAPEX_API_KEY` is optional: without it the agent calls `create_account` and the key is saved for the next runs.)

### claude.ai and ChatGPT connectors

Add a custom connector with the URL `https://pay.snapex.pro/mcp` and no authentication. These clients cannot send
headers, so after `create_account` take `mcp_personal_url` from its answer (also returned by `get_account`) and use it
as the connector URL — every new chat then works with the same account. That URL contains a credential: treat it as a password.

### OpenAI Responses API

```json
{
  "type": "mcp",
  "server_label": "snapex_pay",
  "server_url": "https://pay.snapex.pro/mcp",
  "headers": { "Authorization": "Bearer smk_…" },
  "require_approval": { "always": { "tool_names": ["create_payout", "create_conversion"] } }
}
```

### Other clients and catalogs

The repository carries the manifests the catalogs read: `server.json` (official MCP Registry), `glama.json` (Glama),
`gemini-extension.json` + `GEMINI.md` (Gemini CLI), `lhm.plugin.json` (LobeHub), `.cursor-plugin/plugin.json` +
`mcp.json` (Cursor Marketplace), `plugin.json` (Agent Plugins / Kiro), `llms-install.md` (Cline).

### Docker

```bash
docker build -t snapex-pay-mcp .
docker run -i --rm -e SNAPEX_API_KEY=smk_… snapex-pay-mcp
```

## Tools

**Account**

| Tool | What it does |
|---|---|
| `create_account` | Open a SnapEX Pay account (no captcha) |
| `get_account` | Show the current account and key |

**Catalogue (no key needed)**

| Tool | What it does |
|---|---|
| `list_assets` | List coins and networks |
| `get_fiat_rates` | Fiat exchange rates |
| `get_fees` | Current route fee quotes |
| `list_static_address_networks` | Networks for permanent addresses |

**Balance**

| Tool | What it does |
|---|---|
| `get_balances` | Account balance |
| `list_transactions` | Balance history |

**Receive**

| Tool | What it does |
|---|---|
| `create_invoice` | Create an invoice (receive crypto) |
| `get_invoice` | Invoice status |
| `list_invoices` | List invoices |
| `get_invoice_payment_methods` | Coins an invoice can be paid with |
| `select_invoice_payment_method` | Pick a coin for an invoice |
| `preview_payment` | Quote a direct payment |
| `create_payment` | Create a direct payment |
| `get_payment` | Payment status |
| `list_payments` | List payments |
| `create_static_address` | Permanent deposit address |
| `list_static_addresses` | List permanent addresses |
| `list_static_address_deposits` | Deposits to a permanent address |

**Send (payouts)**

| Tool | What it does |
|---|---|
| `preview_payout` | Quote a payout (send crypto) |
| `create_payout` | Send a payout (irreversible) ⚠️ irreversible |
| `get_payout` | Payout status |
| `list_payouts` | List payouts |

**Exchange**

| Tool | What it does |
|---|---|
| `preview_conversion` | Quote a conversion (exchange) |
| `create_conversion` | Execute a conversion ⚠️ irreversible |
| `get_conversion` | Conversion status |
| `list_conversions` | List conversions |

**Webhooks**

| Tool | What it does |
|---|---|
| `list_webhooks` | List webhook endpoints |
| `create_webhook` | Add a webhook endpoint |
| `update_webhook` | Change a webhook endpoint |
| `rotate_webhook_secret` | New webhook secret ⚠️ irreversible |

Resources: `snapex://docs/quickstart`, `snapex://docs/webhooks`. Prompts: `accept_crypto_payment`, `send_crypto_payout`.

## Environment (stdio package)

| Variable | Default | Meaning |
|---|---|---|
| `SNAPEX_API_KEY` | — | Merchant API key `smk_…`. Optional: `create_account` makes one. |
| `SNAPEX_BASE_URL` | `https://pay.snapex.pro` | API base URL. |
| `SNAPEX_CREDENTIALS_FILE` | `~/.config/snapex-pay/credentials.json` | Where a key from `create_account` is saved (mode 600). |
| `SNAPEX_NO_SAVE` | — | `1` — do not save credentials to disk. |

## Safety

- An agent moves only its own account's money; a new account starts at zero.
- The key and the generated password are shown once. A person can open the cabinet with the login and password and revoke or rotate keys there.
- Payouts are two-step (quote, then send) and need an `idempotency_key`; `create_payout`, `create_conversion` and
  `rotate_webhook_secret` are marked `destructiveHint`, so clients can ask before running them.
- Limits: a few new accounts per IP per hour; about 120 API calls a minute per key; payouts 5 a minute and 30 an hour.
- Rules for what can be sold: <https://pay.snapex.pro/rules>.

## Development

The tool list is generated from the SnapEX Pay server (`app/Mcp/McpToolCatalog.php`):

```bash
php artisan mcp:export-tools      # writes src/tools.json, syncs the version of the manifests and LobeHub's tools
npm ci && npm test                # build + offline smoke test with the official MCP SDK client
SNAPEX_E2E_BASE_URL=http://127.0.0.1:8765 node test/smoke.mjs   # full flow against a local (never production) server
```

## Support

Chat: <https://pay.snapex.pro/#chat> · Privacy: <https://pay.snapex.pro/privacy> · Terms: <https://pay.snapex.pro/terms>

## License

MIT