AlgoVoi MCP Server
Servidor MCP AlgoVoi
Un servidor MCP (Model Context Protocol) que expone la infraestructura de pagos de AlgoVoi como herramientas que cualquier cliente MCP puede llamar: Claude Desktop, Claude Code, Cursor, Windsurf o cualquier otro asistente compatible con MCP.
Se distribuye en dos paquetes:
Paquete | Instalación | Comando |
|
| |
|
|
Ambos exponen las mismas 13 herramientas y la misma superficie de API; elige el entorno de ejecución que prefiera tu cliente.
13 herramientas
Herramientas de pago
# | Herramienta | Qué hace |
1 |
| URL de pago alojada para un importe + cadena determinados |
2 |
| Verifica un token de pago (opcionalmente con un tx_id) |
3 |
| Parámetros de flujo de billetera en página (Algorand / VOI) |
4 |
| Verificación de firma HMAC-SHA256 para webhooks de AlgoVoi |
5 |
| Cadenas compatibles + IDs de activos (sin conexión, sin llamada a API) |
Herramientas de desafío de protocolo
# | Herramienta | Qué hace |
6 |
| Cabeceras |
7 |
| Verifica un recibo MPP en cadena (indexador directo, sin llamada a API) |
8 |
| Verifica una prueba de pago x402 en base64 (indexador directo) |
9 |
| Cabeceras 402 |
10 |
|
|
11 |
| Verifica un recibo de pago de mandato AP2 (indexador directo) |
Herramientas de agente A2A (nuevo en v1.2.0)
# | Herramienta | Qué hace |
12 |
|
|
13 |
|
|
Flujo de pago y llamada A2A
1. fetch_agent_card("https://agent.example.com")
→ see agent costs $0.01, accepts MPP on Algorand
2. send_a2a_message(agent_url, "What is the price of ALGO?")
→ payment_required: true, challenge_headers: {WWW-Authenticate: ...}
3. generate_mpp_challenge(...) ← use tool #6
→ user pays on-chain
4. send_a2a_message(agent_url, text, payment_proof="<proof>")
→ task result returnedRedes compatibles: Algorand, VOI, Hedera, Stellar (USDC en las cuatro + ALGO/VOI/HBAR/XLM nativos).
Related MCP server: ShieldZ Crypto Payments
Dos formas de conectar
Opción A — AlgoVoi Cloud (recomendado)
AlgoVoi Cloud es el plano de control para todas tus integraciones: WooCommerce, Zapier, n8n y MCP, todo en un mismo panel. Apunta ALGOVOI_API_BASE a https://cloud.algovoi.co.uk y tu única clave de API algv_... cubre todas las integraciones; no se necesita ID de inquilino ni direcciones de pago (se almacenan en el panel).
{
"mcpServers": {
"algovoi": {
"command": "npx",
"args": ["-y", "@algovoi/mcp-server"],
"env": {
"ALGOVOI_API_KEY": "algv_...",
"ALGOVOI_API_BASE": "https://cloud.algovoi.co.uk"
}
}
}
}Cada pago que crea Claude aparece en tu panel de Cloud junto con los pagos de cualquier otra plataforma. Un solo lugar para verlo todo.
Regístrate gratis en dash.algovoi.co.uk.
Opción B — AlgoVoi directo
Conéctate directamente a la API de AlgoVoi con tu clave algv_... y tu ID de inquilino.
Ambos paquetes leen las mismas variables de entorno:
Variable | Requerido | Propósito |
| ✅ | Clave de API |
| ✅ | UUID de inquilino del panel de AlgoVoi |
| ✅* | Dirección de billetera de pago de Algorand |
| ✅* | Dirección de billetera de pago de VOI |
| ✅* | Cuenta de pago de Hedera (ej. |
| ✅* | Dirección de pago de Stellar ( |
| — | Alternativa universal si no se establecen las variables por cadena |
| — | Para |
| — | Sobrescribe la URL base de la API de AlgoVoi (predeterminado: |
* Se requiere al menos una dirección por cadena (o ALGOVOI_PAYOUT_ADDRESS como alternativa).
La autenticación es solo mediante variables de entorno. Los secretos nunca pasan a través de los argumentos de la herramienta; el cliente MCP nunca ve la clave de API.
Regístrate en www.algovoi.co.uk para obtener tu clave de API e ID de inquilino.
{
"mcpServers": {
"algovoi": {
"command": "npx",
"args": ["-y", "@algovoi/mcp-server"],
"env": {
"ALGOVOI_API_KEY": "algv_...",
"ALGOVOI_TENANT_ID": "...",
"ALGOVOI_PAYOUT_ALGORAND": "<your-algorand-address>",
"ALGOVOI_PAYOUT_VOI": "<your-voi-address>",
"ALGOVOI_PAYOUT_HEDERA": "0.0.<your-account>",
"ALGOVOI_PAYOUT_STELLAR": "G<your-stellar-address>"
}
}
}
}Para el paquete de Python, cambia a "command": "uvx", "args": ["algovoi-mcp"].
Ubicaciones de los archivos de configuración:
Claude Desktop:
~/Library/Application Support/Claude/claude_desktop_config.json(macOS),%APPDATA%\Claude\claude_desktop_config.json(Windows)Claude Code:
~/.claude.jsonCursor:
~/.cursor/mcp.json
Pruebas
# TypeScript unit tests (77/77)
cd typescript && npm test
# Python unit tests (85/85)
cd python && pytest
# Stdio integration smoke — boots both servers and confirms all 13 tools list
python smoke_stdio.pyLicenciado bajo la Business Source License 1.1.
Available Tools
11 toolscreate_payment_linkA
Create a hosted AlgoVoi checkout URL for a given amount and chain. Returns a short token and public URL the customer can visit to pay in USDC or native tokens (Algorand / VOI / Hedera / Stellar).
Inputs: amount (required), currency (required), label (required), network (required), +2 more.
generate_ap2_mandateA
Generate an AP2 v0.1 PaymentMandate for agent-to-agent payment. Returns the mandate object and its base64 encoding for the AP2-Payment-Required header. After the paying agent submits on-chain, call verify_ap2_payment to confirm.
Inputs: resource_id (required), amount_microunits (required), network, expires_in_seconds, +1 more.
generate_mpp_challengeA
Generate an IETF MPP (draft-ryan-httpauth-payment) 402 challenge that an API server can return to gate a resource. Produces the WWW-Authenticate and X-Payment-Required headers plus the challenge_id to echo.
Inputs: resource_id (required), amount_microunits (required), networks, expires_in_seconds.
generate_x402_challengeA
Generate an x402 (spec v1) 402 Payment Required response for gating a resource. Returns the X-Payment-Required header value and full payload. The client must pay on-chain and re-send with X-Payment: , then verify with verify_x402_proof.
Inputs: resource (required), amount_microunits (required), network, expires_in_seconds, +1 more.
list_networksA
List the blockchain networks AlgoVoi supports, with asset IDs, decimals, and CAIP-2 identifiers. Offline tool — no API call.
Inputs: no named parameters.
prepare_extension_paymentA
Prepare an in-page wallet-extension payment (Algorand / VOI only). Returns the token and chain parameters a frontend can use to ask a browser wallet to sign and submit the transfer, then verify with verify_payment + tx_id.
Inputs: amount (required), currency (required), label (required), network (required).
verify_ap2_paymentA
Verify an AP2 payment — returns {verified: true} if the on-chain transaction satisfies the mandate's amount and recipient.
Inputs: mandate_id (required), tx_id (required), network (required).
verify_mpp_receiptB
Verify an MPP receipt (on-chain transaction ID) for a given resource — returns {verified: true} if the transaction paid the resource's declared amount to the tenant's payout address.
Inputs: resource_id (required), tx_id (required), network (required).
verify_paymentA
Verify that a payment for a given checkout token has settled. Returns paid/unpaid status. If tx_id is supplied, verifies that specific on-chain transaction; otherwise uses hosted-checkout status.
Inputs: token (required), tx_id.
verify_webhookA
Verify an AlgoVoi webhook HMAC-SHA256 signature. Returns {valid: true, payload: } if the signature matches the server's configured webhook secret (ALGOVOI_WEBHOOK_SECRET env var — never passed as a tool argument).
Inputs: raw_body (required), signature (required).
verify_x402_proofA
Verify a base64-encoded x402 payment proof against a given network — returns {verified: true} if the proof corresponds to a confirmed on-chain transfer to the tenant's payout address.
Inputs: proof (required), network (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Most tools have distinct purposes, such as create_payment_link for hosted checkout and generate_ap2_mandate for agent-to-agent payments. However, the three challenge-generation tools (generate_ap2_mandate, generate_mpp_challenge, generate_x402_challenge) could be confusing due to overlapping concepts of payment challenges, though their specific protocols help differentiate them.
All tool names follow a consistent verb_noun pattern with snake_case, such as create_payment_link, verify_payment, and list_networks. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.
With 11 tools, the server is well-scoped for handling blockchain payments and verifications. Each tool serves a clear function, such as payment creation, verification, and network listing, without feeling excessive or insufficient for the domain of payment processing and validation.
The tool set provides comprehensive coverage for the payment domain, including creation (e.g., create_payment_link), verification (e.g., verify_payment, verify_ap2_payment), and support tools (e.g., list_networks, verify_webhook). There are no obvious gaps, as it covers multiple payment protocols and lifecycle stages from initiation to confirmation.
Maintenance
Related MCP Connectors
Agent Commerce Protocol MCP — bridges Stripe ACP + Google AP2 + Coinbase x402 for agent payments
Pay-per-action access to APIs and MCP tools over Lightning L402 and Base USDC x402.
Billing proxy for MCP servers. Adds Stripe and x402 crypto payments without writing billing code.
Solana-native MCP gateway for SAP, DeFi tools, SNS identity, and x402 payments.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA comprehensive Model Context Protocol (MCP) server providing 50+ tools for Algorand blockchain development, including account management, asset operations, smart contracts, API integration, swap functionality, and advanced transaction capabilities.ISC
- AlicenseAqualityDmaintenanceKeyless crypto payments for AI agents. One MCP call turns any wallet address into a non-custodial crypto payment link or tip jar, no API key and no account, with funds settling straight to your wallet at a 0% platform fee (USDC/USDT, BTC, LTC, DASH, DOGE, ZCASH).388 npmMIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server for agentic commerce, enabling AI agents to discover services, make x402 payments with USDC across multiple chains, and manage crypto wallets and token swaps.598 npm1MIT
- AlicenseAqualityBmaintenancePayment infrastructure MCP server enabling AI agents to make gasless USDC payments on Base and JIT single-use virtual card checkouts, with zero-trust card handling, merchant checkout hints, and signed receipts.13348 npm1MIT