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.
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:
| Points | Adoption-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.
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
Each tool and what it can reach — statically extracted from the published source.
analyze_blockno sensitive capabilityanalyze_mempoolno sensitive capabilityanalyze_next_blockno sensitive capabilityanalyze_psbt_securityno sensitive capabilityanalyze_transactionno sensitive capabilitycheck_utxono sensitive capabilitycompare_blocksno sensitive capabilitycompare_fee_estimatesno sensitive capabilitydecode_bolt11_invoiceno sensitive capabilitydecode_raw_transactionno sensitive capabilitydescribe_rpc_commandno sensitive capabilityestimate_smart_feeno sensitive capabilityestimate_transaction_costno sensitive capabilityexplain_inscription_listing_securityno sensitive capabilityexplain_scriptno sensitive capabilitygenerate_keypairno sensitive capabilityget_address_balanceno sensitive capabilityget_address_historyno sensitive capabilityget_address_utxosno sensitive capabilityget_block_countno sensitive capabilityget_block_statsno sensitive capabilityget_blockchain_infono sensitive capabilityget_btc_priceno sensitive capabilityget_chain_tipsno sensitive capabilityget_chain_tx_statsno sensitive capabilityget_difficulty_adjustmentno sensitive capabilityget_fee_estimatesno sensitive capabilityget_fee_recommendationno sensitive capabilityget_halving_countdownno sensitive capabilityget_indexed_transactionno sensitive capabilityget_indexer_statusno sensitive capabilityget_market_sentimentno sensitive capabilityget_mempool_ancestorsno sensitive capabilityget_mempool_entryno sensitive capabilityget_mempool_infono sensitive capabilityget_mining_infono sensitive capabilityget_mining_pool_rankingsno sensitive capabilityget_network_infono sensitive capabilityget_node_statusno sensitive capabilityget_peer_infono sensitive capabilityget_situation_summaryno sensitive capabilityget_supply_infono sensitive capabilityget_utxo_set_infono sensitive capabilitylist_rpc_commandsno sensitive capabilityquery_remote_apino sensitive capabilitysearch_blockchainno sensitive capabilitysearch_blocksno sensitive capabilitysend_raw_transactionno sensitive capabilityvalidate_addressno sensitive capabilityScan 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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.5.1 latest |
A 99/100 | 1 | 1.13.0 | 2026-08-25 |
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.
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
Independent packages implementing the same tool, scanned with the same engine. Compare all 5 side by side →
MCP server exposing honest monetary data to AI agents — purchasing power, M2 vs CPI divergence, Bitcoin vs dollar comparisons. No spin.
A Model Context Protocol (MCP) server that provides real-time Bitcoin blockchain data by querying the mempool.space API
A Model Context Protocol server for interacting with Bitcoin.
Security scan results for the Bitcoin (npm) MCP server.
<img src="./public/logo.png" alt="1Money Logo" width="200"/>
Signed verification attestations for agent decisions: business, price, freshness, claim checks.
Actual Budget MCP server exposing API functionality
MCP server for Actual Budget - query and manage your personal finances through Claude
The Adyen Model Context Protocol server allows you to integrate with Adyen APIs through LLMs function calling utilizing various Clients. It currently supports the following tools:
Trusted agent-commerce hub: discover, trust-check, and route x402 payments with failover.