presign-guard wallet runs on your own machine — the client starts it, so there is no endpoint to ping. 2 390 installs a week from npm. Last commit 15 Oct 2026.
Agent wallet with limits: pays x402/MPP on Base, Solana, Tempo, XRPL and Algorand; phone approval.
We read the source, 23 h ago · rules ccca72095570
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
with open(os.path.join(HERE, args.script)) as f:
p = subprocess.run([ffmpeg, "-i", path], capture_output=True, text=True)
const API = "https://api.telegram.org";
"bytecode": "0x610100604052348015610010575f80fd5b506040516107c83803806107c883398101604081905261002f916100ba565b6001600160a01b038416158061004c57506001600160a01b038316155b80610055575081155b8061006257506201518081105b15610080576040516301f30c8760e21b815260040160405180910390fd5b60016…
finally { b.disabled = false; b.innerHTML = label; }
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Today is the operative word: we check presign-guard wallet every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add presign-guard-wallet -- npx -y presign-guard-wallet-mcp
{
"mcpServers": {
"presign-guard-wallet": {
"args": [
"-y",
"presign-guard-wallet-mcp"
],
"command": "npx"
}
}
}
[mcp_servers.presign-guard-wallet]
command = "npx"
args = ["-y", "presign-guard-wallet-mcp"]
{
"mcpServers": {
"presign-guard-wallet": {
"args": [
"-y",
"presign-guard-wallet-mcp"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"presign-guard-wallet": {
"args": [
"-y",
"presign-guard-wallet-mcp"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
AGENT_KEY (Private key of the agent's own wallet (a separate wallet holding only what the agent may spend)), LIMIT_USDC_PER_TX (Most USDC per payment or transfer without asking you, e.g. 5), LIMIT_USDC_PER_DAY (Daily USDC budget, e.g. 20), TELEGRAM_BOT_TOKEN (Telegram bot that asks you to approve anything over a limit), TELEGRAM_CHAT_ID (Your Telegram chat id (approvals go only there)), WALLET_SERVER_URL (Instead of LIMIT_* and TELEGRAM_*: a wallet server keeping one budget for all your agents), WALLET_SERVER_KEY (The agent key (awk_…) from the wallet server's dashboard), CHAIN (base (default), ethereum, optimism, arbitrum, polygon or bsc), MAX_PAYMENT_USD (Most a single x402 API call may cost, in dollars (default 1)), ALLOW_LIST (Optional: only pay or sign for these addresses (0x, XRPL r… or Algorand, comma-separated); anything else needs approval. Not with a wallet server), PRESIGN_CREDIT_KEY (Optional presign-guard credit key (pgc_…) to pay the $0.01 checks from prepaid credits), RPC_URL (Optional RPC URL for the chain), TEMPO (off to never pay MPP charges on Tempo (default on: paid in USDC.e on Tempo from the same address)), TEMPO_CHAIN (4217 (Tempo, default) or 42431 (Moderato testnet)), TEMPO_RPC_URL (Optional Tempo RPC URL), MPP_SESSION_DEPOSIT (Optional: pay MPP sessions on Tempo; the USDC.e each channel deposit or top-up puts in (counted toward the USDC limits); then each call is a signed voucher), SOLANA_PRIVATE_KEY (Optional: the agent's own Solana secret key (base58 or solana-keygen byte array); pays x402 offers in USDC on Solana (checked by presign-guard, counted toward the USDC limits)), SOLANA_NETWORK (mainnet (default) or devnet), SOLANA_RPC_URL (Optional Solana RPC URL), ALGORAND_MNEMONIC (Optional: the agent's own Algorand account (25 words); pays x402 offers in USDC on Algorand (counted toward the USDC limits)), ALGORAND_NETWORK (mainnet (default) or testnet), XRPL_SEED (Optional: the agent's own XRPL account seed; pays x402 offers in RLUSD on the XRP Ledger (counted toward the USDC limits)), XRPL_NETWORK (mainnet (default) or testnet), XRPL_WS_URL (Optional XRPL node websocket URL).
The author declared them in the registry entry; get the values from the project itself.
Safe to sign? EVM, Solana, XRPL, Algorand txs, permits, tokens; OFAC wallet screen: green/orange/red
Let an AI agent find and pay for x402 APIs and products in USDC on Base, within owner-set limits.
Give an agent a wallet. Pays for x402 resources within hard limits. Base + USDC, gasless.
X402 payment MCP for AI agents. Auto-pay 300+ APIs with USDC on Base and Solana.
Pre-payment merchant trust checks for x402 agents on Base and Solana.
Wallet and payments for AI agents: auto-pay x402 APIs in USDC on XDC, within on-chain limits.
Batch send SOL or any SPL token to 1000+ wallets via x402. AI agent payments on Solana.
Buy any x402 API or data on Base, Solana, Polygon. No wallet on the seller's chain. For AI agents.
Answers built from our own checks of this server.