Mempool Space
NPM · @PIPEWORX/MCP-MEMPOOL-SPACE · 2 COMPONENTS
mempool.space MCP — Bitcoin block explorer + mempool/fee stats
Available components
Last scanned (9 hours ago)
Scores higher than 76% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-mempool-space). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 968 tokens (~96/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 3 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- Stability: unverified → 0.17 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-mempool-space@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-mempool-space |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-mempool-space/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3655361109 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c874efb0d2e7adad2262c9143e9ab05c8424efcbeec38dc352890e080305bd5a290afbe02e753793d4b8558279a4f151fbfd193af2ab1ccf2c1c737be |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
block_height ~81
Return the current chain tip block height (latest mined block number) for mainnet, testnet, signet, or liquid.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Which Bitcoin network. Defaults to mainnet — the real Bitcoin network, which is what "Bitcoin" means in an ordinary question. "bitcoin" and "btc" are accepted as aliases for mainnet. |
No output schema declared.
No examples provided.
get_address ~71
Address summary (UTXO + tx counts).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| network | string | – | Which Bitcoin network. Defaults to mainnet — the real Bitcoin network, which is what "Bitcoin" means in an ordinary question. "bitcoin" and "btc" are accepted as aliases for mainnet. |
No output schema declared.
No examples provided.
get_address_transactions ~150
Recent Bitcoin transactions touching one address, read from the mempool.space block explorer API (mainnet by default; testnet, signet, and Liquid also selectable). Returns up to 50 transactions with txid, inputs, outputs, values in satoshis, fee, size, and confirmation status. Answers what a BTC address has been sending or receiving lately.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| limit | number | – | Default 25 (max ~50) |
| network | string | – | Which Bitcoin network. Defaults to mainnet — the real Bitcoin network, which is what "Bitcoin" means in an ordinary question. "bitcoin" and "btc" are accepted as aliases for mainnet. |
No output schema declared.
No examples provided.
get_block ~76
Block detail by hash or height.
| Name | Type | Req | Description |
|---|---|---|---|
| hash_or_height | string | yes | Block hash or numeric height |
| network | string | – | Which Bitcoin network. Defaults to mainnet — the real Bitcoin network, which is what "Bitcoin" means in an ordinary question. "bitcoin" and "btc" are accepted as aliases for mainnet. |
No output schema declared.
No examples provided.
get_transaction ~94
Fetch full transaction detail (inputs, outputs, fee, size, confirmation status) for a given txid on mainnet/testnet/signet/liquid.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Which Bitcoin network. Defaults to mainnet — the real Bitcoin network, which is what "Bitcoin" means in an ordinary question. "bitcoin" and "btc" are accepted as aliases for mainnet. |
| txid | string | yes | – |
No output schema declared.
No examples provided.
get_tx_status ~87
Return confirmation status (confirmed, block hash, block height) for a txid without fetching the full transaction body.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Which Bitcoin network. Defaults to mainnet — the real Bitcoin network, which is what "Bitcoin" means in an ordinary question. "bitcoin" and "btc" are accepted as aliases for mainnet. |
| txid | string | yes | – |
No output schema declared.
No examples provided.
hashrate ~113
Network hashrate + difficulty history.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Which Bitcoin network. Defaults to mainnet — the real Bitcoin network, which is what "Bitcoin" means in an ordinary question. "bitcoin" and "btc" are accepted as aliases for mainnet. |
| period | string | – | 1d | 3d | 1w | 1m | 3m | 6m | 1y | 2y | 3y | all (default 3m) |
No output schema declared.
No examples provided.
mempool_stats ~67
Current mempool size + tx count + total fees.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Which Bitcoin network. Defaults to mainnet — the real Bitcoin network, which is what "Bitcoin" means in an ordinary question. "bitcoin" and "btc" are accepted as aliases for mainnet. |
No output schema declared.
No examples provided.
mining_pools ~111
Block share by mining pool.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Which Bitcoin network. Defaults to mainnet — the real Bitcoin network, which is what "Bitcoin" means in an ordinary question. "bitcoin" and "btc" are accepted as aliases for mainnet. |
| period | string | – | 24h | 3d | 1w | 1m | 3m | 6m | 1y | 2y | 3y | all (default 1w) |
No output schema declared.
No examples provided.
recommended_fees ~63
Current sat/vB fee recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Which Bitcoin network. Defaults to mainnet — the real Bitcoin network, which is what "Bitcoin" means in an ordinary question. "bitcoin" and "btc" are accepted as aliases for mainnet. |
No output schema declared.
No examples provided.
How do I install the Mempool Space MCP server?
Mempool Space runs locally as an npm package, launched with npx -y @pipeworx/mcp-mempool-space. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-mempool-space
claude mcp add pipeworx-io-mempool-space -- npx -y @pipeworx/mcp-mempool-space
What is the Mempool Space MCP server?
Mempool Space is an MCP server listed in the public MCP registry as io.github.pipeworx-io/mempool-space. mempool.space MCP, Bitcoin block explorer + mempool/fee stats. This page covers its npm package (@pipeworx/mcp-mempool-space).
Is the Mempool Space MCP server safe to use?
Mempool Space scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Mempool Space MCP server expose?
Mempool Space exposes 10 tools: recommended_fees, mempool_stats, block_height, get_block, get_transaction, and 5 more. Their descriptions and schemas cost roughly 913 tokens of context every time the server is loaded.
Is the Mempool Space MCP server still maintained?
Mempool Space is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Mempool Space MCP server under?
Mempool Space declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.