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/teamssUTXO/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/teamssutxo/bitcoin_mcp/bitcoin-mcp)<a href="https://agentmods.dev/mcp/teamssutxo/bitcoin_mcp/bitcoin-mcp"><img src="https://agentmods.dev/badge/mcp/teamssutxo/bitcoin_mcp/bitcoin-mcp/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/teamssutxo/bitcoin_mcp/bitcoin-mcp"><img src="https://agentmods.dev/badge/mcp/teamssutxo/bitcoin_mcp/bitcoin-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
bitcoin-mcp 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 9d 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
{ "bitcoin-mcp": { "command": "uvx", "args": [ "bitcoin-mcp" ] } }
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.
- 9d ago First seen · 8 lines scan A 6a88b4ef2f96
bitcoin-mcp is an MCP server published in the GitHub repository teamssUTXO/bitcoin_mcp (6 stars, last pushed 3mo 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
btc-node
Real BTC full node: fees, mempool, txs, portfolio, trace, whales, SEC, scraping, Reddit via x402. Remote server at mcp.btcnode.uk.
bsv-wallet
MCP server "bsv-wallet" as configured in Calhooon/bsv-wallet-cli. Launched with cargo run --release --manifest-path mcp/Cargo.toml. Needs 1 environment variable to run.
xrpl-referee
Trust and payment layer for the agentic economy on the XRP Ledger. Remote server at xrpl-referee.onrender.com.
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.
canton-mcp
Query Canton Network balances, rewards, transactions, prices, and identity from any AI agent. Runs locally from the @noves/canton-mcp npm package. Needs 1 environment variable to run.
base-multi-wallet-mcp
MCP server for AI agents to manage multiple wallets with coordinated trading and batch operations on. Runs locally from the base-multi-wallet-mcp npm package.