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/spcpza/bitcoin-mcp/bitcoingit clone --depth 1 https://github.com/spcpza/bitcoin-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/spcpza/bitcoin-mcp/bitcoin)<a href="https://agentmods.dev/mcp/spcpza/bitcoin-mcp/bitcoin"><img src="https://agentmods.dev/badge/mcp/spcpza/bitcoin-mcp/bitcoin.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
bitcoin 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 4d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 4d ago First seen · 9 lines scan A f6198800464c
bitcoin is an MCP server published in the GitHub repository spcpza/bitcoin-mcp (0 stars, last pushed 6mo ago), with no licence file. 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
saturnzap
CLI-first, non-custodial Lightning Network wallet for autonomous AI agents. Runs locally from the saturnzap Python package. Needs 2 environment variables to run.
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. Needs 5 environment variables to run.
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.
402-mcp
AI agents discover, pay for, and consume any Lightning-gated API autonomously. Runs locally from the 402-mcp npm package. Needs 2 environment variables to run.
hashlock
Non-custodial cross-chain OTC for AI agents: sealed RFQ, negotiation, HTLC atomic swaps. Testnet. Runs locally from the @hashlock-tech/mcp npm package. Needs 7 environment variables to run.
alloc-context
Portfolio-aware crypto context — CEX or wallet holdings, holdings-scoped market, optional allocation analysis. Runs locally from the alloc-context Python package.