MCP.so
ログイン
S

Snap Protocol MCP Server

@agentzeny

基本情報

カテゴリ

その他

トランスポート

stdio

作者

agentzeny

投稿者

agentzeny

Snap Protocol MCP Server について

概要はまだありません

Snap Protocol MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "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 のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

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

よくある質問

1

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.

2

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.

3

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.

4

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.

5

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.

コメント

「その他」の他のコンテンツ