mempool

This MCP server exposes a suite of Bitcoin data tools powered by mempool.space APIs. It runs as a tool provider that you can connect to from any MCP-compatible client (such as Claude, Cursor, or VS Code). The server offers a broad set of tools including current blockchain and mempool stats, price data, transaction fees, block details, address info, and many more, enabling AI agents to query live Bitcoin information and perform complex lookups through a standardized MCP interface. To use it, configure your MCP client to point to the mempool-mcp-server tool provider (for example via npx) and, if desired, supply a MEMPOOL_BASE_URL to override the default API base URL.

Once configured, you can invoke individual tools by name (for example get-mempool-info, get-blocks, get-address-txs, get-tx-info, get-recommended-fees, get-price, etc.) depending on the capabilities you need. The server translates these requests into mempool.space API calls and returns structured results suitable for downstream AI processing, summaries, or decision making.

Prerequisites:

• Node.js and npm installed on your machine
• Internet access to fetch the MCP server package

1. Clone this repository (optional if you are using the published package):

git clone https://github.com/alexandresanlim/mempool-mcp-server.git
cd mempool-mcp-server

2. Install dependencies and build the project (if you are using a local build workflow):

npm install
npm run build

3. Run the MCP server using npx (as described in the README):

npx @sanlim/mempool-mcp-server

4. Alternatively, configure your MCP client to load the server as a tool provider via package name:

"mempool-mcp-server": {
  "command": "npx",
  "args": [
    "@sanlim/mempool-mcp-server"
  ]
}

5. If you want to customize the API base URL to point at your own mempool API endpoint, set MEMPOOL_BASE_URL in your environment:

"mempool-mcp-server": {
  "command": "npx",
  "args": ["@sanlim/mempool-mcp-server"],
  "env": {
    "MEMPOOL_BASE_URL": "http://umbrel.local:3006/api"
  }
}

6. Start the server and connect your MCP client, ensuring the client uses standard input/output for communication.

Tips and notes:

• The server uses mempool.space APIs; if you want private/local data, you can override the base URL with MEMPOOL_BASE_URL as shown in the examples.
• Common issues include network access problems or misconfigured MCP client I/O channels. Ensure the client communicates via stdio as required by MCP.
• The list of available tools is extensive (e.g., get-difficulty-adjustment, get-mempool-info, get-blocks, get-tx-info, get-address-txs, get-tx-status, get-block-header, etc.). Refer to the README for the full set and exact tool names.
• When upgrading the server, rebuild if you are using a local build workflow to pick up any API or feature changes.