SNAP Protocol
NPM · SNAP-MCP-SERVER
Private agent payments on Solana via ZK proofs: deposit, withdraw, list pools, estimate fees.
Available components
Last scanned (29 minutes ago)
Scores higher than 50% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security89
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects toml 3.0.0, reached via snap-solana-sdk > @coral-xyz/anchor > toml. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 113 of 317 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 152 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 217 tokens (~31/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "snap_withdraw" implies "withdraw" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- CVE-2026-118764 no longer affects this package ▲ security
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −1
- CVE-2026-118764 affects this package: high ▼ security
- Stability: pass → 0.97 functional
- 27 Oct 26 +1
- CVE-2026-114142 affects this package: high ▼ security
- Security disclosure: unverified → pass ▲ functional
- 26 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
- 25 Oct 26 +1
- Stability: 0.97 → pass security
- 23 Oct 26 −1
- CVE-2026-114144 affects this package: high ▼ security
- CVE-2026-114143 affects this package: high ▼ security
- CVE-2026-114141 affects this package: high ▼ security
- Stability: pass → 0.93 functional
- 17 Oct 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/snap-mcp-server@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 15 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-3gc7-fjrx-p6mg | CVE-2025-3194 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | no |
| GHSA-848j-6mx2-7j84 | CVE-2025-14505 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L | no |
| GHSA-528h-pc64-c93x | CVE-2026-71429 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-hqr4-qq8f-hg3x | CVE-2026-104182 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-mjw6-4jj6-33hc | CVE-2026-104183 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L | yes |
| GHSA-4qx8-w7c3-pj3p | CVE-2026-114141 | high | yes | |
| GHSA-82x6-q7mm-w9cf | CVE-2026-77465 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-9j65-hcg3-gc64 | CVE-2026-114143 | high | yes | |
| GHSA-9qmh-m7c6-f92p | CVE-2026-114144 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-h895-cgqg-jf52 | CVE-2026-114142 | high | yes | |
| GHSA-v5mp-jgw5-2x6j | CVE-2026-63376 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L | yes |
| GHSA-qpx9-hpmf-5gmw | CVE-2026-27601 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-58qx-3vcg-4xpx | CVE-2026-45736 | medium | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-96hv-2xvq-fx4p | CVE-2026-48779 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 317 packages
| Packages resolved | 317 |
|---|---|
| Deprecated | 2 |
| Stale | 108 |
| No linked repository | 5 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
snap_balance ~18
Check private shielded balance with a viewing key
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
snap_deposit ~35
Deposit into a SNAP privacy pool and return note metadata
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | – |
| poolAddress | string | – | – |
No output schema declared.
No examples provided.
snap_estimate_fee ~35
Estimate SNAP withdrawal fees for a pool
| Name | Type | Req | Description |
|---|---|---|---|
| poolAddress | string | – | – |
| relayerUrl | string | – | – |
No output schema declared.
No examples provided.
snap_list_pools ~19
List SNAP mainnet shielded payment pools
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
snap_pool_info ~18
Get public information about the configured SNAP pool
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
snap_withdraw ~53
Withdraw from a SNAP pool with a note, optionally through a relayer
| Name | Type | Req | Description |
|---|---|---|---|
| note | – | – | – |
| poolAddress | string | – | – |
| recipient | string | yes | – |
| relayerUrl | string | – | – |
No output schema declared.
No examples provided.
snap_withdraw_private ~39
Legacy alias for relayed SNAP withdrawal
| Name | Type | Req | Description |
|---|---|---|---|
| note | – | – | – |
| recipient | string | yes | – |
| relayerUrl | string | – | – |
No output schema declared.
No examples provided.
How do I install the SNAP Protocol MCP server?
SNAP Protocol runs locally as an npm package, launched with npx -y snap-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · snap-mcp-server
claude mcp add agentzeny-snap-private-payments -- npx -y snap-mcp-server
What is the SNAP Protocol MCP server?
SNAP Protocol is an MCP server listed in the public MCP registry as io.github.agentzeny/snap-private-payments. Private agent payments on Solana via ZK proofs: deposit, withdraw, list pools, estimate fees. This page covers its npm package (snap-mcp-server).
Is the SNAP Protocol MCP server safe to use?
SNAP Protocol scores 75 out of 100 on VerifyMCP. We recorded 15 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SNAP Protocol MCP server expose?
SNAP Protocol exposes 7 tools: snap_list_pools, snap_deposit, snap_withdraw, snap_estimate_fee, snap_withdraw_private, and 2 more. Their descriptions and schemas cost roughly 217 tokens of context every time the server is loaded.
Is the SNAP Protocol MCP server still maintained?
SNAP Protocol is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the SNAP Protocol MCP server under?
SNAP Protocol declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.