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.
npx agentmods add mcp/calhooon/bsv-wallet-cli/bsv-walletgit clone --depth 1 https://github.com/Calhooon/bsv-wallet-cliWrote 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/calhooon/bsv-wallet-cli/bsv-wallet)<a href="https://agentmods.dev/mcp/calhooon/bsv-wallet-cli/bsv-wallet"><img src="https://agentmods.dev/badge/mcp/calhooon/bsv-wallet-cli/bsv-wallet.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
bsv-wallet 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 5d 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
{
"bsv-wallet": {
"type": "stdio",
"command": "cargo",
"args": [
"run",
"--release",
"--manifest-path",
"mcp/Cargo.toml"
],
"env": {
"WALLET_URL": "http://localhost:3322"
}
}
}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.
- 5d ago First seen · 15 lines scan A ffe47e2a1397
bsv-wallet is an MCP server published in the GitHub repository Calhooon/bsv-wallet-cli (10 stars, last pushed today), 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
mcp-server
Bitcoin-native MCP server for AI agents: BTC/STX wallets, DeFi yield, sBTC peg, NFTs, x402 payments. Runs locally from the @aibtc/mcp-server npm package.
bitcoin-mcp
MCP server for Bitcoin — 49 tools for AI agents to save money on fees. Zero config, works out of the box. Runs locally from the bitcoin-mcp Python package.
btc-node
Real BTC full node: fees, mempool, txs, portfolio, trace, whales, SEC, scraping, Reddit via x402. Remote server at mcp.btcnode.uk.
mcp-server
Interact with Counterparty — the token protocol on Bitcoin. Query, compose, sign. Runs locally from the @21e14/mcp-server npm package. Needs 3 environment variables to run.
x402-bridge
Pay any x402 endpoint on the open web: auto-paying bridge with Bazaar discovery and spend caps. Runs locally from the @three-ws/mcp-bridge npm package. Needs 13 environment variables to run.
three-token-mcp
Price, hold, and burn $THREE on Solana — the first MCP server whose actions burn a token. Runs locally from the @three-ws/three-token-mcp npm package. Needs 5 environment variables to run.