Bitview

What Bitview does

Bitview MCP server gives AI agents query access to Bitcoin data. Its tools cover address metadata, confirmed and unconfirmed transactions, UTXOs, blocks, block headers, fee rates, rewards, sizes, weights, chain status, and difficulty adjustments. The interface is read-only, so it is suited to investigation, monitoring, and analysis rather than wallet control or transaction submission.

Address tools accept common Bitcoin address types, including P2PKH, P2SH, P2WPKH, P2WSH, P2TR, and P2A, along with compressed or uncompressed P2PK public keys represented as hexadecimal. Address history can include mempool transactions and confirmed transactions, with cursor-based continuation using a transaction ID.

How it works

The hosted Bitview deployment is available through the MCP endpoint at https://mcp.bitview.space/. The service also provides a web application, REST API, OpenAPI document, and command-line and language clients. Its underlying Bitview application turns Bitcoin Core data into a local data platform using the Bitcoin Research Kit, indexing components, analytics plugins, a query layer, and generated clients.

For local deployment, Bitview reads from a Bitcoin Core mainnet node with RPC access and complete blk*.dat files from genesis. The default setup builds an indexed view of the chain and serves its API and showcases on port 3110, bound to the local machine unless the server binding is changed. The MCP tools expose selected query operations over that data rather than mutation operations.

Setup and configuration

The hosted endpoint requires no account or authentication. A compatible MCP client can be configured to connect to the endpoint directly.

To self-host the daemon on Linux or macOS, install it with Rust and start it with:

rustup update && RUSTFLAGS="-C target-cpu=native" cargo install --locked bitviewd
bitviewd

A full self-hosted deployment needs a mainnet Bitcoin Core node with RPC enabled, the complete block-file history, approximately 290 GiB for Bitview in addition to Bitcoin Core storage and growth, and 16 GB of RAM recommended for a full sync. The repository also supports custom compositions and plugins through its Rust-based Bitview and BRK components.

Tools and capabilities

• Inspect address balances, transaction counts, UTXOs, confirmed history, and mempool history.
• Discover addresses by type and RapidHash v3 prefixes without sending raw addresses or extended public keys.
• Retrieve recent blocks, blocks by height, block hashes, headers, transaction IDs, and block transactions by index.
• Check block status, chain tip height, chain tip hash, and block timestamps.
• Analyze fee-rate percentiles, average block fees, rewards, sizes, and weights over selected periods.
• Review difficulty adjustment progress and historical adjustments.
• Examine CPFP ancestors, descendants, and effective package fee rates.

Most list operations impose bounded result sizes. Address history supports continuation with after_txid; block transaction retrieval uses a starting index in increments of 25.

Limitations and notes

Bitview is read-only: its MCP tools query Bitcoin state and analytics but do not send transactions or alter the chain. Some results distinguish confirmed chain data from live mempool data, and block-status queries identify whether a block belongs to the best chain. Self-hosting has substantial storage and synchronization requirements because it processes the Bitcoin Core chain from genesis. The hosted instance is the simpler option for agents that only need remote queries.