Prototyp · Vorschau: alle Server aus der offiziellen Registry, alle 30 Minuten synchronisiert. Bewertungen und Benutzerkonten folgen in einem späteren Schritt.
PopNx MCPMCP-Server für alle, die KI nutzen · in einfachen Worten erklärt

SnapEX Pay

von snapexpayVersion 1.0.2i★ –iComputer oder Cloud
Name in der Registrypro.snapex/pay

Installieren

Überblick

Beschreibung vom Entwickler (englisches Original)

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

Die drei Säulen von PopNx MCP

Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

  • Verbindung: Computer oder Cloud
  • Transport: stdio, Streamable HTTP
  • Kategorie: Sonstiges
  • Das musst du eintragen: SNAPEX_API_KEY, Authorization

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Bevor du installierst

  • Basischecks: 3 von 3 bestanden
  • Läuft auf dem Server des Entwicklers: Was du fragst, läuft über dessen Server.
  • Kann 32 Dinge (Tools) create_account, get_account, list_assets, get_fiat_rates …
  • Das trägst du selbst ein: SNAPEX_API_KEY, SNAPEX_BASE_URL, Authorization

Als geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.

Du brauchst

  • Läuft in der CloudNichts zu installieren; die Verbindung läuft übers Internet
  • npmNode.js installiert (für den Befehl npx)

Welche App nutzt du?

Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.

Diese Adresse braucht einen Schlüssel in einem Header der Anfrage, und das Menü zum Hinzufügen von Connectors kann ihn nicht setzen. Nutze stattdessen Claude Code, Cursor oder VS Code.

Oder führ ihn auf deinem Computer aus

Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein

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

Führe das in deinem Terminal aus

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

Oder führ ihn auf deinem Computer aus

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

Trag die leeren Werte ein, bevor du ihn startest.

In Cursor öffnen

Oder kopier die Einstellungen selbst

In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen

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

Oder führ ihn auf deinem Computer aus

In Cursor öffnen

Oder kopier die Einstellungen selbst

In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen

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

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

In VS Code öffnen

Oder kopier die Einstellungen selbst

In .vscode/mcp.json in deinem Projekt einfügen

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

Oder führ ihn auf deinem Computer aus

In VS Code öffnen

Oder kopier die Einstellungen selbst

In .vscode/mcp.json in deinem Projekt einfügen

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

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

Diese Adresse braucht einen Schlüssel in einem Header der Anfrage, und das Menü zum Hinzufügen von Connectors kann ihn nicht setzen. Nutze stattdessen Claude Code, Cursor oder VS Code.

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Werte, die du selbst einträgst

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

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Tool-Namen und -Beschreibungen genau so, wie der Server sie am 6. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen 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.

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026

  • ✓ Bestanden

    Entwickler passt zum Repo

    Der Registry-Name wurde über die Domain snapex.pro bestätigt (die Registry prüft, wem die Domain gehört)

  • … Noch nicht geprüft

    Wird noch gepflegt

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • … Noch nicht geprüft

    Hat eine Lizenz

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • ✓ Bestanden

    Endpunkt antwortet

    Antwort in 685 ms (HTTP 200)

  • – Nicht zutreffend

    Anmeldung mit OAuth

    Keine Anmeldung nötig

  • ✓ Bestanden

    Keine versteckten Anweisungen in Tool-Beschreibungen

    Wir haben 32 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Im Vergleich mit anderen in Sonstigesi

  • Mehr Sterne als 0 % der anderen 32476 Server in dieser Kategorie
  • Neuer in der Registry veröffentlicht als 92 % der anderen 32476 Server in dieser Kategorie
  • Basischecks gleich gut wie oder besser als bei 100 % der anderen 32476 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Häufige Fragen

Ist SnapEX Pay sicher?

Er hat 3 von 3 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.

Welche Schlüssel oder Codes braucht er?

Das musst du eintragen: SNAPEX_API_KEY, Authorization

Läuft er auf meinem Computer oder in der Cloud?

Beides geht: Installiere ihn auf deinem Computer oder verbinde dich mit der Cloud-Version.

Wird er noch gepflegt?

Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (1.0.2) kam vorgestern in die Registry.

Welche Apps können ihn nutzen?

Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.

Was kann ich stattdessen nutzen?

In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, zanadir

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

Spec Driven Development

von formulahendry

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

Läuft auf deinem Computer★ 440MITAktualisiert vor 14 Monaten
Installieren

Remote Desktop Commander

von desktop-commander

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

Läuft in der Cloud★ 211Aktualisiert gestern
Installieren

zanadir

von MustacheCase

Find what a repository's CI is missing, and which security checks cannot fail the build.

Läuft auf deinem ComputerAktualisiert heute
Installieren

README vom Entwickler

README öffnen

Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.

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

PopNx fragen