Skip to main content
Glama

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

TypeScript

npm i -g @algovoi/mcp-server

npx -y @algovoi/mcp-server

Python

pip install algovoi-mcp

uvx algovoi-mcp o algovoi-mcp

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

create_payment_link

URL de pago alojada para un importe + cadena determinados

2

verify_payment

Verifica un token de pago (opcionalmente con un tx_id)

3

prepare_extension_payment

Parámetros de flujo de billetera en página (Algorand / VOI)

4

verify_webhook

Verificación de firma HMAC-SHA256 para webhooks de AlgoVoi

5

list_networks

Cadenas compatibles + IDs de activos (sin conexión, sin llamada a API)

Herramientas de desafío de protocolo

#

Herramienta

Qué hace

6

generate_mpp_challenge

Cabeceras WWW-Authenticate de IETF MPP 402 + challenge_id

7

verify_mpp_receipt

Verifica un recibo MPP en cadena (indexador directo, sin llamada a API)

8

verify_x402_proof

Verifica una prueba de pago x402 en base64 (indexador directo)

9

generate_x402_challenge

Cabeceras 402 X-Payment-Required + carga útil

10

generate_ap2_mandate

PaymentMandate de AP2 v0.1 para flujos de pago de agentes de IA

11

verify_ap2_payment

Verifica un recibo de pago de mandato AP2 (indexador directo)

Herramientas de agente A2A (nuevo en v1.2.0)

#

Herramienta

Qué hace

12

fetch_agent_card

GET {agent_url}/.well-known/agent.json — descubre las capacidades y requisitos de pago de un agente A2A antes de llamarlo

13

send_a2a_message

POST {agent_url}/message:send — llama a un agente A2A v1.0 con pago restringido; devuelve el resultado de la tarea en 200, o challenge_headers en 402 para que Claude pueda pagar y reintentar

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 returned

Redes 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

ALGOVOI_API_KEY

✅

Clave de API algv_... del panel de AlgoVoi

ALGOVOI_TENANT_ID

✅

UUID de inquilino del panel de AlgoVoi

ALGOVOI_PAYOUT_ALGORAND

✅*

Dirección de billetera de pago de Algorand

ALGOVOI_PAYOUT_VOI

✅*

Dirección de billetera de pago de VOI

ALGOVOI_PAYOUT_HEDERA

✅*

Cuenta de pago de Hedera (ej. 0.0.123456)

ALGOVOI_PAYOUT_STELLAR

✅*

Dirección de pago de Stellar (G...)

ALGOVOI_PAYOUT_ADDRESS

—

Alternativa universal si no se establecen las variables por cadena

ALGOVOI_WEBHOOK_SECRET

—

Para verify_webhook

ALGOVOI_API_BASE

—

Sobrescribe la URL base de la API de AlgoVoi (predeterminado: https://cloud.algovoi.co.uk)

* 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.json

  • Cursor: ~/.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.py

Licenciado bajo la Business Source License 1.1.

Available Tools

11 tools
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

    A4/5.0

    Scored across 11 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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

    ActivityMaintained
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A 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
    • A
      license
      A
      quality
      D
      maintenance
      Keyless 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).
      3
      88 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An 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 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Payment 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.
      13
      348 npm
      1
      MIT