Server data from the Official MCP Registry
Non-custodial payment engine for AI agents — BTC, ETH, USDT, USDC, XRP, XMR, ZEC.
Non-custodial payment engine for AI agents — BTC, ETH, USDT, USDC, XRP, XMR, ZEC.
This MCP payment server handles cryptocurrency transfers across seven blockchains with a well-designed policy engine for spend limits and idempotency safeguards. However, several security concerns prevent a higher score: the system relies on environment variables for private keys without enforcement of secure storage practices, the MCP server uses a fixed agent ID from env vars which could lead to policy bypass if multiple agents share the same process, and there is insufficient input validation for blockchain addresses. The architecture and code quality are generally sound, but production deployment would require hardening key management and adding address validation. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.
7 files analyzed · 14 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: AGENTIC_PAY_AGENT_ID
Environment variable: AGENTIC_PAY_CONFIG
Environment variable: BTC_WIF
Environment variable: ETH_RPC_URL
Environment variable: ETH_PRIVATE_KEY
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-shieldcubed-agentic-pay": {
"env": {
"BTC_WIF": "your-btc-wif-here",
"ETH_RPC_URL": "your-eth-rpc-url-here",
"ETH_PRIVATE_KEY": "your-eth-private-key-here",
"AGENTIC_PAY_CONFIG": "your-agentic-pay-config-here",
"AGENTIC_PAY_AGENT_ID": "your-agentic-pay-agent-id-here"
},
"args": [
"-y",
"@shieldcubed/agentic-pay"
],
"command": "npx"
}
}
}From the project's GitHub README.
A cross-platform payment engine that lets third-party AI agents send and receive payments over seven crypto rails: BTC, ETH, USDT, USDC, XRP, XMR, ZEC.
One Node.js core runs unmodified on Linux, Windows, and macOS. The same backend is reachable from iOS and Android via an installable Progressive Web App (PWA) — there is no separate native mobile codebase to maintain.
┌───────────────────────────┐
│ core/railManager.js │ <- one call-site for
│ (policy + ledger + auth) │ every asset
└─────────────┬─────────────┘
│
┌───────────┬─────────────┼─────────────┬───────────┬──────────┐
│ │ │ │ │ │
rails/btc rails/eth rails/xrp rails/xmr rails/zec │
(bitcoinjs) (ethers.js, (xrpl.js) (JSON-RPC to (JSON-RPC to │
ETH+USDT+ monero- zcashd) │
USDC ERC20) wallet-rpc) │
│
Agent-facing surfaces (both call railManager, never a rail │
adapter directly): │
┌────────────────────────┐ ┌───────────────────────────┐ │
│ server/restApi.js │ │ server/mcpServer.mjs │ │
│ HTTP/JSON, API-key │ │ MCP stdio server for │ │
│ auth, for any HTTP- │ │ Claude / other MCP- │ │
│ capable agent stack │ │ compatible agent clients │ │
└────────────────────────┘ └───────────────────────────┘ │
│
Human-facing surfaces: │
┌────────────────────────┐ ┌───────────────────────────┐ │
│ cli/index.js │ │ web/ (PWA) │ │
│ Linux/Windows/macOS │ │ served by server/ │ │
│ terminal │ │ staticWeb.js, installable │ │
│ │ │ on iOS/Android home screen │ │
└────────────────────────┘ └───────────────────────────┘ │
Every send, from any surface, passes through core/limits.js (per-agent
spend caps + human-confirmation floor) and core/ledger.js (idempotency,
so a retried tool call can never double-pay).
git clone <this repo> # or unzip the delivered archive
cd agentic-pay
npm install
cp config/.env.example .env
cp config/config.example.json config/config.json
# edit both files — see docs/SETUP_<YOUR_OS>.md for exact values per rail
npm run start:rest # REST API on :8787
npm run start:web # PWA on :8788 (optional, for mobile/browser access)
npm run start:mcp # MCP stdio server (for Claude Desktop / Claude Code)
node cli/index.js rails # sanity check from the terminal
Start on testnets first. Every rail's example config defaults to a
testnet or requires you to explicitly fill in mainnet values — this is
intentional. Do not point real funds at this system until you've reviewed
core/limits.js and set spend caps you're comfortable with.
docs/SETUP_LINUX.mddocs/SETUP_WINDOWS.mddocs/SETUP_MACOS.mddocs/SETUP_MOBILE.md — iOS and Android via PWAdocs/AGENT_INTEGRATION.md — wiring up
Claude, MCP clients, or any HTTP-based agent frameworkdocs/SECURITY.md — key management, spend limits,
and legal/regulatory considerations — read this before sending real
funds.env to an OS keychain or HSM/KMS for anything beyond
development — see core/keystore.js for the extension point).agentic-pay is licensed under the Business Source License 1.1 (see
LICENSE). In plain terms:
Want a commercial license for a hosted/managed offering before then? Contact team@spacenet.network.
Be the first to review this server!
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
by Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption