Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Crypto payments for AI agents: self-serve account, invoices, receiving, payouts, exchange.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
SNAPEX_API_KEY, SNAPEX_BASE_URL, AuthorizationLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Esta dirección necesita una clave en un header de la solicitud, y el menú para agregar conectores no puede ponerla. Usa Claude Code, Cursor o VS Code.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"pay": {
"command": "npx",
"args": [
"-y",
"snapex-pay-mcp"
],
"env": {
"SNAPEX_API_KEY": "your-value",
"SNAPEX_BASE_URL": "your-value"
}
}
}
}Ejecuta esto en tu terminal
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-mcpCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"pay": {
"url": "https://pay.snapex.pro/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"pay": {
"command": "npx",
"args": [
"-y",
"snapex-pay-mcp"
],
"env": {
"SNAPEX_API_KEY": "your-value",
"SNAPEX_BASE_URL": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"pay": {
"type": "http",
"url": "https://pay.snapex.pro/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"pay": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"snapex-pay-mcp"
],
"env": {
"SNAPEX_API_KEY": "your-value",
"SNAPEX_BASE_URL": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Esta dirección necesita una clave en un header de la solicitud, y el menú para agregar conectores no puede ponerla. Usa Claude Code, Cursor o VS Code.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
SNAPEX_BASE_URL envAuthorization secreto HTTP headerEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Nombres y descripciones de las herramientas tal como los informó el servidor el 6 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.
create_accountOpens 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_accountReturns 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_assetsLists 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_ratesFiat → 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_feesWhat 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_networksLists 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_balancesReturns 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_transactionsLedger of the balance, newest first: every credit and debit (payments, payouts, fees, conversions) with amount, direction and time. Paginated with cursor.
create_invoiceCreates 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_invoiceReturns 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_invoicesInvoices of the account, newest first, optionally filtered by status and environment. Paginated with cursor.
get_invoice_payment_methodsLists the coins and networks the payer can use for this invoice, with the amount to send in each.
select_invoice_payment_methodChooses 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_paymentLow-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_paymentCreates 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_paymentOne 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_paymentsPayments of the account, newest first, optionally filtered by status. Paginated with cursor.
create_static_addressGets (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_addressesPermanent deposit addresses of the account, optionally for one customer_ref. Paginated with cursor.
list_static_address_depositsTransfers received on one permanent address with their status and credited USDT. Paginated with cursor.
preview_payoutStep 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_payoutStep 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_payoutOne 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_payoutsPayouts of the account, newest first, optionally filtered by status. Paginated with cursor.
preview_conversionStep 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_conversionStep 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_conversionOne conversion with its status and amounts.
list_conversionsConversions of the account, newest first. Paginated with cursor.
list_webhooksWebhook endpoints of the account: endpoint_id, url, events, status.
create_webhookRegisters 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_webhookReplaces the url and events of an endpoint, or disables/enables it (status).
rotate_webhook_secretIssues a new signing secret for an endpoint (shown once); the old one stops working at once.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con el dominio snapex.pro (el registro comprueba quién es dueño del dominio)
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Respondió en 685 ms (HTTP 200)
No hace falta iniciar sesión
Leímos 32 descripciones de herramientas y no encontramos instrucciones ocultas para la IA
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 3 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: SNAPEX_API_KEY, Authorization
Funciona de las dos formas: instálalo en tu computadora o conéctate a la versión en la nube.
El repo de GitHub cambió por última vez –, y la última versión (1.0.2) llegó al registro hace 3 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, AvaHR
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Read hiring data and create inactive assessment and questionnaire drafts for human review.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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.
https://pay.snapex.pro/mcp — Streamable HTTP.npx -y snapex-pay-mcp — the same tools, a thin client of the same API.docker build -t snapex-pay-mcp . && docker run -i --rm snapex-pay-mcp.pro.snapex/pay.list_assets, get_fiat_rates, get_fees, list_static_address_networks) work at once.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).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).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).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.
claude mcp add --transport http snapex-pay https://pay.snapex.pro/mcp
claude mcp add --transport http snapex-pay https://pay.snapex.pro/mcp --header "Authorization: Bearer smk_…"
~/.cursor/mcp.json{
"mcpServers": { "snapex-pay": { "url": "https://pay.snapex.pro/mcp" } } }
Add "headers": { "Authorization": "Bearer smk_…" } to keep one account across sessions.
.vscode/mcp.json{
"servers": { "snapex-pay": { "type": "http", "url": "https://pay.snapex.pro/mcp" } } }
~/.codeium/windsurf/mcp_config.json{
"mcpServers": { "snapex-pay": { "serverUrl": "https://pay.snapex.pro/mcp" } } }
cline_mcp_settings.json{
"mcpServers": { "snapex-pay": { "type": "streamableHttp", "url": "https://pay.snapex.pro/mcp" } } }
Step-by-step for AI installers: llms-install.md.
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_config.jsonRemote 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.)
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.
{
"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"] } } }
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 build -t snapex-pay-mcp .
docker run -i --rm -e SNAPEX_API_KEY=smk_… snapex-pay-mcp
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.
| 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. |
idempotency_key; create_payout, create_conversion and rotate_webhook_secret are marked destructiveHint, so clients can ask before running them.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
Chat: https://pay.snapex.pro/#chat · Privacy: https://pay.snapex.pro/privacy · Terms: https://pay.snapex.pro/terms
MIT