Bitcoin (Bortlesboat) MCP Server

bitcoin-mcp PyPI v0.5.1

Published by bortlesboat — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Bitcoin — 49 tools for AI agents to save money on fees. Zero config, works out of the box.

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

low Shell/command execution in packaging/dev tooling (tests/test_server.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_server.py:434`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: elf): result = subprocess.run( [sys.executable, "-m", "bitcoin_mcp.server", "--version"],

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_server.py

Tools 49

Each tool and what it can reach — statically extracted from the published source.

  • analyze_blockno sensitive capability
  • analyze_mempoolno sensitive capability
  • analyze_next_blockno sensitive capability
  • analyze_psbt_securityno sensitive capability
  • analyze_transactionno sensitive capability
  • check_utxono sensitive capability
  • compare_blocksno sensitive capability
  • compare_fee_estimatesno sensitive capability
  • decode_bolt11_invoiceno sensitive capability
  • decode_raw_transactionno sensitive capability
Show 39 more tools ↓
  • describe_rpc_commandno sensitive capability
  • estimate_smart_feeno sensitive capability
  • estimate_transaction_costno sensitive capability
  • explain_inscription_listing_securityno sensitive capability
  • explain_scriptno sensitive capability
  • generate_keypairno sensitive capability
  • get_address_balanceno sensitive capability
  • get_address_historyno sensitive capability
  • get_address_utxosno sensitive capability
  • get_block_countno sensitive capability
  • get_block_statsno sensitive capability
  • get_blockchain_infono sensitive capability
  • get_btc_priceno sensitive capability
  • get_chain_tipsno sensitive capability
  • get_chain_tx_statsno sensitive capability
  • get_difficulty_adjustmentno sensitive capability
  • get_fee_estimatesno sensitive capability
  • get_fee_recommendationno sensitive capability
  • get_halving_countdownno sensitive capability
  • get_indexed_transactionno sensitive capability
  • get_indexer_statusno sensitive capability
  • get_market_sentimentno sensitive capability
  • get_mempool_ancestorsno sensitive capability
  • get_mempool_entryno sensitive capability
  • get_mempool_infono sensitive capability
  • get_mining_infono sensitive capability
  • get_mining_pool_rankingsno sensitive capability
  • get_network_infono sensitive capability
  • get_node_statusno sensitive capability
  • get_peer_infono sensitive capability
  • get_situation_summaryno sensitive capability
  • get_supply_infono sensitive capability
  • get_utxo_set_infono sensitive capability
  • list_rpc_commandsno sensitive capability
  • query_remote_apino sensitive capability
  • search_blockchainno sensitive capability
  • search_blocksno sensitive capability
  • send_raw_transactionno sensitive capability
  • validate_addressno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.5.1 latest A 99/100 1 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/bitcoin-mcp-2/badge.svg)](https://mcptrustchecker.com/registry/bitcoin-mcp-2)
HTML
<a href="https://mcptrustchecker.com/registry/bitcoin-mcp-2"><img src="https://mcptrustchecker.com/registry/bitcoin-mcp-2/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/bitcoin-mcp-2/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan bitcoin-mcp --online --registry pypi

Use the free API → How scoring works

Other implementations of Bitcoin 4

Independent packages implementing the same tool, scanned with the same engine. Compare all 5 side by side →

More in Finance & Commerce