PipRail MCP Server

Budget-bound x402 payment wallet for AI agents — pays HTTP 402 URLs, capped locally. No backend.

Local serverstdio

What is the PipRail MCP Server?

PipRail is an MCP integration. Budget-bound x402 payment wallet for AI agents — pays HTTP 402 URLs, capped locally. No backend.

Packages and local setup

The published npm package is @piprail/mcp, version 0.10.0. Its declared MCP transport is stdio.

The package declares PIPRAIL_PRIVATE_KEY: Your wallet's private key/seed for the chosen chain. Optional: omit it to run read-only (discover/quote/register/budget/guide); set it to let the agent pay. Stays on your machine; the spend policy caps every payment.; PIPRAIL_CHAIN: Chain to pay on (default: base).; PIPRAIL_CHAINS: Pay across several chains (instead of PIPRAIL_CHAIN): a comma-separated list, e.g. base,polygon,solana. Give each its own PIPRAIL_ KEY (+ optional PIPRAIL _RPC_URL). The agent pays whichever chain a 402 asks for — the first listed that can settle — under one shared budget.; PIPRAIL_MAX_AMOUNT: Max spend per single payment, in token units (default: 0.10).; PIPRAIL_MAX_TOTAL: Lifetime spend cap per token, in token units (default: 10.00).; PIPRAIL_MAX_TOTAL_DENOM: Cross-token GRAND TOTAL: one spend cap per denomination across every stablecoin and chain, e.g. USD:20.00,EUR:5.00. Not a price oracle — sums tokens of the same unit, each counted 1:1. Native coins are excluded.; PIPRAIL_MAX_PAYMENTS: Lifetime cap on the NUMBER of payments, across every chain + token (e.g. 100).; PIPRAIL_MAX_PAYMENTS_PER_WINDOW: Cap on the number of payments within PIPRAIL_WINDOW_SECONDS (a rolling rate limit; set PIPRAIL_WINDOW_SECONDS too).; PIPRAIL_WARN_AT_FRACTION: Emit an early-warning event when spend crosses this fraction of any cap, e.g. 0.8 (80%). Needs PIPRAIL_EVENT_LOG to be visible.; PIPRAIL_SPEND_LOG: Path to a local append-only spend log. When set, the budget (lifetime, grand total, counts) SURVIVES a restart — hydrated from this file. No backend; you own the file.; PIPRAIL_EVENT_LOG: Mirror payment events (settled / declined / budget-threshold) as one-line JSON to 'stderr' or a file path — the operator's notification stream. Default: off.; PIPRAIL_TOKENS: Comma-separated allowed token symbols, plus the alias 'native' for the chain's coin (default: USDC).; PIPRAIL_SCHEMES: Comma-separated payment schemes to settle (default: onchain-proof). Add 'exact' (onchain-proof,exact) to also pay standard x402 servers GASLESS on EVM + Solana (method auto-selected). Add 'upto' to also pay metered x402 servers on EVM (Permit2): sign a MAX, the server settles the actual <= max..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.10.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related payments & commerce MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
PIPRAIL_PRIVATE_KEYYour wallet's private key/seed for the chosen chain. Optional: omit it to run read-only (discover/quote/register/budget/guide); set it to let the agent pay. Stays on your machine; the spend policy caps every payment.Optional
PIPRAIL_CHAINChain to pay on (default: base).Optional
PIPRAIL_CHAINSPay across several chains (instead of PIPRAIL_CHAIN): a comma-separated list, e.g. base,polygon,solana. Give each its own PIPRAIL_ _KEY (+ optional PIPRAIL_ _RPC_URL). The agent pays whichever chain a 402 asks for — the first listed that can settle — under one shared budget.Optional
PIPRAIL_MAX_AMOUNTMax spend per single payment, in token units (default: 0.10).Optional
PIPRAIL_MAX_TOTALLifetime spend cap per token, in token units (default: 10.00).Optional
PIPRAIL_MAX_TOTAL_DENOMCross-token GRAND TOTAL: one spend cap per denomination across every stablecoin and chain, e.g. USD:20.00,EUR:5.00. Not a price oracle — sums tokens of the same unit, each counted 1:1. Native coins are excluded.Optional
PIPRAIL_MAX_PAYMENTSLifetime cap on the NUMBER of payments, across every chain + token (e.g. 100).Optional
PIPRAIL_MAX_PAYMENTS_PER_WINDOWCap on the number of payments within PIPRAIL_WINDOW_SECONDS (a rolling rate limit; set PIPRAIL_WINDOW_SECONDS too).Optional
PIPRAIL_WARN_AT_FRACTIONEmit an early-warning event when spend crosses this fraction of any cap, e.g. 0.8 (80%). Needs PIPRAIL_EVENT_LOG to be visible.Optional
PIPRAIL_SPEND_LOGPath to a local append-only spend log. When set, the budget (lifetime, grand total, counts) SURVIVES a restart — hydrated from this file. No backend; you own the file.Optional
PIPRAIL_EVENT_LOGMirror payment events (settled / declined / budget-threshold) as one-line JSON to 'stderr' or a file path — the operator's notification stream. Default: off.Optional
PIPRAIL_TOKENSComma-separated allowed token symbols, plus the alias 'native' for the chain's coin (default: USDC).Optional
PIPRAIL_SCHEMESComma-separated payment schemes to settle (default: onchain-proof). Add 'exact' (onchain-proof,exact) to also pay standard x402 servers GASLESS on EVM + Solana (method auto-selected). Add 'upto' to also pay metered x402 servers on EVM (Permit2): sign a MAX, the server settles the actual <= max.Optional