SNAP Protocol runs on your own machine — the client starts it, so there is no endpoint to ping. 38 installs a week from npm. Last commit 6 Jun 2026.
Private agent payments on Solana via ZK proofs: deposit, withdraw, list pools, estimate fees.
What the code does
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const wasmPath = path.join(artifactsDir, wasmName);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
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 snap-private-payments -e 'SNAP_RPC_URL=<SNAP_RPC_URL>' -e 'SNAP_POOL_ADDRESS=<SNAP_POOL_ADDRESS>' -- npx -y snap-mcp-server{
"mcpServers": {
"snap-private-payments": {
"command": "npx",
"args": [
"-y",
"snap-mcp-server"
],
"env": {
"SNAP_POOL_ADDRESS": "<SNAP_POOL_ADDRESS>",
"SNAP_RPC_URL": "<SNAP_RPC_URL>"
}
}
}
}[mcp_servers.snap-private-payments]
command = "npx"
args = ["-y", "snap-mcp-server"]
env = { SNAP_RPC_URL = "<SNAP_RPC_URL>", SNAP_POOL_ADDRESS = "<SNAP_POOL_ADDRESS>" }{
"mcpServers": {
"snap-private-payments": {
"command": "npx",
"args": [
"-y",
"snap-mcp-server"
],
"env": {
"SNAP_POOL_ADDRESS": "<SNAP_POOL_ADDRESS>",
"SNAP_RPC_URL": "<SNAP_RPC_URL>"
}
}
}
}{
"servers": {
"snap-private-payments": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"snap-mcp-server"
],
"env": {
"SNAP_POOL_ADDRESS": "<SNAP_POOL_ADDRESS>",
"SNAP_RPC_URL": "<SNAP_RPC_URL>"
}
}
}
}Put your own values in place of
<SNAP_RPC_URL> (Solana RPC endpoint URL), <SNAP_POOL_ADDRESS> (Default shielded pool address).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
SNAP_RELAYER_URL (Optional relayer URL for private withdrawals).
Alternatives to SNAP Protocol
same job, measured the same wayGive any AI agent instant payment capabilities via x402 protocol on Solana
Give any AI agent instant payment capabilities via x402 protocol on Solana
Private balance on Robinhood Chain for AI agents: send, swap and withdraw ETH, USDG and stocks.
MCP server for jPOS and ISO 8583. Deterministic payment protocol tools for AI agents.
AI Agent payment protocol on CKB Fiber Network. Zero-gas micropayments with Hold Invoice escrow.
USDC wallets, payment links and x402 payments on Solana for AI agents.
Batch send SOL or any SPL token to 1000+ wallets via x402. AI agent payments on Solana.
X402 payment MCP for AI agents. Auto-pay 300+ APIs with USDC on Base and Solana.
SNAP Protocol — questions
Answers built from our own checks of this server.