All servers / Payments / Stablevoy MCP server
Stablevoy MCP server
MCP server for Stablevoy: create and cancel USDT and USDC invoices, sum up payments, review unmatched transfers and search the docs from Claude, Cursor or any M
Tested by ConnectATDScore 86 out of 100. Tested 2026-11-19 on package version 0.7.0. Package: stablevoy-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (1.9 seconds including download)
- Tools offered: 10
- Last published: 2026-11-14
- Weekly downloads (npm): 657
- License: MIT · Direct dependencies: 3
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
list_storesno parametersLists every Stablevoy store this server has a key for, all at once with no paging (usually one to a few). Needs a store key (npx stablevoy-mcp login). Each entry has id, name, status, enabledNetworks, canAcceptPayments, evmPayoutStatus, the payout addresses the store uses, whether each is its own or the account one, and the account addresses. Payout addresses are read only here. They change in the dashboard. A store whose key no longer works shows its error instead. An archived store has its keys revoked, so it shows that error. Call it first to learn the names for the store argument of the other tools. For the full settings of one store use get_store. A failure comes back as an error with its code and what to do, for example rate_limited with the seconds to wait.
get_store1 of 1 parameter describedGets one store with its settings, read only. Needs a store key (npx stablevoy-mcp login). Each call makes three live requests: the store, the platform limits and the fee. Nothing is cached, so a change made in the dashboard shows at once. Nothing here can change a setting. That is done in the Stablevoy dashboard. Returned, grouped: status and canAcceptPayments; networks and payout state, with the payout addresses this store uses, whether each is its own or the account one, and the account addresses; the invoice range in effect with the store and platform limits and the fee; the website, return and webhook addresses; webhookHealth, the state of the webhook endpoint (null without a webhook URL): status active, failing after 10 failed attempts with pausesAt (when it will be paused if it keeps failing) or paused after 24 hours of failures, when new events wait until the merchant resumes it in the dashboard; archivedAt. Call it first when create_invoice fails or a store cannot accept payments. For the short view of all stores use list_stores. Leaving store out works only with one connected store. With several, the answer is an error listing their names and ids. The API takes up to 300 requests a minute from one address. A failure comes back as an error with its code and what to do, for example rate_limited with the seconds to wait.
get_invoice2 of 2 parameters describedGets one invoice by its id: status, amountUsd, reference, dates (createdAt, expiresAt, paidAt), holdReason, networks and the payments received. Needs a store key (npx stablevoy-mcp login). The id comes from create_invoice, list_invoices or the merchant. Without store every connected store is asked; an id no store has gives not_found. To find invoices by status, reference or date, use list_invoices. A failure comes back as an error with its code and what to do, for example rate_limited with the seconds to wait.
list_invoices8 of 8 parameters describedLists invoices newest first, to find invoices when you have no id. Needs a store key (npx stablevoy-mcp login). All filters are optional and combine: status, source, search (an invoice id or the start of the reference), createdFrom and createdTo (UTC days, both included) and limit (1 to 100, 20 by default). Each call returns one page per store: its name, invoices with the fields of get_invoice, and nextCursor. For the next page pass nextCursor as cursor with the same store. No match is an empty list. For one invoice by id use get_invoice; for totals of a period use summarize_payments. A failure comes back as an error with its code and what to do, for example rate_limited with the seconds to wait.
summarize_payments4 of 4 parameters describedSums up the invoices created in a period, instead of paging through list_invoices. Needs a store key (npx stablevoy-mcp login). It returns how many invoices are in each status, invoicedUsd (cancelled and expired left out), receivedUsd (confirmed payments that passed sanctions screening) and the money per network and token. Pass either period or both createdFrom and createdTo as UTC days. A period together with dates, or only one of the two dates, is refused. One call covers at most 92 days; ask for a year in four quarters. Without store and with several stores you get one summary per store plus a total. Use list_invoices to see the invoices themselves. A failure comes back as an error with its code and what to do, for example rate_limited with the seconds to wait.
list_unmatched_transfers1 of 1 parameter describedLists payments that reached the merchant's own Tron wallet but matched no invoice, newest first. Needs a store key (npx stablevoy-mcp login). This usually happens when an exchange took its fee out of the amount. At most the 100 newest are returned; there is no paging past them. Each transfer has amountUsd, network, token, fromAddress, txHash, explorerUrl, detectedAt and the stores it was listed for. sharedWithStores tells whose it is: how many active stores offer the network and pay out to the same wallet, so 1 means the transfer is certainly that store's and more means it may belong to any of that many stores. You cannot attach a transfer to an invoice: tell the merchant to do it in the Stablevoy dashboard, Unmatched transfers section. Use get_invoice or list_invoices to find the invoice the buyer meant. Without store and with several stores, every store is asked and each transfer is listed once. A failure comes back as an error with its code and what to do, for example rate_limited with the seconds to wait.
create_invoice5 of 5 parameters describedCreates a Stablevoy invoice the buyer pays in USDT or USDC and returns its payment link, checkoutUrl. Needs a store key (npx stablevoy-mcp login). Send that link to the buyer yourself; Stablevoy does not email it. Give a reference (for example "acme-october") whenever you can: the same amount and reference return the same invoice instead of a second one. returnUrl is an https page the buyer goes back to after paying. expiresInMinutes, 15 to 10080, is how long the buyer has; left out, the store default applies. After expiresAt the payment page tells the buyer not to pay, and money that still arrives is marked paid_late. To change the amount of an unpaid invoice, cancel it with cancel_invoice first. Check the result later with get_invoice. Pass store when several stores are connected. A failure comes back as an error with its code and what to do, for example rate_limited with the seconds to wait.
cancel_invoice2 of 2 parameters describedCancels an unpaid invoice so the buyer can no longer pay it, for example when the order was called off. Needs a store key (npx stablevoy-mcp login). Pass the invoiceId from create_invoice, list_invoices or get_invoice. Without store every connected store is tried and only the one that owns the invoice cancels it. It works only while no payment has been seen; otherwise it returns invoice_not_cancellable and the invoice stays as it is. Money that still arrives later is marked paid_late, and cancelling twice returns the invoice unchanged. Use get_invoice first if you are not sure of its status. A failure comes back as an error with its code and what to do, for example rate_limited with the seconds to wait.
search_docs1 of 1 parameter describedSearches the Stablevoy documentation for how-to questions. Needs no key. Topics: connecting a shop, stores, webhooks and their signatures, networks and fees, the payment widget, the plugins, recovery. A section ranks higher for each query word it contains. It ranks higher still when the word is in its heading or page title. Two to four specific words work best, for example "webhook signature" or "Tron fee". Each hit has the page title, its path for get_doc, the page address, the heading and up to 2000 characters of the section. Only the best 5 hits come back and there is no paging, so use other words to reach other sections. An empty list means no word matched. Call get_doc with a path to read the whole page. This running server keeps the pages for an hour, so searching again makes no request.
get_doc1 of 1 parameter describedGets one whole page of the Stablevoy documentation as Markdown. Needs no key. Pass a path from search_docs; the OpenAPI outline lists every API endpoint with its parameters, the errors page every error code with what to do. Only Stablevoy pages are read: any other address is refused with the list of pages, and a page over 1 MB is refused rather than cut. Use search_docs first when you do not know which page has the answer.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.