pro.snapex/pay

None of its 32 tools are described as changing anything. For 32 the reading was uncertain, so no mark is shown.

• create_accounton 46 other servers

  “Opens a new SnapEX Pay merchant account for you and returns a merchant API key with every scope (receive, pay out, convert, webhooks).”

  Publisher declares: read-only no · destructive no · idempotent no · open-world yes

  5 inputs

  • agentstring“Who you are: your product or agent name (shown to SnapEX support).”
  • emailstring“Optional contact email of the account owner.”
  • telegramstring“Optional Telegram @username of the owner.”
  • loginstring“Optional cabinet login; generated (agent-xxxxxxxxxx) when omitted.”
  • passwordstring“Optional cabinet password; a strong one is generated and returned when omitted.”
• get_accounton 123 other servers

  “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 h…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  Takes no inputs.

• list_assetson 34 other servers

  “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_…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  Takes no inputs.

• get_fiat_rates

  “Fiat → USD rates used for invoices priced in another currency (create_invoice with price_amount + price_currency).”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  1 input

  • currencystring“ISO 4217 code.”
• get_feeson 7 other servers

  “What SnapEX Pay charges, no key needed.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  3 inputs

  • routestring“Route name, e.g.”
  • from_asset_idstring“Public asset code from list_assets (its asset_id field), e.g.”
  • to_asset_idstring“Public asset code from list_assets (its asset_id field), e.g.”
• list_static_address_networks

  “Lists the coins/networks for which you can get a permanent deposit address (create_static_address): asset code (e.g.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  Takes no inputs.

• get_balanceson 9 other servers

  “Returns the account balance.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  Takes no inputs.

• list_transactionson 22 other servers

  “Ledger of the balance, newest first: every credit and debit (payments, payouts, fees, conversions) with amount, direction and time.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  3 inputs

  • statusstring“Filter by ledger entry type.”
  • cursorstring“Pass meta.next_cursor of the previous page to get the next one.”
  • limitinteger“Items per page (1–100).”
• create_invoiceon 20 other servers

  “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.”

  Publisher declares: read-only no · destructive no · idempotent yes · open-world yes

  13 inputs

  • amount_usdstring“Invoice amount in USD.”
  • price_amountstring“Price in your currency (with price_currency).”
  • price_currencystring“ISO 4217 currency of price_amount.”
  • descriptionstring“What is paid for; shown to the payer.”
  • external_idstring“Your own reference (order id); unique per account.”
  • environmentstring“"test" — no real money: paid by itself ~10 s after a coin is selected, balance unchanged.”
  • fee_onstring“Who pays the service fee: you (default) or the payer on top of the amount.”
  • asset_idstring“Preselect the coin the payer pays with (Public asset code from list_assets (its asset_id field), e.g.”
  • lock_methodboolean“true — the payer cannot change asset_id (requires asset_id).”
  • expires_ininteger“Seconds until the invoice expires.”
  • success_urlstring“Where the payer returns after paying.”
  • cancel_urlstring“Where the payer returns on cancel.”
  • idempotency_keystring“Optional.”
• get_invoiceon 21 other servers

  “Returns one invoice with its status (open, awaiting, underpaid, paid, partially_paid, expired), pay_url, credit_usd, the selected coin and the payment attempts.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  1 input, 1 required

  • invoice_idstringrequired“invoice_id from create_invoice.”
• list_invoiceson 23 other servers

  “Invoices of the account, newest first, optionally filtered by status and environment.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  4 inputs

  • statusstring“e.g.”
  • environmentstring
  • cursorstring“Pass meta.next_cursor of the previous page to get the next one.”
  • limitinteger“Items per page (1–100).”
• get_invoice_payment_methods

  “Lists the coins and networks the payer can use for this invoice, with the amount to send in each.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  1 input, 1 required

  • invoice_idstringrequired“invoice_id from create_invoice.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-03.

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.