AlgoVoi MCP Server
AlgoVoi MCP-Server
Ein MCP (Model Context Protocol)-Server, der die Zahlungsinfrastruktur von AlgoVoi als Tools bereitstellt, die von jedem MCP-Client aufgerufen werden können — Claude Desktop, Claude Code, Cursor, Windsurf oder jeder andere MCP-kompatible Assistent.
Erhältlich als zwei Pakete:
Paket | Installation | Befehl |
|
| |
|
|
Beide stellen die gleichen 13 Tools und die gleiche API-Oberfläche bereit — wählen Sie die Laufzeitumgebung, die Ihr Client bevorzugt.
13 Tools
Zahlungs-Tools
# | Tool | Was es tut |
1 |
| Gehostete Checkout-URL für einen bestimmten Betrag + Chain |
2 |
| Verifiziert ein Checkout-Token (optional mit einer tx_id) |
3 |
| In-Page Wallet-Flow-Parameter (Algorand / VOI) |
4 |
| HMAC-SHA256-Signaturprüfung für AlgoVoi-Webhooks |
5 |
| Unterstützte Chains + Asset-IDs (offline, kein API-Aufruf) |
Protokoll-Challenge-Tools
# | Tool | Was es tut |
6 |
| IETF MPP 402 |
7 |
| Verifiziert einen MPP On-Chain-Beleg (direkter Indexer, kein API-Aufruf) |
8 |
| Verifiziert einen x402 base64-Zahlungsnachweis (direkter Indexer) |
9 |
| x402 |
10 |
| AP2 v0.1 |
11 |
| Verifiziert einen AP2-Mandats-Zahlungsbeleg (direkter Indexer) |
A2A-Agenten-Tools (neu in v1.2.0)
# | Tool | Was es tut |
12 |
|
|
13 |
|
|
A2A Pay-and-Call-Ablauf
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 returnedUnterstützte Netzwerke: Algorand, VOI, Hedera, Stellar (USDC auf allen vier + natives ALGO/VOI/HBAR/XLM).
Related MCP server: ShieldZ Crypto Payments
Zwei Möglichkeiten zur Verbindung
Option A — AlgoVoi Cloud (empfohlen)
AlgoVoi Cloud ist die Steuerungsebene für alle Ihre Integrationen — WooCommerce, Zapier, n8n und MCP in einem einzigen Dashboard. Richten Sie ALGOVOI_API_BASE auf https://cloud.algovoi.co.uk ein und Ihr einzelner algv_... API-Schlüssel deckt jede Integration ab — keine Mandanten-ID oder Auszahlungsadressen erforderlich (diese werden im Dashboard gespeichert).
{
"mcpServers": {
"algovoi": {
"command": "npx",
"args": ["-y", "@algovoi/mcp-server"],
"env": {
"ALGOVOI_API_KEY": "algv_...",
"ALGOVOI_API_BASE": "https://cloud.algovoi.co.uk"
}
}
}
}Jede Zahlung, die Claude erstellt, erscheint in Ihrem Cloud-Dashboard neben Zahlungen von jeder anderen Plattform. Alles an einem Ort im Blick.
Registrieren Sie sich kostenlos unter dash.algovoi.co.uk.
Option B — AlgoVoi direkt
Verbinden Sie sich direkt mit der AlgoVoi-API mit Ihrem algv_...-Schlüssel und Ihrer Mandanten-ID.
Beide Pakete lesen die gleichen Umgebungsvariablen:
Variable | Erforderlich | Zweck |
| ✅ |
|
| ✅ | Mandanten-UUID aus dem AlgoVoi-Dashboard |
| ✅* | Algorand-Auszahlungs-Wallet-Adresse |
| ✅* | VOI-Auszahlungs-Wallet-Adresse |
| ✅* | Hedera-Auszahlungskonto (z. B. |
| ✅* | Stellar-Auszahlungsadresse ( |
| — | Universeller Fallback, falls keine Chain-spezifischen Variablen gesetzt sind |
| — | Für |
| — | Überschreibt die AlgoVoi-API-Basis-URL (Standard: |
* Mindestens eine Adresse pro Chain (oder ALGOVOI_PAYOUT_ADDRESS als Fallback) ist erforderlich.
Die Authentifizierung erfolgt nur über Umgebungsvariablen. Geheimnisse werden niemals über Tool-Argumente übergeben — der MCP-Client sieht den API-Schlüssel niemals.
Registrieren Sie sich unter www.algovoi.co.uk, um Ihren API-Schlüssel und Ihre Mandanten-ID zu erhalten.
{
"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>"
}
}
}
}Für das Python-Paket tauschen Sie "command": "uvx", "args": ["algovoi-mcp"] aus.
Speicherorte der Konfigurationsdatei:
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
Testen
# 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.pyLizenziert unter der 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