SNAP Protocol

io.github.agentzenyPublished by GitHub account agentzenyv0.1.2Updated Oct 24, 2026

Private agent payments on Solana via ZK proofs: deposit, withdraw, list pools, estimate fees.

The publisher's own server: Payments Ai Mcp

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

A local MCP server that lets an assistant make private Solana payments through a shielded pool using zero-knowledge proofs: deposit, withdraw, list pools and,

What you can do
List shielded pools and read pool information, including mainnet pools for SOL and USDC amounts shown in the README. Deposit funds into a shielded pool. Withdraw from a pool, including a private withdrawal path that can use an optional relayer. Estimate fees before moving funds. Compatibility helpers cover private withdrawal, pool info and balance checks for existing local flows.
When to use it
Useful when an assistant should help with private on-chain payments on Solana: checking available pools, estimating fees, and preparing deposits or withdrawals through a shielded pool rather than a plain transfer.
Requirements
Runs locally over stdio, typically via npx with the npm package or a local script path. Requires SNAP_RPC_URL (a Solana RPC endpoint) and SNAP_POOL_ADDRESS (default pool). SNAP_RELAYER_URL is optional for private withdrawals. A serialized note (SNAP_MCP_NOTE) and a viewing key (SNAP_MCP_VIEWING_KEY_JSON) are read from the environment. Desktop only.
Before you install
This server moves real funds: deposits and withdrawals act on mainnet pools and can spend money, so review amounts and pool addresses before approving. It reads sensitive secrets from the environment, including SNAP_MCP_NOTE and SNAP_MCP_VIEWING_KEY_JSON, which should be handled carefully. Private withdrawals may send data to the relayer set in SNAP_RELAYER_URL. A stub mode variable exists for local testing; do not confuse stub runs with real transactions.

Installation

In SourceWeft

  1. Open SNAP Protocol in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

SNAP MCP Server

MCP server for SNAP private payments. It targets @modelcontextprotocol/sdk 1.28.0 and uses stdio transport.

Tools

  • snap_list_pools
  • snap_deposit
  • snap_withdraw
  • snap_estimate_fee

The server also keeps snap_withdraw_private, snap_pool_info, and snap_balance as compatibility helpers for existing local flows.

Claude Code Config

json
{  "mcpServers": {    "snap": {      "command": "npx",      "args": ["tsx", "/path/to/agent-privacy-pool/integrations/mcp/snap-mcp-server.ts"],      "env": {        "SNAP_RPC_URL": "https://api.mainnet-beta.solana.com",        "SNAP_POOL_ADDRESS": "B8SyffZKt8LABKogWjH9rZcjY5PV2hyYRCbTxxbcrpFf",        "SNAP_RELAYER_URL": "https://your-relayer.example"      }    }  }}

For deterministic local transport tests, set SNAP_MCP_STUB_MODE=1.

Environment

Start from integrations/mcp/.env.example:

  • SNAP_RPC_URL
  • SNAP_POOL_ADDRESS
  • SNAP_RELAYER_URL
  • SNAP_MCP_NOTE
  • SNAP_MCP_VIEWING_KEY_JSON
  • SNAP_MCP_STUB_MODE

SNAP_MCP_NOTE should be a serialized note returned by SNAPClient.serializeNote(...).

Mainnet Pools

  • 0.1 SOL: B8SyffZKt8LABKogWjH9rZcjY5PV2hyYRCbTxxbcrpFf
  • 1 USDC: 5LeuHrPBgHNhgbCy996MEjcsBk5gNHhVj6AiuuCHZ8od
  • 10 USDC: ECuHf8kgiWfmL3Q6id4WGBQWvuukhzqvF5vsxuPAKZBv

Run

bash
cd /path/to/agent-privacy-poolset -asource integrations/mcp/.env.exampleset +anpx tsx integrations/mcp/snap-mcp-server.ts

Smoke test:

bash
npx mocha --require tsx integrations/tests/mcp-stdio.test.ts

Source: integrations/mcp/README.md at commit bee9bb0

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Payments integrations