AlgoVoi MCP Server
AlgoVoi MCP 서버
MCP (Model Context Protocol) 서버로, AlgoVoi의 결제 인프라를 Claude Desktop, Claude Code, Cursor, Windsurf 또는 기타 MCP 호환 어시스턴트와 같은 모든 MCP 클라이언트가 호출할 수 있는 도구로 노출합니다.
두 가지 패키지로 제공됩니다:
패키지 | 설치 | 명령어 |
|
| |
|
|
두 패키지 모두 동일한 13개의 도구와 동일한 API 인터페이스를 제공하므로, 클라이언트가 선호하는 런타임을 선택하세요.
13개의 도구
결제 도구
# | 도구 | 기능 |
1 |
| 특정 금액 및 체인에 대한 호스팅된 결제 URL 생성 |
2 |
| 결제 토큰 검증 (선택적으로 tx_id 포함) |
3 |
| 인페이지 지갑 흐름 매개변수 (Algorand / VOI) |
4 |
| AlgoVoi 웹훅을 위한 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 등 모든 통합을 위한 제어 평면입니다. 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가 생성하는 모든 결제는 다른 플랫폼의 결제와 함께 Cloud 대시보드에 표시됩니다. 한곳에서 모든 것을 확인할 수 있습니다.
dash.algovoi.co.uk에서 무료로 가입하세요.
옵션 B — AlgoVoi 직접 연결
algv_... 키와 테넌트 ID를 사용하여 AlgoVoi API에 직접 연결합니다.
두 패키지 모두 동일한 환경 변수를 읽습니다:
변수 | 필수 | 목적 |
| ✅ | AlgoVoi 대시보드의 |
| ✅ | AlgoVoi 대시보드의 테넌트 UUID |
| ✅* | Algorand 지급 지갑 주소 |
| ✅* | VOI 지급 지갑 주소 |
| ✅* | Hedera 지급 계정 (예: |
| ✅* | Stellar 지급 주소 ( |
| — | 체인별 변수가 설정되지 않은 경우의 범용 대체 주소 |
| — |
|
| — | AlgoVoi API 기본 URL 재정의 (기본값: |
***** 체인별 주소 중 최소 하나(또는 대체용 ALGOVOI_PAYOUT_ADDRESS)가 필요합니다.
인증은 환경 변수로만 수행됩니다. 비밀 정보는 도구 인수를 통해 전달되지 않으며, 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