mcp-mempool
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMPOOL_API_BASE | No | Base URL for the mempool.space API. Can be used to point to a self-hosted instance or other networks. | https://mempool.space/api |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_recommended_feesA | Get current recommended Bitcoin transaction fees in sat/vB (fastestFee, halfHourFee, hourFee, economyFee, minimumFee). Call this when the user asks what fee to use for a transaction right now. |
| get_mempool_statsA | Get the current state of the Bitcoin mempool: number of unconfirmed transactions, total virtual size (vBytes), and total pending fees in satoshis. Useful to judge network congestion. |
| get_tipA | Get the current Bitcoin chain tip: block height and block hash. |
| get_recent_blocksA | Get a summary of the most recent Bitcoin blocks: height, hash, timestamp, transaction count, size, and median fee. Returns up to 10 blocks. |
| get_transactionA | Get details for a Bitcoin transaction by txid: confirmation status, block height, fee, size, and inputs/outputs summary. |
| get_addressA | Get stats for a Bitcoin address: confirmed balance, total received/spent, and transaction counts (on-chain and in mempool). |
| get_priceA | Get the current Bitcoin price in USD, EUR, GBP, CAD, CHF, AUD, and JPY. |
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 7 tools
Each tool targets a distinct data resource: fees, mempool stats, chain tip, recent blocks, a specific transaction, an address, and price. No two tools overlap in purpose, making selection unambiguous.
All tools follow a consistent 'get_' verb + noun pattern (get_recommended_fees, get_mempool_stats, get_tip, get_recent_blocks, get_transaction, get_address, get_price). The naming scheme is uniform and predictable.
Seven tools is well-scoped for a mempool/blockchain information server. Each tool addresses a common need without redundancy, and the count is within the ideal 3-15 range.
The server covers fees, mempool state, chain tip, recent blocks, transactions, addresses, and price—covering the primary read-only use cases. A notable minor gap is the lack of a way to fetch a specific block by height or hash, but this is not critical for typical mempool queries.