Bitcoin Data MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_blockA | Get block information by hash or height |
| get_transactionC | Get transaction information by txid |
| get_addressB | Get address information including balance and transaction history |
| get_utxosB | Get unspent transaction outputs for an address |
| get_price_dataC | Get current Bitcoin price and market data |
| get_historical_priceC | Get historical Bitcoin price data |
| get_network_metricsC | Get Bitcoin network health metrics |
| analyze_fee_landscapeC | Analyze current fee landscape and get recommendations |
| analyze_mempool_stateC | Analyze current mempool state |
| analyze_utxo_distributionB | Analyze UTXO distribution for multiple addresses |
| trace_coin_lineageB | Trace the lineage of coins from a transaction output |
| detect_transaction_patternsC | Detect patterns in a transaction (basic analysis) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool targets a distinct aspect of Bitcoin data, such as fee analysis, mempool state, UTXO distribution, transaction patterns, address info, block info, price data, network metrics, and coin lineage. There is no ambiguity or overlap between tools, making it clear which to use for a specific query.
All tool names follow a consistent verb_noun pattern using lowercase and underscores (e.g., analyze_fee_landscape, get_address, trace_coin_lineage). This uniformity aids predictability and ease of selection for agents.
With 12 tools, the server covers its domain without being sparse or overwhelming. The number is well-scoped for a Bitcoin data server, providing enough granularity without unnecessary redundancy.
The tool surface covers most key aspects of Bitcoin data: blockchain info, mempool, fees, UTXOs, transaction patterns, prices, and network metrics. A minor gap is the absence of a transaction broadcast tool, but for a data-focused server, this is acceptable.