Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/agentzeny/snap-publicWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/agentzeny/snap-public/mcp-snap-private-payments)<a href="https://agentmods.dev/mcp/agentzeny/snap-public/mcp-snap-private-payments"><img src="https://agentmods.dev/badge/mcp/agentzeny/snap-public/mcp-snap-private-payments/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/agentzeny/snap-public/mcp-snap-private-payments"><img src="https://agentmods.dev/badge/mcp/agentzeny/snap-public/mcp-snap-private-payments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
snap-private-payments scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"snap-private-payments": {
"command": "npx",
"args": [
"-y",
"snap-mcp-server"
],
"env": {
"SNAP_RPC_URL": "",
"SNAP_POOL_ADDRESS": "",
"SNAP_RELAYER_URL": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 14 lines scan A 603d2782ace9
snap-private-payments is an MCP server published in the GitHub repository agentzeny/snap-public (0 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
onchain-agent-wallets
Give an AI agent a Solana spending allowance instead of your key. Chain-enforced cap, x402. Runs locally from the @three-ws/onchain-agent-wallets npm package. Needs 5 environment variables to run.
madeonsol
Solana KOL trading intelligence & deployer analytics via x402 micropayments or API key. Runs locally from the mcp-server-madeonsol npm package.
ap2-iso20022
Bridge AP2 (Agent Payments Protocol) and x402 agent-payment mandates into wire-valid ISO 20022 pain.001 / pacs.008 records, with spending-cap, expiry and authorisation guardrails. Includes an MCP server. Runs locally from the ap2-iso20022 Python package.
stipend
Non-custodial USDC wallet on Base with spending limits enforced in code, not in a prompt. Runs locally from the stipend npm package.
tidex6-mcp-local
MCP server "tidex6-mcp-local" as configured in koshak01/tidex6. Launched with tidex6-mcp-local.
anchor-x402
MCP server for anchor-x402 — 14 x402-paid agent utilities on Base + Solana. 9 commodity primitives (anchor, screen, attest, decode/tx, resolve/name, price/token, decode/calldata, parse/datetime, intel/wallet) plus 5 universal LLM endpoints (roast, oracle. Runs locally from the anchor-x402-mcp npm package. Needs 1…