AlgoVoi MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALGOVOI_API_KEY | Yes | Your AlgoVoi API key (starts with algv_). Get one from https://dash.algovoi.co.uk | |
| ALGOVOI_API_BASE | No | API base URL. Default https://cloud.algovoi.co.uk (AlgoVoi Cloud, managed payouts). Change to https://api1.ilovechicken.co.uk for direct API access. | https://cloud.algovoi.co.uk |
| ALGOVOI_TENANT_ID | No | Tenant UUID. Required only for direct API access (when ALGOVOI_API_BASE is api1.ilovechicken.co.uk). Leave unset when using AlgoVoi Cloud. | |
| ALGOVOI_PAYOUT_VOI | No | Per-chain override: VOI payout address (direct API only). | |
| ALGOVOI_PAYOUT_HEDERA | No | Per-chain override: Hedera payout address, e.g. 0.0.123456 (direct API only). | |
| ALGOVOI_PAYOUT_ADDRESS | No | Default payout wallet address. Required only for direct API access; managed centrally in AlgoVoi Cloud otherwise. | |
| ALGOVOI_PAYOUT_STELLAR | No | Per-chain override: Stellar public key, starts with G (direct API only). | |
| ALGOVOI_WEBHOOK_SECRET | No | Optional HMAC-SHA256 secret for webhook signature verification. Enables the verify_webhook tool. | |
| ALGOVOI_PAYOUT_ALGORAND | No | Per-chain override: Algorand payout address (direct API only). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_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). |
| 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. |
| 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. |
| 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). |
| list_networksA | List the blockchain networks AlgoVoi supports, with asset IDs, decimals, and CAIP-2 identifiers. Offline tool — no API call. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| verify_ap2_paymentA | Verify an AP2 payment — returns {verified: true} if the on-chain transaction satisfies the mandate's amount and recipient. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.