Stablevoy Mcp

io.github.stablevoyPublished by GitHub account stablevoyv0.1.1Updated Nov 6, 2026

USDT and USDC invoices and payment checks across your Stablevoy stores. Keys cannot move funds.

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Connects an assistant to Stablevoy stores so it can create USDT/USDC invoices, fetch payment links and check which invoices are paid.

What you can do
  • List and inspect stores, including networks, payout addresses, limits and fees
  • Create an invoice for a dollar amount with an optional reference and return URL, returning a payment link
  • Look up a single invoice with the payments received
  • List invoices newest first, filtered by status, source, search text and creation date
When to use it
Useful when you bill clients in USDT or USDC through Stablevoy and want an assistant to draft invoices, hand out payment links, or report on what came in this week across one or more stores.
Requirements
Runs locally over stdio via npx, so Node.js 22.12 or later is needed. Either run the login command, which opens the Stablevoy dashboard in a browser for a wallet sign-in and stores one API key per store in the config folder, or set STABLEVOY_API_KEY for a single store. Optional variables: STABLEVOY_MCP_PROFILE, STABLEVOY_MCP_READ_ONLY, STABLEVOY_API_URL. Network access to the Stablevoy API.
Before you install
The server holds store API keys that can create invoices and read invoice amounts and references; it cannot move funds or change payout addresses, webhooks, limits, keys or stores. Reading is the stated exposure, so consider STABLEVOY_MCP_READ_ONLY=true to drop invoice creation, especially if the assistant also reads untrusted content. Keys are stored in a local config folder and can be revoked from the dashboard; logout revokes all keys for that computer.

Installation

In SourceWeft

  1. Open Stablevoy Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

stablevoy-mcp

An MCP server for Stablevoy, the non-custodial USDT and USDC payment gateway. Ask your AI assistant to bill a client, check whether an invoice is paid or sum up the week, across all your stores:

  • "Bill Acme 250 dollars for the October work" gives a payment link.
  • "Has Acme paid?" gives the status and the transactions.
  • "What came in this week in the Main store?" gives the list.

It works with Claude Desktop, Claude Code, Cursor and any client that speaks the Model Context Protocol. It runs on your computer and talks only to the Stablevoy API.

What it can and cannot do

The server holds store API keys only. With them it can create invoices to receive money and read your stores and invoices. It cannot move funds, change your payout address, your webhooks, your limits, your keys or your stores: those need your wallet signature in the Stablevoy dashboard. Stablevoy never holds your money, so there is nothing to withdraw.

So even an assistant tricked by a malicious web page or document can only create invoices that pay you, and read your invoices. Reading is the real exposure: invoice amounts and your references. Keep that in mind before you connect the server to an assistant that also reads untrusted content, or run it read-only (below).

Connect

Requires Node.js 22.12 or later.

sh
npx stablevoy-mcp login

This opens the Stablevoy dashboard in your browser. Sign in with your wallet, tick the stores the assistant may use and approve. The browser hands a one-time code back to the command on this computer, which exchanges it for one API key per store and keeps them in your config folder (~/.config/stablevoy-mcp on Linux, ~/Library/Application Support/stablevoy-mcp on macOS, %APPDATA%\stablevoy-mcp on Windows), readable by you only. The keys are named "MCP (your computer)" on the store pages of the dashboard, where you can revoke any of them.

Then add the server to your client.

Claude Desktop (claude_desktop_config.json), Cursor (.cursor/mcp.json) and most clients:

json
{  "mcpServers": {    "stablevoy": { "command": "npx", "args": ["-y", "stablevoy-mcp"] }  }}

Claude Code:

sh
claude mcp add stablevoy -- npx -y stablevoy-mcp

One store without a login

Create a key on the store page of the dashboard and pass it instead:

json
{  "mcpServers": {    "stablevoy": { "command": "npx", "args": ["-y", "stablevoy-mcp"], "env": { "STABLEVOY_API_KEY": "sk_live_..." } }  }}

Read-only

Add "STABLEVOY_MCP_READ_ONLY": "true" to env: create_invoice is then not offered at all.

Change the stores

  • npx stablevoy-mcp login again: the stores this computer has are ticked; untick the ones to drop. Their keys are revoked, the new selection replaces the old one.
  • npx stablevoy-mcp stores lists the stores of this computer; npx stablevoy-mcp stores remove "Main" drops one and revokes its key.
  • npx stablevoy-mcp logout revokes every key of this computer and deletes the file.

Adding a store always goes through the browser, since it needs your wallet. The assistant cannot change the set. Several accounts or sets: --profile work on these commands, and "STABLEVOY_MCP_PROFILE": "work" in the client config.

Tools

ToolWhat it does
list_storesThe connected stores, whether each can take payments and its EVM payout status.
get_storeA store's settings: networks, payout addresses, the EVM payout status, invoice limits, fee, website, return and webhook URLs. Read only.
create_invoiceAn invoice for an amount in dollars ("19.99"), with an optional reference and return URL; returns the payment link. The same amount and reference return the same invoice instead of a second one.
get_invoiceAn invoice by id, with the payments received.
list_invoicesInvoices newest first, filtered by status, source, search and the days they were created.

With several stores, tools take a store argument (the id or the exact name from list_stores); the server asks for it rather than guessing.

Configuration

VariableMeaning
STABLEVOY_API_KEYOne store key; when set, the login keys are not used.
STABLEVOY_MCP_PROFILEWhich login profile to use, default by default.
STABLEVOY_MCP_READ_ONLYtrue leaves create_invoice out.
STABLEVOY_API_URLThe API, https://api.stablevoy.com by default.

License

MIT

Source: README.md at commit 5e30d0f

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not start.

Version history

1
  1. v0.1.1LatestNov 6, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts