AlgoVoi MCP Server
AlgoVoi MCPサーバー
MCP (Model Context Protocol)サーバーであり、AlgoVoiの決済インフラをClaude Desktop、Claude Code、Cursor、Windsurf、その他MCP互換アシスタントなどのあらゆるMCPクライアントから呼び出せるツールとして公開します。
2つのパッケージで提供されています:
パッケージ | インストール | コマンド |
|
| |
|
|
どちらも同じ13種類のツールとAPIインターフェースを提供します。クライアントが好むランタイムを選択してください。
13種類のツール
決済ツール
# | ツール | 機能 |
1 |
| 指定した金額とチェーンのホスト型チェックアウトURL |
2 |
| チェックアウトトークンの検証(オプションでtx_idを指定可能) |
3 |
| ページ内ウォレットフローのパラメータ(Algorand / VOI) |
4 |
| AlgoVoi Webhook用のHMAC-SHA256署名チェック |
5 |
| サポートされているチェーンとアセットID(オフライン、API呼び出しなし) |
プロトコルチャレンジツール
# | ツール | 機能 |
6 |
| IETF MPP 402 |
7 |
| MPPオンチェーンレシートの検証(直接インデクサー、API呼び出しなし) |
8 |
| x402 base64決済証明の検証(直接インデクサー) |
9 |
| x402 |
10 |
| AIエージェント決済フロー用のAP2 v0.1 |
11 |
| AP2委任決済レシートの検証(直接インデクサー) |
A2Aエージェントツール (v1.2.0で新機能)
# | ツール | 機能 |
12 |
|
|
13 |
|
|
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サポートされているネットワーク: Algorand、VOI、Hedera、Stellar(4つすべてでUSDC + ネイティブのALGO/VOI/HBAR/XLM)。
Related MCP server: ShieldZ Crypto Payments
接続方法
オプションA — AlgoVoi Cloud(推奨)
AlgoVoi Cloudは、WooCommerce、Zapier、n8n、MCPなど、すべての統合を1つのダッシュボードで管理するコントロールプレーンです。ALGOVOI_API_BASE を https://cloud.algovoi.co.uk に設定し、単一の algv_... APIキーを使用すれば、すべての統合をカバーできます。テナントIDや支払い用アドレスを個別に設定する必要はありません(ダッシュボードに保存されます)。
{
"mcpServers": {
"algovoi": {
"command": "npx",
"args": ["-y", "@algovoi/mcp-server"],
"env": {
"ALGOVOI_API_KEY": "algv_...",
"ALGOVOI_API_BASE": "https://cloud.algovoi.co.uk"
}
}
}
}Claudeが作成したすべての決済は、他のプラットフォームからの決済とともにクラウドダッシュボードに表示されます。すべてを一元管理できます。
dash.algovoi.co.ukから無料で登録してください。
オプションB — AlgoVoi直接接続
algv_... キーとテナントIDを使用して、AlgoVoi APIに直接接続します。
両方のパッケージで同じ環境変数を読み取ります:
変数 | 必須 | 用途 |
| ✅ | AlgoVoiダッシュボードの |
| ✅ | AlgoVoiダッシュボードのテナントUUID |
| ✅* | Algorand支払い用ウォレットアドレス |
| ✅* | VOI支払い用ウォレットアドレス |
| ✅* | Hedera支払い用アカウント (例: |
| ✅* | Stellar支払い用アドレス ( |
| — | チェーンごとの変数が設定されていない場合の汎用フォールバック |
| — |
|
| — | AlgoVoi APIベースURLのオーバーライド (デフォルト: |
* チェーンごとのアドレス(またはフォールバックとしての ALGOVOI_PAYOUT_ADDRESS)が少なくとも1つ必要です。
認証は環境変数のみで行われます。 シークレットがツール引数として渡されることはなく、MCPクライアントがAPIキーを見ることはありません。
www.algovoi.co.ukで登録して、APIキーとテナントIDを取得してください。
{
"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>"
}
}
}
}Pythonパッケージの場合は、"command": "uvx", "args": ["algovoi-mcp"] に置き換えてください。
設定ファイルの場所:
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
テスト
# 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.pyBusiness 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