Toreador

io.toreadorPublished by toreador.iov0.2.6Updated Oct 24, 2026

Generate crypto QR codes (BTC, ETH, SOL, USDC, USDT, EURC) and manage payment sessions.

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Toreador's local MCP server lets an assistant generate crypto payment QR codes and create and track hosted stablecoin payment sessions.

What you can do
  • Generate QR codes for native tokens (BTC, ETH, SOL, POL) and USDC on Solana, returning the payment URI and a base64 PNG data URI
  • Create hosted ERC-20 payment sessions for USDC, USDT and EURC on Ethereum, Polygon or Base, returning a session ID, security code and payment URL
  • Poll the status of a payment session (pending, submitted, confirming, completed, expired, failed)
  • List the 50 most recent QR code generations and the 50 most recent payment sessions
When to use it
Useful when you want an assistant to prepare crypto payment requests inside a chat — producing a scannable QR code for a wallet address and amount, or opening a hosted stablecoin checkout session and checking whether it has been paid.
Requirements
Runs locally over stdio, typically launched with npx from the npm package, so Node.js is needed. Requires a Pro plan Toreador API key in the TOREADOR_API_KEY environment variable. Optional TOREADOR_BASE_URL and TOREADOR_TIMEOUT_MS settings. Outbound HTTPS access to toreador.io.
Before you install
The API key (TOREADOR_API_KEY) is a paid-plan credential and is sent in outbound HTTPS calls to toreador.io. Tools create payment objects and hosted payment URLs, so an assistant can start real payment requests; review amounts and destination addresses before confirming. No delete or refund tools exist, and the server is described as non-custodial, but it does not verify that an address belongs to you.

Installation

In SourceWeft

  1. Open Toreador 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

@toreador/mcp-server

Official Model Context Protocol server for Toreador. Lets Claude Desktop, Cursor, and any other MCP-capable assistant generate crypto QR codes and manage payment sessions on your behalf.

[toreador-mcp-server MCP server]

⚠️ Requires a Pro plan API key (tdr_...) from your Toreador dashboard. The MCP server runs locally and uses your key to call https://toreador.io/api/v1/public.

Tools exposed

ToolWhat it does
toreador_generate_qrGenerate a QR code for native tokens (BTC, ETH, SOL, POL) or Solana SPL (USDC on Solana). Returns the on-chain payment URI and a base64 PNG data URI.
toreador_create_sessionCreate a hosted payment session for ERC-20 stablecoins (USDC, USDT, EURC) on Ethereum, Polygon or Base. Returns a session ID, security code and a hosted payment URL.
toreador_get_payment_statusPoll the status of an ERC-20 payment session: pending / submitted / confirming / completed / expired / failed.
toreador_list_historyList the 50 most recent QR code generations.
toreador_list_sessionsList the 50 most recent ERC-20 payment sessions.

Install in Claude Desktop

Edit Claude Desktop's config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%/Claude/claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json

Add the toreador entry under mcpServers:

json
{  "mcpServers": {    "toreador": {      "command": "npx",      "args": ["-y", "@toreador/mcp-server"],      "env": {        "TOREADOR_API_KEY": "tdr_your_key_here"      }    }  }}

Restart Claude Desktop. You should see the 5 Toreador tools in the tools menu.

Install in Cursor

In Cursor settings → MCP → "Add new MCP server", paste:

json
{  "command": "npx",  "args": ["-y", "@toreador/mcp-server"],  "env": { "TOREADOR_API_KEY": "tdr_..." }}

Example prompts

Once installed, try these prompts in your MCP client:

  • "Generate a Bitcoin QR code for 0.001 BTC to bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh."
  • "Create a USDC payment session for 50 USDC on Polygon to 0x742d35Cc6634C0532925a3b844Bc9e7595f2bD18."
  • "What's the status of session ses_123?"
  • "Show me my last 10 payment sessions."

The assistant will pick the right tool, call Toreador, and return the result — including the QR code data URI which most clients can render inline.

Configuration

Environment variableDefaultDescription
TOREADOR_API_KEYrequiredYour Pro plan API key. Format: tdr_....
TOREADOR_BASE_URLhttps://toreador.io/api/v1/publicOverride the API base URL (useful for testing).
TOREADOR_TIMEOUT_MS30000Per-request timeout in milliseconds.

Trust and safety

  • Local only. The MCP server runs on your machine via stdio. Your API key never leaves your computer except in outbound HTTPS calls to toreador.io.
  • Non-custodial. Toreador never holds funds. The MCP tools only generate QR codes and read session state — they cannot move money.
  • Read or create, no destruction. Tools either generate new payment objects or read existing ones. There is no "delete" or "refund" tool.

Build from source

bash
git clone https://github.com/Bentonabento/toreador-sdk.gitcd toreador-sdk/mcpnpm installnpm run buildTOREADOR_API_KEY=tdr_... node dist/index.js

The server will boot, print [toreador-mcp] ready (5 tools registered) to stderr, and wait for MCP requests on stdin.

License

MIT

Source: README.md at commit 355bf75

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.6LatestSep 16, 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