SnapEX Pay

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 电脑或云端
• 传输方式: stdio, Streamable HTTP
• 分类: 其他
• 你需要填写：SNAPEX_API_KEY, Authorization

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接
• npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

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

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

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

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

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

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

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

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

• SNAPEX_API_KEY 机密 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 机密 HTTP header
  Optional: "Bearer smk_…" merchant API key. Without it the agent calls create_account and the session goes on with the new key.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

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

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 snapex.pro 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 685 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 32 个工具描述，未发现针对 AI 的隐藏指令

与“其他”中的其他服务器比较i

• 星标数多于此分类中其他 32583 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 32583 个服务器的 92% 更新
• 基础检查结果等于或优于此分类中其他 32583 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

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

{

{

{

{

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

{

{

{

{

docker build -t snapex-pay-mcp .

php artisan mcp:export-tools      # writes src/tools.json, syncs the version of the manifests and LobeHub's tools