toreador-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOREADOR_API_KEY | Yes | Your Pro plan API key. Format: tdr_... | |
| TOREADOR_BASE_URL | No | Override the API base URL (useful for testing). | https://toreador.io/api/v1/public |
| TOREADOR_TIMEOUT_MS | No | Per-request timeout in milliseconds. | 30000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| toreador_generate_qrA | Generate a crypto QR code for a native token (BTC, ETH, SOL, POL) or a Solana SPL token (USDC on Solana). Returns the QR data URI (PNG base64) and the on-chain payment URI (BIP21, EIP-681, Solana Pay). FREE — no API key needed for these chains. For ERC-20 stablecoins on Ethereum/Polygon/Base (USDT, USDC, EURC), use toreador_create_session (Pro plan required). |
| toreador_create_sessionA | Create a hosted payment session for ERC-20 stablecoins on EVM chains (USDC, USDT, EURC on Ethereum, Polygon or Base). Returns a session ID, a 6-character security code to display to the payer, and a URL to a Toreador-hosted payment page where the payer connects their wallet. Sessions expire 15 minutes after creation. PRO PLAN REQUIRED. For native tokens or Solana SPL, use toreador_generate_qr instead. |
| toreador_get_payment_statusA | Get the current status of an ERC-20 payment session by ID. Status values: pending, submitted, confirming, completed, expired, failed. Includes on-chain confirmation count and tx hash once submitted. |
| toreador_list_historyA | List the 50 most recent QR code generations for the authenticated account. Returns a list of payment requests with token, chain, amount, recipient and timestamp. |
| toreador_list_sessionsA | List the 50 most recent ERC-20 payment sessions for the authenticated account. Includes status, tx hash, confirmations and timestamps. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: creating sessions for ERC-20 stablecoins, generating QR codes for native tokens, checking session status, listing QR history, and listing sessions. No overlap or ambiguity.
All tool names follow a consistent 'toreador_verb_noun' pattern (e.g., create_session, generate_qr, get_payment_status, list_history, list_sessions). Verbs and nouns are clearly chosen and consistent.
With 5 tools, the server is well-scoped for its purpose of handling crypto payments. It covers creation, generation, status checks, and history listing without being overly numerous or sparse.
The tool set covers ERC-20 sessions well (create, status, list) but lacks a status checker for QR-generated payments (native tokens/SPL). This is a notable gap that could cause agents to be unable to confirm payment completion for those types.