Provides tools for querying live Bitcoin data from mempool.space, including recommended fees, mempool statistics, blocks, transactions, address balances, and price.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-mempool What are the current Bitcoin fees and mempool stats?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP (Model Context Protocol) server for the mempool.space Bitcoin API. No API key required.
Lets any MCP client (Claude Code, Claude Desktop, etc.) query live Bitcoin data: recommended fees, mempool state, blocks, transactions, addresses, price.
Tool | Arguments | Returns |
| — | Fee estimates in sat/vB (fastest, 30 min, 1 h, economy, minimum) |
| — | Unconfirmed tx count, total vsize, total pending fees |
| — | Current block height and hash |
|
| Recent blocks: height, time, tx count, median fee, mining pool |
|
| Confirmation status, fee, fee rate, inputs/outputs |
|
| Confirmed balance, received total, tx counts, pending delta |
| — | BTC price in USD, EUR, GBP, CAD, CHF, AUD, JPY |
Related MCP server: mcp-l402-gate-example
npm install
npm run buildexamples/client.mjs spawns the server over stdio and calls each tool:
npm run exampleclaude mcp add mempool -- node /path/to/mcp-mempool/dist/index.jsThen ask, for example: "quels frais je mets pour une transaction confirmée dans l'heure ?"
Add to claude_desktop_config.json:
{
"mcpServers": {
"mempool": {
"command": "node",
"args": ["/path/to/mcp-mempool/dist/index.js"]
}
}
}Set MEMPOOL_API_BASE to point elsewhere (default: https://mempool.space/api):
{
"mcpServers": {
"mempool-testnet": {
"command": "node",
"args": ["/path/to/mcp-mempool/dist/index.js"],
"env": { "MEMPOOL_API_BASE": "https://mempool.space/testnet4/api" }
}
}
}Works with any mempool.space-compatible instance (e.g. a self-hosted one on your own node).
Uses the public REST API; heavy usage should point MEMPOOL_API_BASE at a self-hosted instance (mempool.space rate-limits aggressively).
API errors are returned as MCP tool errors (isError: true) with the upstream message, so the model can react to them.
MIT
Get stats for a Bitcoin address: confirmed balance, total received/spent, and transaction counts (on-chain and in mempool).
Inputs: address (required).
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.
Inputs: no named parameters.
Get the current Bitcoin price in USD, EUR, GBP, CAD, CHF, AUD, and JPY.
Inputs: no named parameters.
Get a summary of the most recent Bitcoin blocks: height, hash, timestamp, transaction count, size, and median fee. Returns up to 10 blocks.
Inputs: limit.
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.
Inputs: no named parameters.
Get the current Bitcoin chain tip: block height and block hash.
Inputs: no named parameters.
Get details for a Bitcoin transaction by txid: confirmation status, block height, fee, size, and inputs/outputs summary.
Inputs: txid (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
mempool.space MCP — Bitcoin block explorer + mempool/fee stats
Bitcoin MCP for fee budgets, transaction proofs and address checks. Free service discovery.
Bitcoin full node data via MCP: fees, mempool, txs, whales, SEC. $0.001/call USDC on Base.
Unlock the power of real-time cryptocurrency data with our Crypto Price Insights MCP server.