Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

SnapEX Pay

by snapexpayversion 1.0.2i★ –iComputer or cloud
Registry namepro.snapex/pay

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Computer or cloud
  • Transport: stdio, Streamable HTTP
  • Category: Other
  • You need to fill in: SNAPEX_API_KEY, Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 3 of 3 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • Can do 32 things (tools) create_account, get_account, list_assets, get_fiat_rates …
  • You fill in yourself: SNAPEX_API_KEY, SNAPEX_BASE_URL, Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • Runs in the cloudNothing to install; it connects over the internet
  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "pay": {
      "command": "npx",
      "args": [
        "-y",
        "snapex-pay-mcp"
      ],
      "env": {
        "SNAPEX_API_KEY": "your-value",
        "SNAPEX_BASE_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http pay https://pay.snapex.pro/mcp --header 'Authorization: your-value'

Or run it on your computer

claude mcp add pay --env SNAPEX_API_KEY=your-value --env SNAPEX_BASE_URL=your-value -- npx -y snapex-pay-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "pay": {
      "url": "https://pay.snapex.pro/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "pay": {
      "command": "npx",
      "args": [
        "-y",
        "snapex-pay-mcp"
      ],
      "env": {
        "SNAPEX_API_KEY": "your-value",
        "SNAPEX_BASE_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "pay": {
      "type": "http",
      "url": "https://pay.snapex.pro/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "pay": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "snapex-pay-mcp"
      ],
      "env": {
        "SNAPEX_API_KEY": "your-value",
        "SNAPEX_BASE_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • SNAPEX_API_KEY secret env
    Merchant API key (smk_…). Optional: create_account makes one and saves it to ~/.config/snapex-pay/credentials.json.
  • SNAPEX_BASE_URL env
    API base URL.
  • Authorization secret HTTP header
    Optional: "Bearer smk_…" merchant API key. Without it the agent calls create_account and the session goes on with the new key.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

  • 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

  • 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 p

  • 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 b

  • 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 w

  • 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_netw

  • 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 amoun

  • 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

  • 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

  • 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 " . " against the Webhook-Signature header ("v1= "). Deliveries are at-least-once — dedupe by Webhook

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

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain snapex.pro (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • ✓ Pass

    Endpoint responds

    Responded in 685 ms (HTTP 200)

  • – Not applicable

    Sign-in with OAuth

    No sign-in needed

  • ✓ Pass

    No hidden instructions in tool descriptions

    Read 32 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

  • More stars than 0% of the other 32589 servers in this category
  • Published to the registry more recently than 92% of the other 32589 servers in this category
  • Basic checks equal to or better than 100% of the other 32589 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is SnapEX Pay safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: SNAPEX_API_KEY, Authorization

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.2) reached the registry 3 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Detailing Manager

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

Detailing Manager

by RadoslavMoshev

Connect your auto detailing studio's tasks, cars, clients and revenue to Claude or ChatGPT.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

SnapEX Pay MCP server

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.

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
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
{

"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
{

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

Windsurf — ~/.codeium/windsurf/mcp_config.json
{

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

Cline — cline_mcp_settings.json
{

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

Step-by-step for AI installers: llms-install.md.

Gemini CLI

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

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

or in ~/.gemini/settings.json:

{

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

Claude Desktop — claude_desktop_config.json

Remote server through mcp-remote:

{

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

or the local package:

{

"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
{

"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
docker build -t snapex-pay-mcp .

docker run -i --rm -e SNAPEX_API_KEY=smk_… snapex-pay-mcp

Tools

Account

ToolWhat it does
create_accountOpen a SnapEX Pay account (no captcha)
get_accountShow the current account and key

Catalogue (no key needed)

ToolWhat it does
list_assetsList coins and networks
get_fiat_ratesFiat exchange rates
get_feesCurrent route fee quotes
list_static_address_networksNetworks for permanent addresses

Balance

ToolWhat it does
get_balancesAccount balance
list_transactionsBalance history

Receive

ToolWhat it does
create_invoiceCreate an invoice (receive crypto)
get_invoiceInvoice status
list_invoicesList invoices
get_invoice_payment_methodsCoins an invoice can be paid with
select_invoice_payment_methodPick a coin for an invoice
preview_paymentQuote a direct payment
create_paymentCreate a direct payment
get_paymentPayment status
list_paymentsList payments
create_static_addressPermanent deposit address
list_static_addressesList permanent addresses
list_static_address_depositsDeposits to a permanent address

Send (payouts)

ToolWhat it does
preview_payoutQuote a payout (send crypto)
create_payoutSend a payout (irreversible) ⚠️ irreversible
get_payoutPayout status
list_payoutsList payouts

Exchange

ToolWhat it does
preview_conversionQuote a conversion (exchange)
create_conversionExecute a conversion ⚠️ irreversible
get_conversionConversion status
list_conversionsList conversions

Webhooks

ToolWhat it does
list_webhooksList webhook endpoints
create_webhookAdd a webhook endpoint
update_webhookChange a webhook endpoint
rotate_webhook_secretNew webhook secret ⚠️ irreversible

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

Environment (stdio package)

VariableDefaultMeaning
SNAPEX_API_KEY—Merchant API key smk_…. Optional: create_account makes one.
SNAPEX_BASE_URLhttps://pay.snapex.proAPI base URL.
SNAPEX_CREDENTIALS_FILE~/.config/snapex-pay/credentials.jsonWhere 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):

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

Ask PopNx