Bitcoin MCP
UnclaimedBitcoin MCP server with 50 standard tools for fees, mempool, blocks, transactions, mining, price, and supply. Supports Bitcoin Core and compatible API backends.
Install
uvx --from bitcoin-mcp>=0.5.2 bitcoin-mcpSet up this server
More in AI & ML
Browse the full directoryUnclaimed listing
Is this your MCP server?
This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.
Claim this serverSecurity profile
Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works
40 of 40 tools
Documented tools (40)
From project documentation. A server handshake does not verify each tool’s description or behavior.
analyze_block
Deep analysis of any block by height or hash
analyze_mempool
Full mempool analysis — depth, fees, congestion
analyze_next_block
Preview of the next block template
analyze_transaction
Full transaction analysis with inscription detection
check_utxo
Check if a UTXO is spent or unspent
compare_blocks
Compare two blocks side by side
compare_fee_estimates
Side-by-side comparison of fee sources
decode_raw_transaction
Decode a raw transaction hex
estimate_smart_fee
Fee estimate for a specific confirmation target
estimate_transaction_cost
Exact cost estimate for a transaction before sending
get_address_balance
Total received/sent/balance, tx count, first/last seen
get_address_history
Paginated transaction history with net value change
get_address_transactions
Transaction history with per-transaction value details
get_address_utxos
UTXOs for an address
get_block_count
Current chain height
get_block_stats
Statistical breakdown of a block
get_blockchain_info
Chain state, verification progress, softfork status
get_btc_price
Current BTC/USD price
get_chain_tips
Active and stale chain tips
get_chain_tx_stats
Transaction throughput over N blocks
get_difficulty_adjustment
Time and percentage of next difficulty change
get_fee_estimates
Fee estimates across all confirmation targets
get_fee_recommendation
Optimal fee rate with urgency tiers and savings tips
get_halving_countdown
Blocks and estimated time until next halving
get_indexed_transaction
Enriched tx with resolved input addresses + spent status
get_market_sentiment
Fear/greed index and market indicators
get_mempool_ancestors
Ancestor chain for a mempool transaction
get_mempool_entry
Details for a specific unconfirmed transaction
get_mempool_info
Mempool size, bytes, fee floor
get_mining_info
Current mining difficulty, hashrate, block reward
get_mining_pool_rankings
Top mining pools by recent blocks
get_network_info
Node version, connections, relay info
get_node_status
Connection status and node health
get_peer_info
Connected peer details
get_situation_summary
Aggregated overview — price, fees, mempool, mining
get_supply_info
Circulating supply, inflation rate, percent mined
get_utxo_set_info
UTXO set size and total supply
search_blocks
Search a range of blocks
send_raw_transaction
Broadcast a signed transaction
validate_address
Validate and classify a Bitcoin address
Tool change history
FAQ
Questions about Bitcoin MCP Server
- How do I connect Bitcoin MCP Server to Claude?
- The listing records `uvx --from bitcoin-mcp>=0.5.2 bitcoin-mcp` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Desktop, Claude Code, Cursor as compatible clients.
- Is Bitcoin MCP Server free?
- The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
- What can Bitcoin MCP Server do?
- Bitcoin MCP Server documents 40 tools to the agent, including analyze_block, analyze_mempool, analyze_next_block. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.