New:Microsoft Teams Notifications Are Now Available in Socket.Learn more
Get Started

@algovoi/mcp-server

Package Overview
Dependencies
Maintainers
1
Versions
13
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@algovoi/mcp-server

MCP server for AlgoVoi — create crypto payment links, verify payments, probe MPP endpoints (including MPP subscription lifecycle), screen recipients, compliance trust queries, and generate MPP / x402 challenges from any MCP client. Supports 29 tools acros

latest
Source
npmnpm
Version
1.7.0
Version published
Weekly downloads
28
-36.36%
Maintainers
1
Weekly downloads
 
Created
Source

AlgoVoi MCP Server

An MCP (Model Context Protocol) server that exposes AlgoVoi's payment infrastructure as tools any MCP client can call — Claude Desktop, Claude Code, Cursor, Windsurf, or any other MCP-compatible assistant.

Ships as two packages:

PackageInstallCommand
TypeScriptnpm i -g @algovoi/mcp-servernpx -y @algovoi/mcp-server
Pythonpip install algovoi-mcpuvx algovoi-mcp or algovoi-mcp

Both expose the same 29 tools and the same API surface — pick whichever runtime your client prefers.

29 tools

#ToolWhat it does
1create_payment_linkHosted-checkout URL for a given amount + chain
2verify_paymentVerify a checkout token (optionally with a tx_id)
3prepare_extension_paymentIn-page wallet-flow params (Algorand / VOI)
4verify_webhookHMAC-SHA256 signature check for AlgoVoi webhooks
5list_networksSupported chains + asset IDs (offline, no API call)
6generate_mpp_challengeIETF MPP 402 WWW-Authenticate headers + challenge_id
7verify_mpp_receiptVerify an MPP on-chain receipt
8verify_x402_proofVerify an x402 base64 payment proof
9generate_x402_challengex402 X-Payment-Required 402 headers + payload
10generate_ap2_mandateAP2 v0.1 PaymentMandate for AI agent payment flows
11verify_ap2_paymentVerify an AP2 mandate payment receipt
12try_mpp_endpointProbe any URL for MPP/x402 payment requirements
13discover_resourcesBrowse the public AlgoVoi payment resource catalogue
14screen_recipientCompliance screen a wallet address (sanctions / risk)
15get_compliance_attestationFetch AlgoVoi's live compliance posture document
16compliance_trust_queryComposite trust verdict (TRUSTED/PROVISIONAL/UNTRUSTED) over a chain of substrate receipts
17try_mpp_subscriptionProbe an MPP subscription URL; parse the 402 subscription terms
18list_mpp_subscriptionsList a tenant's MPP subscriptions
19cancel_mpp_subscriptionCancel an active MPP subscription
20–29(Tier 2 recurring authorities)create_recurring_authority, get_authority, list_authorities, confirm_authority, revoke_authority, pause_authority, resume_authority, manual_pull + protocol helpers

Supported networks: Algorand, VOI, Hedera, Stellar, Base, Solana, Tempo (USDC on all seven).

Response model — ALGOVOI_MODE

Set ALGOVOI_MODE to choose how much detail tool results carry:

ModeBehaviour
substrate (default)Tools return AlgoVoi substrate primitives — action_ref, Ed25519-signed compliance_receipt / settlement_attestation, and the composite trust-query hash + signed ctq_response.
standardThose substrate-only keys are stripped, leaving the bare x402 / MPP / AP2 standard response shape. The verdict fields (verdict, reasons, trust_outcome, paid) are preserved.

The underlying API always returns substrate fields (they are additive) — standard simply filters them client-side, so you can A/B the two models by flipping one env var.

Two ways to connect

AlgoVoi Cloud is the control plane for all your integrations — WooCommerce, Zapier, n8n, and MCP all in one dashboard. Point ALGOVOI_API_BASE at https://cloud.algovoi.co.uk and your single algv_... API key covers every integration — no tenant ID or payout addresses needed (they're stored in the dashboard).

{
  "mcpServers": {
    "algovoi": {
      "command": "npx",
      "args": ["-y", "@algovoi/mcp-server"],
      "env": {
        "ALGOVOI_API_KEY": "algv_...",
        "ALGOVOI_API_BASE": "https://cloud.algovoi.co.uk"
      }
    }
  }
}

Every payment Claude creates appears in your Cloud dashboard alongside payments from every other platform. One place to see everything.

Sign up free at dash.algovoi.co.uk.

Option B — AlgoVoi direct

Connect straight to the AlgoVoi API with your algv_... key and tenant ID.

Both packages read the same env vars:

VarRequiredPurpose
ALGOVOI_API_KEYalgv_... API key from the AlgoVoi dashboard
ALGOVOI_TENANT_IDTenant UUID from the AlgoVoi dashboard
ALGOVOI_PAYOUT_ALGORAND✅*Algorand payout wallet address
ALGOVOI_PAYOUT_VOI✅*VOI payout wallet address
ALGOVOI_PAYOUT_HEDERA✅*Hedera payout account (e.g. 0.0.123456)
ALGOVOI_PAYOUT_STELLAR✅*Stellar payout address (G...)
ALGOVOI_PAYOUT_ADDRESSUniversal fallback if per-chain vars are not set
ALGOVOI_WEBHOOK_SECRETFor verify_webhook
ALGOVOI_API_BASEOverride the AlgoVoi API base URL (default: https://api.algovoi.co.uk)
ALGOVOI_MODEResponse model: substrate (default) or standard — see "Response model" above

* At least one per-chain address (or ALGOVOI_PAYOUT_ADDRESS as fallback) is required.

Auth is env-var only. Secrets never pass through tool arguments — the MCP client never sees the API key.

Sign up at www.algovoi.co.uk to get your API key and tenant 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>"
      }
    }
  }
}

For the Python package, swap "command": "uvx", "args": ["algovoi-mcp"].

Config file locations:

  • 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

Testing

# TypeScript unit tests
cd typescript && npm test

# Python unit tests
cd python && pytest

# Stdio integration smoke — boots both servers and confirms all 29 tools list
python smoke_stdio.py

Licensed under the MIT License.

Keywords

mcp

FAQs

Package last updated on 29 May 2026

Related posts