Bitview
REMOTE · MCP.BITVIEW.SPACE
Read-only Bitcoin blockchain, mempool, mining, market, and on-chain analytics; no API key.
Available components
Last scanned (1 hour ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 6950 tokens (~92/item across 75 items; 75 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability check failed: schema churn in the 30 days we've observed: 12 tool removals, 3 breaking changes, 0 auth/transport breaks, 8 additions. See how to fix → Fail
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 47% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 75 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 76 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 2 Nov 26 0
- Server version: 0.12.2 → 0.13.0 functional
- 31 Oct 26 −11
- Authorization: partial → unverified ▼ security
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 0.12.2 ▼ security
- Tool “get_block_by_height” was removed ▼ security
- Tool “get_indexes” was removed ▼ security
- Tool “get_mempool_hash” was removed ▼ security
- Tool “get_oracle_histogram_outputs” was removed ▼ security
- Tool “get_oracle_histogram_outputs_live” was removed ▼ security
- Tool “get_oracle_histogram_payments” was removed ▼ security
- Tool “get_oracle_histogram_payments_live” was removed ▼ security
- Tool “get_pool_blocks_from” was removed ▼ security
- Tool “get_pool_stats” was removed ▼ security
- Tool “get_tx_by_index” was removed ▼ security
- Tool “get_urpd_at” was removed ▼ security
- Tool “list_urpd_dates” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_address” rewrote its description, which is the text the model reads security
- Tool “get_address_confirmed_txs” rewrote its description, which is the text the model reads security
- Tool “get_address_confirmed_txs_after” rewrote its description, which is the text the model reads security
- Tool “get_address_hash_prefix_matches” rewrote its description, which is the text the model reads security
- Tool “get_address_mempool_txs” rewrote its description, which is the text the model reads security
- Tool “get_address_txs” rewrote its description, which is the text the model reads security
- Tool “get_address_utxos” rewrote its description, which is the text the model reads security
- Tool “get_block” rewrote its description, which is the text the model reads security
- Tool “get_block_by_timestamp” rewrote its description, which is the text the model reads security
- Tool “get_block_fee_rates” rewrote its description, which is the text the model reads security
- Tool “get_block_fees” rewrote its description, which is the text the model reads security
- Tool “get_block_rewards” rewrote its description, which is the text the model reads security
- Tool “get_block_sizes_weights” rewrote its description, which is the text the model reads security
- Tool “get_block_status” rewrote its description, which is the text the model reads security
- Tool “get_block_tip_hash” rewrote its description, which is the text the model reads security
- Tool “get_block_tip_height” rewrote its description, which is the text the model reads security
- Tool “get_block_txs_from_index” rewrote its description, which is the text the model reads security
- Tool “get_blocks” rewrote its description, which is the text the model reads security
- Tool “get_blocks_from_height” rewrote its description, which is the text the model reads security
- Tool “get_blocks_v1_from_height” rewrote its description, which is the text the model reads security
- Tool “get_cpfp” rewrote its description, which is the text the model reads security
- Tool “get_difficulty_adjustments” rewrote its description, which is the text the model reads security
- Tool “get_difficulty_adjustments_by_period” rewrote its description, which is the text the model reads security
- Tool “get_hashrate_by_period” rewrote its description, which is the text the model reads security
- Tool “get_historical_price” rewrote its description, which is the text the model reads security
- Tool “get_mempool” rewrote its description, which is the text the model reads security
- Tool “get_pool” rewrote its description, which is the text the model reads security
- Tool “get_pool_blocks” rewrote its description, which is the text the model reads security
- Tool “get_pools” rewrote its description, which is the text the model reads security
- Tool “get_pools_hashrate” rewrote its description, which is the text the model reads security
- Tool “get_pools_hashrate_by_period” rewrote its description, which is the text the model reads security
- Tool “get_replacements” rewrote its description, which is the text the model reads security
- Tool “get_series” rewrote its description, which is the text the model reads security
- Tool “get_series_info” rewrote its description, which is the text the model reads security
- Tool “get_series_len” rewrote its description, which is the text the model reads security
- Tool “get_series_version” rewrote its description, which is the text the model reads security
- Tool “get_sync_status” rewrote its description, which is the text the model reads security
- Tool “get_transaction_times” rewrote its description, which is the text the model reads security
- Tool “get_tx” rewrote its description, which is the text the model reads security
- Tool “get_tx_hex” rewrote its description, which is the text the model reads security
- Tool “get_tx_merkle_proof” rewrote its description, which is the text the model reads security
- Tool “get_tx_outspend” rewrote its description, which is the text the model reads security
- Tool “get_tx_outspends” rewrote its description, which is the text the model reads security
- Tool “get_tx_status” rewrote its description, which is the text the model reads security
- Tool “get_urpd” rewrote its description, which is the text the model reads security
- Tool “list_series” rewrote its description, which is the text the model reads security
- Tool “list_urpd_cohorts” rewrote its description, which is the text the model reads security
- Tool “search_series” rewrote its description, which is the text the model reads security
- Tool “validate_address” rewrote its description, which is the text the model reads security
- “get_address_hash_prefix_matches” added a required parameter “address_type”, so existing callers break ▼ functional
- “get_transaction_times” added a required parameter “txids”, so existing callers break ▼ functional
- “get_urpd” added a required parameter “point”, so existing callers break ▼ functional
- “get_address_hash_prefix_matches” dropped the required parameter “addr_type” ▼ functional
- “get_transaction_times” dropped the required parameter “txId[]” ▼ functional
- Tool coverage: 90% → 100% ▲ functional
- Tool “get_block_header” now declares an output schema ▲ functional
- Tool “get_block_tip_hash” now declares an output schema ▲ functional
- Tool “get_block_tip_height” now declares an output schema ▲ functional
- Tool “get_block_txid” now declares an output schema ▲ functional
- Tool “get_tx_hex” now declares an output schema ▲ functional
- Tool “get_tx_merkleblock_proof” now declares an output schema ▲ functional
- Schema quality: excellent → good functional
- New tool “get_block_fee_rates_precise” functional
- New tool “get_block_hash_by_height” functional
- New tool “get_pool_blocks_from_height” functional
- New tool “get_pool_ranking” functional
- New tool “get_txid_by_index” functional
- New tool “get_urpd_latest” functional
- New tool “get_utxo_set_diff” functional
- New tool “list_indexes” functional
- “get_address_confirmed_txs” added an optional parameter “max_txs” cosmetic
- “get_address_confirmed_txs_after” added an optional parameter “max_txs” cosmetic
- “get_address_mempool_txs” added an optional parameter “max_txs” cosmetic
- “get_address_txs” added an optional parameter “after_txid” cosmetic
- “get_address_txs” added an optional parameter “max_txs” cosmetic
- “get_historical_price” added an optional parameter “currency” cosmetic
- “get_block_fee_rates” reworded the description of “time_period” cosmetic
- “get_block_fees” reworded the description of “time_period” cosmetic
- “get_block_rewards” reworded the description of “time_period” cosmetic
- “get_block_sizes_weights” reworded the description of “time_period” cosmetic
- “get_block_txid” reworded the description of “hash” cosmetic
- “get_block_txs_from_index” reworded the description of “hash” cosmetic
- “get_difficulty_adjustments_by_period” reworded the description of “time_period” cosmetic
- “get_hashrate_by_period” reworded the description of “time_period” cosmetic
- “get_historical_price” reworded the description of “timestamp” cosmetic
- “get_pools_hashrate_by_period” reworded the description of “time_period” cosmetic
- “get_series” reworded the description of “end” cosmetic
- “get_series” reworded the description of “format” cosmetic
- “get_series” reworded the description of “index” cosmetic
- “get_series” reworded the description of “limit” cosmetic
- “get_series” reworded the description of “series” cosmetic
- “get_series” reworded the description of “start” cosmetic
- “get_series_bulk” reworded the description of “end” cosmetic
- “get_series_bulk” reworded the description of “format” cosmetic
- “get_series_bulk” reworded the description of “index” cosmetic
- “get_series_bulk” reworded the description of “limit” cosmetic
- “get_series_bulk” reworded the description of “series” cosmetic
- “get_series_bulk” reworded the description of “start” cosmetic
- “get_series_latest” reworded the description of “index” cosmetic
- “get_series_latest” reworded the description of “series” cosmetic
- “get_series_len” reworded the description of “index” cosmetic
- “get_series_len” reworded the description of “series” cosmetic
- “get_series_version” reworded the description of “index” cosmetic
- “get_series_version” reworded the description of “series” cosmetic
- “get_tx_outspend” reworded the description of “txid” cosmetic
- “get_urpd” reworded the description of “agg” cosmetic
- “get_urpd” reworded the description of “weight” cosmetic
- “list_series” reworded the description of “page” cosmetic
- “list_series” reworded the description of “per_page” cosmetic
- “search_series” reworded the description of “limit” cosmetic
- “search_series” reworded the description of “q” cosmetic
- “validate_address” reworded the description of “address” cosmetic
- Tool “get_urpd” changed its title: Latest URPD → URPD at block height or date cosmetic
- 23 Oct 26 +1
- Stability: 0.97 → pass security
- 22 Oct 26 −1
- Stability: pass → 0.97 functional
- 29 Sept 26 0
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 0
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Schema quality: 72 → 84 ▼ functional
- Schema quality: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: fail → 0.80 functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 · Probed https://mcp.bitview.space/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bitview.space | CN=WE1,O=Google Trust Services,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d1829f095933835e0e6701a13fc0fead |
| SANs: bitview.space, *.bitview.space | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.bitview.space. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| space. | present | 51168 | 13 | Verified |
| bitview.space. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.bitview.space/ | Verified | 200 | |
| http (plaintext) | http://mcp.bitview.space/ | HTTPS enforced | 301 | https://mcp.bitview.space/ |
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 →
get_address Address information ~95
Balance and transaction counts. Supports P2PKH, P2SH, P2WPKH, P2WSH, P2TR and P2A addresses, and P2PK public keys in hex (33 or 65 bytes). *[Mempool.space docs](https://mempool.space/docs/api/rest#get-address)* REST operation: `GET /api/address/{address}`.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_address_confirmed_txs Address confirmed transactions ~134
Get the newest confirmed transactions for an address, up to `max_txs` (25 by default and at most). For pagination, request `GET /api/address/{address}/txs/chain/{after_txid}` with the last returned txid. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-address-transactions-chain)* REST operation: `GET /api/address/{address}/txs/chain`.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | yes | – |
| max_txs | integer | – | Transactions to return, at most 25 (the default); larger values return 25. |
Structured output declared, but exposes no named fields.
No examples provided.
get_address_confirmed_txs_after Address confirmed transactions (paginated) ~163
Get the next confirmed transactions strictly older than `after_txid`, up to `max_txs` (25 by default and at most); a txid outside the address's history answers `[]` (Esplora-canonical pagination form, matches mempool.space). *[Mempool.space docs](https://mempool.space/docs/api/rest#get-address-transactions-chain)* REST operation: `GET /api/address/{address}/txs/chain/{after_txid}`.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | yes | – |
| after_txid | – | yes | Last txid from the previous page (return transactions strictly older than this) |
| max_txs | integer | – | Transactions to return, at most 25 (the default); larger values return 25. |
Structured output declared, but exposes no named fields.
No examples provided.
get_address_hash_prefix_matches Address hash-prefix matches ~123
Find addresses by address type and by the first 1-16 hex nibbles of RapidHash v3 over the raw address payload bytes. Intended for privacy-preserving client-side wallet discovery without sending raw addresses or xpubs. Fetch metadata with `GET /api/address/{address}`. REST operation: `GET /api/address/hash-prefix/{address_type}/{prefix}`.
| Name | Type | Req | Description |
|---|---|---|---|
| address_type | – | yes | – |
| prefix | string | yes | First 1–16 hexadecimal nibbles of the RapidHash v3 hash over the raw address payload bytes. |
Structured output declared, but exposes no named fields.
No examples provided.
get_address_mempool_txs Address mempool transactions ~116
Get unconfirmed transactions for an address from the mempool, newest first, up to `max_txs` (50 by default and at most). *[Mempool.space docs](https://mempool.space/docs/api/rest#get-address-transactions-mempool)* REST operation: `GET /api/address/{address}/txs/mempool`.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | yes | – |
| max_txs | integer | – | Transactions to return, at most 50 (the default); larger values return 50. |
Structured output declared, but exposes no named fields.
No examples provided.
get_address_txs Address transactions ~191
Get transaction history for an address, newest first: up to `max_txs` (50 by default and at most), mempool transactions first and confirmed ones filling the rest. To continue, pass the last returned txid as `after_txid`, or request `GET /api/address/{address}/txs/chain/{after_txid}` for confirmed history. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-address-transactions)* REST operation: `GET /api/address/{address}/txs`.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | yes | – |
| after_txid | – | – | Continue after this transaction, a mempool or a confirmed one: the older ones (a confirmed cursor skips the mempool). One that is neither answers 422. |
| max_txs | integer | – | Transactions to return, at most 50 (the default); larger values return 50. |
Structured output declared, but exposes no named fields.
No examples provided.
get_address_utxos Address UTXOs ~81
Get unspent transaction outputs (UTXOs) for an address, including unconfirmed ones; outputs that mempool transactions spend are left out. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-address-utxo)* REST operation: `GET /api/address/{address}/utxo`.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_block Block information ~46
*[Mempool.space docs](https://mempool.space/docs/api/rest#get-block)* REST operation: `GET /api/block/{hash}`.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_block_by_timestamp Block by timestamp ~79
Find the block with the greatest header timestamp at or before the given UNIX timestamp, choosing the earliest height on ties. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-timestamp)* REST operation: `GET /api/v1/mining/blocks/timestamp/{timestamp}`.
| Name | Type | Req | Description |
|---|---|---|---|
| timestamp | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_block_fee_rates Block fee rates ~158
Get block fee rate percentiles (min, 10th, 25th, median, 75th, 90th, max) for a time period, each a whole sat/vB (`/precise` for 3 decimals). *[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-feerates)* REST operation: `GET /api/v1/mining/blocks/fee-rates/{time_period}`.
| Name | Type | Req | Description |
|---|---|---|---|
| time_period | – | yes | Lookback period: `24h`, `3d`, `1w`, `1m`, `3m`, `6m`, `1y`, `2y`, `3y`, `4y` or `all`. |
Structured output declared, but exposes no named fields.
No examples provided.
get_block_fee_rates_precise Block fee rates (precise) ~156
Get block fee rate percentiles (min, 10th, 25th, median, 75th, 90th, max) for a time period, each in sat/vB to 3 decimals. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-feerates)* REST operation: `GET /api/v1/mining/blocks/fee-rates/{time_period}/precise`.
| Name | Type | Req | Description |
|---|---|---|---|
| time_period | – | yes | Lookback period: `24h`, `3d`, `1w`, `1m`, `3m`, `6m`, `1y`, `2y`, `3y`, `4y` or `all`. |
Structured output declared, but exposes no named fields.
No examples provided.
get_block_fees Block fees ~116
Get average total fees per block for a time period. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-fees)* REST operation: `GET /api/v1/mining/blocks/fees/{time_period}`.
| Name | Type | Req | Description |
|---|---|---|---|
| time_period | – | yes | Lookback period: `24h`, `3d`, `1w`, `1m`, `3m`, `6m`, `1y`, `2y`, `3y`, `4y` or `all`. |
Structured output declared, but exposes no named fields.
No examples provided.
get_block_hash_by_height Block hash by height ~56
Block hash as plain text. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-height)* REST operation: `GET /api/block-height/{height}`.
| Name | Type | Req | Description |
|---|---|---|---|
| height | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_block_header Block header ~59
Returns the hex-encoded 80-byte block header. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-header)* REST operation: `GET /api/block/{hash}/header`.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_block_rewards Block rewards ~123
Get average coinbase reward (subsidy + fees) per block for a time period. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-rewards)* REST operation: `GET /api/v1/mining/blocks/rewards/{time_period}`.
| Name | Type | Req | Description |
|---|---|---|---|
| time_period | – | yes | Lookback period: `24h`, `3d`, `1w`, `1m`, `3m`, `6m`, `1y`, `2y`, `3y`, `4y` or `all`. |
Structured output declared, but exposes no named fields.
No examples provided.
get_block_sizes_weights Block sizes and weights ~119
Get average block sizes and weights for a time period. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-sizes-weights)* REST operation: `GET /api/v1/mining/blocks/sizes-weights/{time_period}`.
| Name | Type | Req | Description |
|---|---|---|---|
| time_period | – | yes | Lookback period: `24h`, `3d`, `1w`, `1m`, `3m`, `6m`, `1y`, `2y`, `3y`, `4y` or `all`. |
Structured output declared, but exposes no named fields.
No examples provided.
get_block_status Block status ~92
Whether the block is in the best chain and, if so, its height and the hash of the next block. A block outside the best chain (orphaned or unknown) reports `in_best_chain: false`. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-status)* REST operation: `GET /api/block/{hash}/status`.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_block_tip_hash Block tip hash ~47
*[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-tip-hash)* REST operation: `GET /api/blocks/tip/hash`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_block_tip_height Block tip height ~47
*[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-tip-height)* REST operation: `GET /api/blocks/tip/height`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_block_txid Transaction ID at index ~87
Retrieve a single transaction ID at a specific index within a block. Returns plain text txid. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-transaction-id)* REST operation: `GET /api/block/{hash}/txid/{index}`.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | – | yes | – |
| index | – | yes | Transaction index within the block (0-based) |
Structured output declared, but exposes no named fields.
No examples provided.
get_block_txs_from_index Block transactions (paginated) ~89
Up to 25 transactions starting at `start_index`, a multiple of 25. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-transactions)* REST operation: `GET /api/block/{hash}/txs/{start_index}`.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | – | yes | – |
| start_index | – | yes | Starting transaction index within the block (0-based) |
Structured output declared, but exposes no named fields.
No examples provided.
get_block_v1 Block (v1) ~59
Returns block details with extras by hash. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-v1)* REST operation: `GET /api/v1/block/{hash}`.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_blocks Recent blocks ~45
The last 10 blocks. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-blocks)* REST operation: `GET /api/blocks`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_blocks_from_height Blocks from height ~101
Retrieve up to 10 blocks going backwards from the given height. For example, height=100 returns blocks 100, 99, 98, ..., 91. Height=0 returns only block 0. A height past the tip is not found. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-blocks)* REST operation: `GET /api/blocks/{height}`.
| Name | Type | Req | Description |
|---|---|---|---|
| height | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_blocks_v1 Recent blocks with extras ~61
Retrieve the last 15 blocks with extended data including pool identification and fee statistics. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-blocks-v1)* REST operation: `GET /api/v1/blocks`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_blocks_v1_from_height Blocks from height with extras ~93
Retrieve up to 15 blocks with extended data going backwards from the given height: the published blocks among the 15 heights ending at it, so fewer (or none) past the tip. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-blocks-v1)* REST operation: `GET /api/v1/blocks/{height}`.
| Name | Type | Req | Description |
|---|---|---|---|
| height | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_cpfp CPFP info ~123
Returns ancestors and descendants for a CPFP (Child Pays For Parent) transaction, including the effective fee rate of the package. A mempool transaction answers its live package; a confirmed one its package among its block's transactions; an unknown transaction, or a confirmed one without relatives in its block, `{"ancestors":[]}`. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-children-pay-for-parent)* REST operation: `GET /api/v1/cpfp/{txid}`.
| Name | Type | Req | Description |
|---|---|---|---|
| txid | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_difficulty_adjustment Difficulty adjustment ~56
Get current difficulty adjustment progress and estimates. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-difficulty-adjustment)* REST operation: `GET /api/v1/difficulty-adjustment`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_difficulty_adjustments Difficulty adjustments (all time) ~51
*[Mempool.space docs](https://mempool.space/docs/api/rest#get-difficulty-adjustments)* REST operation: `GET /api/v1/mining/difficulty-adjustments`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_difficulty_adjustments_by_period Difficulty adjustments ~118
Get historical difficulty adjustments for a time period. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-difficulty-adjustments)* REST operation: `GET /api/v1/mining/difficulty-adjustments/{time_period}`.
| Name | Type | Req | Description |
|---|---|---|---|
| time_period | – | yes | Lookback period: `24h`, `3d`, `1w`, `1m`, `3m`, `6m`, `1y`, `2y`, `3y`, `4y` or `all`. |
Structured output declared, but exposes no named fields.
No examples provided.
get_fullrbf_replacements Recent full-RBF replacements ~82
Same response shape as `GET /api/v1/replacements`, but limited to trees where at least one predecessor was non-signaling (full-RBF). *[Mempool.space docs](https://mempool.space/docs/api/rest#get-fullrbf-replacements)* REST operation: `GET /api/v1/fullrbf/replacements`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_hashrate Network hashrate (all time) ~57
Get network hashrate and difficulty data for all time. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-hashrate)* REST operation: `GET /api/v1/mining/hashrate`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_hashrate_by_period Network hashrate ~117
Get network hashrate and difficulty data for a time period. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-hashrate)* REST operation: `GET /api/v1/mining/hashrate/{time_period}`.
| Name | Type | Req | Description |
|---|---|---|---|
| time_period | – | yes | Lookback period: `24h`, `3d`, `1w`, `1m`, `3m`, `6m`, `1y`, `2y`, `3y`, `4y` or `all`. |
Structured output declared, but exposes no named fields.
No examples provided.
get_historical_price Historical price ~156
Completed four-hour BTC/USD closes, newest first as mempool.space lists them, labeled by interval end, from the first priced interval (2010-08-16). With a UNIX timestamp, returns the latest nonempty completed close at or before it; before the first close returns an empty list. The current partial interval is excluded. USD only (`currency` accepts `USD`); exchangeRates is empty. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-historical-price)* REST operation: `GET /api/v1/historical-price`.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | – | – | Quote currency: USD, the only one served |
| timestamp | – | – | UNIX timestamp: the latest close at or before it |
Structured output declared, but exposes no named fields.
No examples provided.
get_mempool Mempool statistics ~44
*[Mempool.space docs](https://mempool.space/docs/api/rest#get-mempool)* REST operation: `GET /api/mempool`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_mempool_blocks Projected mempool blocks ~83
Projected blocks for fee estimation. Block 0 reflects Bitcoin Core's actual next-block selection; blocks 1+ are a fee-tier approximation. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-mempool-blocks-fees)* REST operation: `GET /api/v1/fees/mempool-blocks`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_mempool_recent Recent mempool transactions ~60
Get the last 10 transactions to enter the mempool. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-mempool-recent)* REST operation: `GET /api/mempool/recent`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_pool Mining pool details ~65
Block counts and mining shares by time period for one pool. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-mining-pool)* REST operation: `GET /api/v1/mining/pool/{slug}`.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_pool_blocks Mining pool blocks ~70
Get up to 100 recent blocks mined by a specific pool. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-mining-pool-blocks)* REST operation: `GET /api/v1/mining/pool/{slug}/blocks`.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_pool_blocks_from_height Mining pool blocks before height ~97
Get up to 100 blocks mined by a specific pool strictly below the given height (pass the last height of a page to get the next one). *[Mempool.space docs](https://mempool.space/docs/api/rest#get-mining-pool-blocks)* REST operation: `GET /api/v1/mining/pool/{slug}/blocks/{height}`.
| Name | Type | Req | Description |
|---|---|---|---|
| height | – | yes | – |
| slug | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_pool_hashrate Mining pool hashrate ~71
Get hashrate history for a specific mining pool. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-mining-pool-hashrate)* REST operation: `GET /api/v1/mining/pool/{slug}/hashrate`.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_pool_ranking Mining pool statistics ~113
Get mining pool statistics for a time period. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-mining-pools)* REST operation: `GET /api/v1/mining/pools/{time_period}`.
| Name | Type | Req | Description |
|---|---|---|---|
| time_period | – | yes | Lookback period: `24h`, `3d`, `1w`, `1m`, `3m`, `6m`, `1y`, `2y`, `3y`, `4y` or `all`. |
Structured output declared, but exposes no named fields.
No examples provided.
get_pools List all mining pools ~47
*[Mempool.space docs](https://mempool.space/docs/api/rest#get-mining-pools)* REST operation: `GET /api/v1/mining/pools`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_pools_hashrate All pools hashrate (all time) ~84
Get weekly hashrate data, over the whole chain, of the mining pools that mined in the last week, by time and then their weekly rank. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-mining-pool-hashrates)* REST operation: `GET /api/v1/mining/hashrate/pools`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_pools_hashrate_by_period All pools hashrate ~143
Get weekly hashrate data, for a time period, of the mining pools that mined in the last week, by time and then their weekly rank. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-mining-pool-hashrates)* REST operation: `GET /api/v1/mining/hashrate/pools/{time_period}`.
| Name | Type | Req | Description |
|---|---|---|---|
| time_period | – | yes | Lookback period: `24h`, `3d`, `1w`, `1m`, `3m`, `6m`, `1y`, `2y`, `3y`, `4y` or `all`. |
Structured output declared, but exposes no named fields.
No examples provided.
get_precise_fees Recommended fee rates (precise) ~75
Recommended fee rates by confirmation target, with up to three decimal places and support for sub-sat/vB rates. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-recommended-fees-precise)* REST operation: `GET /api/v1/fees/precise`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_prices Current BTC price ~52
Returns bitcoin latest price (on-chain derived, USD only). *[Mempool.space docs](https://mempool.space/docs/api/rest#get-price)* REST operation: `GET /api/v1/prices`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_replacements Recent RBF replacements ~86
Returns up to 25 most-recent RBF replacement trees across the whole mempool. Each entry has the shape of `replacements` in `GET /api/v1/tx/{txid}/rbf`. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-replacements)* REST operation: `GET /api/v1/replacements`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_reward_stats Mining reward statistics ~85
Get mining reward statistics for the last N blocks including total rewards, fees, and transaction count. *[Mempool.space docs](https://mempool.space/docs/api/rest#get-reward-stats)* REST operation: `GET /api/v1/mining/reward-stats/{block_count}`.
| Name | Type | Req | Description |
|---|---|---|---|
| block_count | integer | yes | Number of recent blocks to include |
Structured output declared, but exposes no named fields.
No examples provided.
get_series Get series data ~148
Rows selected by a range of positions, dates or timestamps, as JSON or CSV. REST operation: `GET /api/series/{series}/{index}`.
| Name | Type | Req | Description |
|---|---|---|---|
| end | – | – | Exclusive end: integer index, date (YYYY-MM-DD), or timestamp (ISO 8601). Negative integers count from end. |
| format | – | – | – |
| index | – | yes | – |
| limit | – | – | Maximum number of values to return; with `end` too, the tighter of the two applies. Omitted, the rest of the range. |
| series | – | yes | – |
| start | – | – | Inclusive start: integer index, date (YYYY-MM-DD), or timestamp (ISO 8601). Negative integers count from end. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Bitview MCP server?
Bitview is a hosted endpoint at https://mcp.bitview.space/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.bitview.space
claude mcp add --transport http bitcoinresearchkit-bitview 'https://mcp.bitview.space/'
What is the Bitview MCP server?
Bitview is an MCP server listed in the public MCP registry as io.github.bitcoinresearchkit/bitview. Read-only Bitcoin blockchain, mempool, mining, market, and on-chain analytics; no API key. This page covers its hosted endpoint (https://mcp.bitview.space/).
Is the Bitview MCP server safe to use?
Bitview scores 74 out of 100 on VerifyMCP. 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 Bitview MCP server expose?
Bitview exposes 75 tools: get_address, get_address_confirmed_txs, get_address_confirmed_txs_after, get_address_hash_prefix_matches, get_address_mempool_txs, and 70 more. Their descriptions and schemas cost roughly 6,899 tokens of context every time the server is loaded.
Does the Bitview MCP server require authentication?
Its publisher declares no required credentials for Bitview. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Bitview MCP server still maintained?
Bitview 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.