What does Snap Protocol do that a simple token transfer cannot?
It makes the deposit and withdrawal unlinkable: observers see only shielded pool activity, not the connection between the sending and receiving agents.
S
Snap Protocol MCP Server
@agentzeny
Basic information
About Snap Protocol MCP Server
No overview available yet
Snap Protocol MCP Server config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"snap": {
"command": "npx",
"args": [
"tsx",
"snap-mcp-server.ts"
],
"env": {
"SNAP_RPC_URL": "https://api.mainnet-beta.solana.com",
"SNAP_POOL_ADDRESS": "B8SyffZKt8LABKogWjH9rZcjY5PV2hyYRCbTxxbcrpFf"
}
}
}
}Snap Protocol MCP Server tools
Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
Fetch the live tool list by running this server in a temporary sandbox using the button above.
Overview
What is Snap Protocol?
Snap Protocol is an MCP server that enables private agent-to-agent payments on Solana mainnet using zero-knowledge proofs. It lets two agents conduct unlinkable transfers through shielded pools — one agent deposits tokens and generates a secret note, the other agent withdraws using a Groth16 proof.
How to use Snap Protocol?
Install the SDK via npm install snap-solana-sdk, then use the provided tools: snap_list_pools, snap_deposit, snap_withdraw, and snap_estimate_fee. A typical flow is deposit into a pool, share the resulting secret note off‑chain, and have the receiving agent withdraw with a zero‑knowledge proof.
Key features of Snap Protocol
- Private agent-to-agent payments on Solana mainnet
- Shielded pools for 0.1 SOL, 1 USDC, and 10 USDC
- Deposit creates a cryptographic commitment and secret note
- Withdrawal requires a Groth16 ZK proof
- Direct withdrawal or relayed withdrawal supported
- Protocol fee of 0.25% on withdrawals
Use cases of Snap Protocol
- A trading agent pays another agent privately without on-chain linkability
- A DAO compensates a contributor off-chain while preserving privacy
- A gaming agent sends winnings to another agent with no public trace
- Two agents exchange value across services without exposing balances
Frequently asked questions
What runtime or dependencies are required?
Solana mainnet-beta and the Node.js package `snap-solana-sdk`. No additional infrastructure is needed; the server handles proof generation and submission.
Where do the secret notes live?
Secret notes are generated during deposit and must be sent off‑chain by the depositor to the intended recipient. They are not stored on-chain.
Are there any known limits?
The protocol currently offers three shielded pools (0.1 SOL, 1 USDC, 10 USDC) and imposes a 0.25% protocol fee on withdrawals. The withdrawal can be direct or via a relayer.
What transport or authentication does the server use?
The README does not specify transport or authentication details. The server communicates with the Solana network and exposes the listed tools for MCP clients.
More Other MCP servers
Yuppsy
Yuppsy MCP: build and publish real estate websites from your AI assistant. Yuppsy lets your AI assistant create live websites for real estate agents and individual property listings. You don't need a designer or any code
MCP Toolbox for Databases
googleapisMCP Toolbox for Databases is an open source MCP server for databases.
15.9K
Handl
Handl speaks the Model Context Protocol. Your whole billing operation — projects, invoices, clients, reports, approvals — as tools any AI assistant can call, inside your autonomy rules.
DeepMark
DeepMark helps teachers deliver rapid, consistent marking with meaningful feedback for every student — in a fraction of the time. What once took a week, now takes one free period.
Blender
ahujasidOpen-source MCP to use Blender with any LLM
23.6K
Comments