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/hypeprinter007-stack/anchor-x402-mcpWrote 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/hypeprinter007-stack/anchor-x402-mcp/anchor-x402)<a href="https://agentmods.dev/mcp/hypeprinter007-stack/anchor-x402-mcp/anchor-x402"><img src="https://agentmods.dev/badge/mcp/hypeprinter007-stack/anchor-x402-mcp/anchor-x402/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/hypeprinter007-stack/anchor-x402-mcp/anchor-x402"><img src="https://agentmods.dev/badge/mcp/hypeprinter007-stack/anchor-x402-mcp/anchor-x402.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
anchor-x402 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 8d 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
{
"anchor-x402": {
"command": "npx",
"args": [
"-y",
"anchor-x402-mcp"
],
"env": {
"ANCHOR_WALLET_PRIVATE_KEY": ""
}
}
}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.
- 8d ago First seen · 12 lines scan A 6bc690dd162c
anchor-x402 is an MCP server published in the GitHub repository hypeprinter007-stack/anchor-x402-mcp (1 stars, last pushed 4d 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
lightning-wallet-mcp
Give AI agents a Bitcoin wallet with Lightning Network payments and L402 support. Runs locally from the lightning-wallet-mcp npm package.
danke
MCP server for AI agents to earn and send sats on the Danke network — Bitcoin Lightning micropayments for Claude, Cursor, OpenClaw. Runs locally from the danke-mcp npm package. Needs 3 environment variables to run.
vybe-solana-api
Solana MCP for wallets, trades, markets, PnL, transfers, onchain data, signable swaps and API tools. Remote server at docs.vybenetwork.com.
verantis-mcp
MCP server for Verantis — the verified directory for machine payments (x402 & MPP). Find live-verified services and check a wallet before your agent pays. Runs locally from the verantis-mcp Python package. Needs 1 environment variable to run.
gblin-treasury-risk-regime
Risk regime + treasury for AI agents on Base: free regime reads, signed attestations, idle USDC. Runs locally from the @gblin-protocol/mcp-server npm package. Needs 1 environment variable to run.
bitget-agent-mcp
Official Bitget MCP Server for the Unified Trading Account (UTA v3) API. Runs locally from the @bitget-ai/bitget-agent-mcp npm package. Needs 3 environment variables to run.