Saltar al contenido
Logo de SnapEX

Servidor MCP de SnapEX

Qué servidores MCP son de SnapEX, del registro oficial y encontrados preguntando a su propio dominio, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-11-02

← Volver a SnapEX

De quién es el servidor
  • Nombre en el registropro.snapex/payverificado en el registro MCP

El nombre en el registro está bajo snapex.pro. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

Cuando le preguntamoscomprobado el 2026-11-02
  • Estadorespondecomprobado el 2026-11-02
  • Herramientas32
  • El servidor se llamasnapex-pay
  • Versión del servidor1.0.0
  • Versión del protocolo2025-06-18

El 2026-11-02 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 738 ms.

¿Debe un agente conectarlo?Aún no está claro
  • Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
  • Comprobado 2 de los 7 días necesarios para juzgar su fiabilidad.

Una vez conectado

  • create_account, create_invoice, create_payment, create_static_address, create_payout cambian datos sin iniciar sesión: cualquiera con la dirección puede llamarlas.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

Medido cada díacomprobaciones diarias: 2, la primera el 2026-11-02
  • Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 2 hasta ahora
  • Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
  • Mediana de la primera respuesta808 ms
  • Espacio en el contexto del agente≈ 6109 tokenslas definiciones de todas sus herramientas (32), que el agente lleva en cada turno
  • Definiciones de herramientasA · 98 de 100
  • Resultados tipados0 de 32 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez
  • Parámetros sin descripción: en 4 de 32

Qué puede hacer un agente con él

  • no está claro · exchange cryptocurrency anonymously through an automated 24/7 swap
  • no está claro · withdraw bonus earnings in USDT
  • no puede · play slots, mines and dice with bonus funds

Cada caso de uso del producto se le preguntó a Jev junto con la lista de herramientas de este servidor: ¿puede un agente hacerlo con estas herramientas?

Conviene revisar

  • Herramientas que cambian datos, en un servidor que responde sin iniciar sesión: create_account, create_invoice, create_payment, create_static_address, create_payout

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

Herramientas que ofrece32 herramientas · leído el 2026-11-02
  • 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…

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

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

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

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

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

  • 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_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…

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

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

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

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

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

Cómo conectar

Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:

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

Añadirlo

Claude Code, en una terminal

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

Añadir a CursorAñadir a VS Code

claude.ai, ChatGPT y otros clientes: añade https://pay.snapex.pro/mcp como conector personalizado en los ajustes.

Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.