# Bitview (remote · mcp.bitview.space)

Read-only Bitcoin blockchain, mempool, mining, market, and on-chain analytics; no API key.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcp.bitview.space`: 81/100 (this document), [markdown](https://verifymcp.io/servers/bitcoinresearchkit-bitview/mcp.md), [page](https://verifymcp.io/servers/bitcoinresearchkit-bitview/mcp)

## Channel facts

- Endpoint: `https://mcp.bitview.space/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.12.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 6640 tokens (~84/item across 79 items; 79 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 49% of tool parameters carry a description.
  - Structured output schemas are declared (90% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 79 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 80 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http bitcoinresearchkit-bitview 'https://mcp.bitview.space/'
```

### Cursor

```json
{
  "mcpServers": {
    "bitcoinresearchkit-bitview": {
      "url": "https://mcp.bitview.space/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "bitcoinresearchkit-bitview": {
      "type": "http",
      "url": "https://mcp.bitview.space/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.bitcoinresearchkit-bitview]
url = "https://mcp.bitview.space/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bitcoinresearchkit-bitview": {
      "type": "remote",
      "url": "https://mcp.bitview.space/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add bitcoinresearchkit-bitview --url 'https://mcp.bitview.space/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  bitcoinresearchkit-bitview:
    url: "https://mcp.bitview.space/"
```

### Netclaw

```json
{
  "McpServers": {
    "bitcoinresearchkit-bitview": {
      "Transport": "http",
      "Url": "https://mcp.bitview.space/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add bitcoinresearchkit-bitview -t streamable-http -u 'https://mcp.bitview.space/'
```

### Other

```json
{
  "mcpServers": {
    "bitcoinresearchkit-bitview": {
      "type": "http",
      "url": "https://mcp.bitview.space/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (79)

### `get_address` (~86 tokens)

Address information

Retrieve address information including current balance and transaction counts. Supports all standard Bitcoin address types (P2PKH, P2SH, P2WPKH, P2WSH, P2TR).

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-address)*

REST operation: `GET /api/address/{address}`.

Input parameters:

- `address` (required)

### `get_address_confirmed_txs` (~95 tokens)

Address confirmed transactions

Get the first 25 confirmed transactions for an address. 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`.

Input parameters:

- `address` (required)

### `get_address_confirmed_txs_after` (~112 tokens)

Address confirmed transactions (paginated)

Get the next 25 confirmed transactions strictly older than `after_txid` (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}`.

Input parameters:

- `address` (required)
- `after_txid` (required): Last txid from the previous page (return transactions strictly older than this)

### `get_address_hash_prefix_matches` (~123 tokens)

Address hash-prefix matches

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/{addr_type}/{prefix}`.

Input parameters:

- `addr_type` (required)
- `prefix` (string, required): First 1–16 hexadecimal nibbles of the RapidHash v3 hash over the raw address payload bytes.

### `get_address_mempool_txs` (~80 tokens)

Address mempool transactions

Get unconfirmed transactions for an address from the mempool, newest first (up to 50).

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-address-transactions-mempool)*

REST operation: `GET /api/address/{address}/txs/mempool`.

Input parameters:

- `address` (required)

### `get_address_txs` (~132 tokens)

Address transactions

Get transaction history for an address, newest first. Returns up to 50 mempool transactions plus a confirmed page sized to fill the response to 50 total (chain floor of 25, so 25-50 confirmed depending on mempool weight). To paginate further confirmed history, 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)*

REST operation: `GET /api/address/{address}/txs`.

Input parameters:

- `address` (required)

### `get_address_utxos` (~84 tokens)

Address UTXOs

Get unspent transaction outputs (UTXOs) for an address. Returns txid, vout, value, and confirmation status for each UTXO.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-address-utxo)*

REST operation: `GET /api/address/{address}/utxo`.

Input parameters:

- `address` (required)

### `get_block` (~70 tokens)

Block information

Retrieve block information by block hash. Returns block metadata including height, timestamp, difficulty, size, weight, and transaction count.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-block)*

REST operation: `GET /api/block/{hash}`.

Input parameters:

- `hash` (required)

### `get_block_by_height` (~65 tokens)

Block hash by height

Retrieve the block hash at a given height. Returns the hash as plain text.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-height)*

REST operation: `GET /api/block-height/{height}`.

Input parameters:

- `height` (required)

### `get_block_by_timestamp` (~66 tokens)

Block by timestamp

Find the block closest to a given UNIX timestamp.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-timestamp)*

REST operation: `GET /api/v1/mining/blocks/timestamp/{timestamp}`.

Input parameters:

- `timestamp` (required)

### `get_block_fee_rates` (~134 tokens)

Block fee rates

Get block fee rate percentiles (min, 10th, 25th, median, 75th, 90th, max) for a time period. Valid periods: `24h`, `3d`, `1w`, `1m`, `3m`, `6m`, `1y`, `2y`, `3y`.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-feerates)*

REST operation: `GET /api/v1/mining/blocks/fee-rates/{time_period}`.

Input parameters:

- `time_period` (required)

### `get_block_fees` (~108 tokens)

Block fees

Get average total fees per block for a time period. Valid periods: `24h`, `3d`, `1w`, `1m`, `3m`, `6m`, `1y`, `2y`, `3y`.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-fees)*

REST operation: `GET /api/v1/mining/blocks/fees/{time_period}`.

Input parameters:

- `time_period` (required)

### `get_block_header` (~59 tokens)

Block header

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`.

Input parameters:

- `hash` (required)

### `get_block_rewards` (~115 tokens)

Block rewards

Get average coinbase reward (subsidy + fees) per block for a time period. Valid periods: `24h`, `3d`, `1w`, `1m`, `3m`, `6m`, `1y`, `2y`, `3y`.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-rewards)*

REST operation: `GET /api/v1/mining/blocks/rewards/{time_period}`.

Input parameters:

- `time_period` (required)

### `get_block_sizes_weights` (~111 tokens)

Block sizes and weights

Get average block sizes and weights for a time period. Valid periods: `24h`, `3d`, `1w`, `1m`, `3m`, `6m`, `1y`, `2y`, `3y`.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-sizes-weights)*

REST operation: `GET /api/v1/mining/blocks/sizes-weights/{time_period}`.

Input parameters:

- `time_period` (required)

### `get_block_status` (~79 tokens)

Block status

Retrieve the status of a block. Returns whether the block is in the best chain and, if so, its height and the hash of the next block.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-status)*

REST operation: `GET /api/block/{hash}/status`.

Input parameters:

- `hash` (required)

### `get_block_tip_hash` (~54 tokens)

Block tip hash

Returns the hash of the last block.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-tip-hash)*

REST operation: `GET /api/blocks/tip/hash`.

### `get_block_tip_height` (~54 tokens)

Block tip height

Returns the height of the last block.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-tip-height)*

REST operation: `GET /api/blocks/tip/height`.

### `get_block_txid` (~90 tokens)

Transaction ID at index

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}`.

Input parameters:

- `hash` (required): Bitcoin block hash
- `index` (required): Transaction index within the block (0-based)

### `get_block_txs_from_index` (~100 tokens)

Block transactions (paginated)

Retrieve transactions in a block by block hash, starting from the specified index. Returns up to 25 transactions at a time.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-block-transactions)*

REST operation: `GET /api/block/{hash}/txs/{start_index}`.

Input parameters:

- `hash` (required): Bitcoin block hash
- `start_index` (required): Starting transaction index within the block (0-based)

### `get_block_v1` (~59 tokens)

Block (v1)

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}`.

Input parameters:

- `hash` (required)

### `get_blocks` (~53 tokens)

Recent blocks

Retrieve the last 10 blocks. Returns block metadata for each block.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-blocks)*

REST operation: `GET /api/blocks`.

### `get_blocks_from_height` (~92 tokens)

Blocks from height

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.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-blocks)*

REST operation: `GET /api/blocks/{height}`.

Input parameters:

- `height` (required)

### `get_blocks_v1` (~61 tokens)

Recent blocks with extras

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`.

### `get_blocks_v1_from_height` (~71 tokens)

Blocks from height with extras

Retrieve up to 15 blocks with extended data going backwards from the given height.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-blocks-v1)*

REST operation: `GET /api/v1/blocks/{height}`.

Input parameters:

- `height` (required)

### `get_cpfp` (~82 tokens)

CPFP info

Returns ancestors and descendants for a CPFP (Child Pays For Parent) transaction, including the effective fee rate of the package.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-children-pay-for-parent)*

REST operation: `GET /api/v1/cpfp/{txid}`.

Input parameters:

- `txid` (required)

### `get_difficulty_adjustment` (~56 tokens)

Difficulty adjustment

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`.

### `get_difficulty_adjustments` (~67 tokens)

Difficulty adjustments (all time)

Get historical difficulty adjustments including timestamp, block height, difficulty value, and percentage change.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-difficulty-adjustments)*

REST operation: `GET /api/v1/mining/difficulty-adjustments`.

### `get_difficulty_adjustments_by_period` (~110 tokens)

Difficulty adjustments

Get historical difficulty adjustments for a time period. Valid periods: `24h`, `3d`, `1w`, `1m`, `3m`, `6m`, `1y`, `2y`, `3y`.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-difficulty-adjustments)*

REST operation: `GET /api/v1/mining/difficulty-adjustments/{time_period}`.

Input parameters:

- `time_period` (required)

### `get_fullrbf_replacements` (~82 tokens)

Recent full-RBF replacements

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`.

### `get_hashrate` (~57 tokens)

Network hashrate (all time)

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`.

### `get_hashrate_by_period` (~109 tokens)

Network hashrate

Get network hashrate and difficulty data for a time period. Valid periods: `24h`, `3d`, `1w`, `1m`, `3m`, `6m`, `1y`, `2y`, `3y`.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-hashrate)*

REST operation: `GET /api/v1/mining/hashrate/{time_period}`.

Input parameters:

- `time_period` (required)

### `get_historical_price` (~70 tokens)

Historical price

Get historical BTC/USD price. Optionally specify a UNIX timestamp to get the price at that time.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-historical-price)*

REST operation: `GET /api/v1/historical-price`.

Input parameters:

- `timestamp`

### `get_indexes` (~37 tokens)

List available indexes

Returns all available indexes with their accepted query aliases. Use any alias when querying series.

REST operation: `GET /api/series/indexes`.

### `get_mempool` (~63 tokens)

Mempool statistics

Get current mempool statistics including transaction count, total vsize, total fees, and fee histogram.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-mempool)*

REST operation: `GET /api/mempool`.

### `get_mempool_blocks` (~83 tokens)

Projected mempool blocks

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`.

### `get_mempool_hash` (~74 tokens)

Mempool content hash

Returns an opaque hash that changes whenever the projected next block changes. Same value as the mempool ETag. Useful as a freshness/liveness signal: if it stays constant for tens of seconds on a live network, the mempool sync loop has stalled.

REST operation: `GET /api/mempool/hash`.

### `get_mempool_recent` (~60 tokens)

Recent mempool transactions

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`.

### `get_oracle_histogram_outputs` (~119 tokens)

Output value histogram at height or day

Unfiltered output value histogram for a confirmed point. A block height (`840000`) gives every output in that block, coinbase included, binned by value on the oracle log scale; a calendar date (`YYYY-MM-DD`) sums every block that day. A flat array of log-scale bins.

REST operation: `GET /api/oracle/histogram/outputs/{point}`.

Input parameters:

- `point` (string, required): Confirmed block height as decimal digits (`840000`) or calendar date in `YYYY-MM-DD` format.

### `get_oracle_histogram_outputs_live` (~80 tokens)

Live output value histogram

Live unfiltered output value histogram for the forming mempool block. Every live output is binned by value on the oracle log scale; no oracle payment filters are applied. A flat array of log-scale bins, all zero when no mempool is configured.

REST operation: `GET /api/oracle/histogram/outputs/live`.

### `get_oracle_histogram_payments` (~117 tokens)

Payment output histogram at height or day

Smoothed histogram of oracle-eligible payment outputs for a confirmed point. A block height (`840000`) gives that block's oracle payment histogram; a calendar date (`YYYY-MM-DD`) gives the average of that day's per-block payment histograms. A flat array of log-scale bins.

REST operation: `GET /api/oracle/histogram/payments/{point}`.

Input parameters:

- `point` (string, required): Confirmed block height as decimal digits (`840000`) or calendar date in `YYYY-MM-DD` format.

### `get_oracle_histogram_payments_live` (~73 tokens)

Live payment output histogram

Live smoothed histogram of oracle-eligible payment outputs, binned by output value on the oracle log scale. It combines the committed oracle window with the forming mempool block. A flat array of log-scale bins.

REST operation: `GET /api/oracle/histogram/payments/live`.

### `get_pool` (~71 tokens)

Mining pool details

Get detailed information about a specific mining pool including block counts and shares for different time periods.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-mining-pool)*

REST operation: `GET /api/v1/mining/pool/{slug}`.

Input parameters:

- `slug` (required)

### `get_pool_blocks` (~70 tokens)

Mining pool blocks

Get the 10 most 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`.

Input parameters:

- `slug` (required)

### `get_pool_blocks_from` (~84 tokens)

Mining pool blocks from height

Get 10 blocks mined by a specific pool before (and including) the given height.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-mining-pool-blocks)*

REST operation: `GET /api/v1/mining/pool/{slug}/blocks/{height}`.

Input parameters:

- `height` (required)
- `slug` (required)

### `get_pool_hashrate` (~71 tokens)

Mining pool hashrate

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`.

Input parameters:

- `slug` (required)

### `get_pool_stats` (~104 tokens)

Mining pool statistics

Get mining pool statistics for a time period. Valid periods: `24h`, `3d`, `1w`, `1m`, `3m`, `6m`, `1y`, `2y`, `3y`.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-mining-pools)*

REST operation: `GET /api/v1/mining/pools/{time_period}`.

Input parameters:

- `time_period` (required)

### `get_pools` (~57 tokens)

List all mining pools

Get list of all known mining pools with their identifiers.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-mining-pools)*

REST operation: `GET /api/v1/mining/pools`.

### `get_pools_hashrate` (~63 tokens)

All pools hashrate (all time)

Get hashrate data for all mining pools.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-mining-pool-hashrates)*

REST operation: `GET /api/v1/mining/hashrate/pools`.

### `get_pools_hashrate_by_period` (~106 tokens)

All pools hashrate

Get hashrate data for all mining pools for a time period. Valid periods: `1m`, `3m`, `6m`, `1y`, `2y`, `3y`.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-mining-pool-hashrates)*

REST operation: `GET /api/v1/mining/hashrate/pools/{time_period}`.

Input parameters:

- `time_period` (required)

### `get_precise_fees` (~75 tokens)

Recommended fee rates (precise)

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`.

### `get_prices` (~52 tokens)

Current BTC price

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`.

### `get_replacements` (~75 tokens)

Recent RBF replacements

Returns up to 25 most-recent RBF replacement trees across the whole mempool. Each entry has the same shape as `tx_rbf().replacements`.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-replacements)*

REST operation: `GET /api/v1/replacements`.

### `get_reward_stats` (~85 tokens)

Mining reward statistics

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}`.

Input parameters:

- `block_count` (integer, required): Number of recent blocks to include

### `get_series` (~188 tokens)

Get series data

Fetch data for a specific series at the given index. Use query parameters to filter by date range and format (json/csv).

REST operation: `GET /api/series/{series}/{index}`.

Input parameters:

- `end`: Exclusive end: integer index, date (YYYY-MM-DD), or timestamp (ISO 8601). Negative integers count from end. Aliases: `to`, `t`, `e`
- `format`: Format of the output
- `index` (required): Aggregation index
- `limit`: Maximum number of values to return (ignored if `end` is set). Aliases: `count`, `c`, `l`
- `series` (required): Series name
- `start`: Inclusive start: integer index, date (YYYY-MM-DD), or timestamp (ISO 8601). Negative integers count from end. Aliases: `from`, `f`, `s`

### `get_series_bulk` (~196 tokens)

Bulk series data

Fetch multiple series in a single request. Supports filtering by index and date range. Returns an array of SeriesData objects. For a single series, use `get_series` instead.

REST operation: `GET /api/series/bulk`.

Input parameters:

- `end`: Exclusive end: integer index, date (YYYY-MM-DD), or timestamp (ISO 8601). Negative integers count from end. Aliases: `to`, `t`, `e`
- `format`: Format of the output
- `index` (required): Index to query
- `limit`: Maximum number of values to return (ignored if `end` is set). Aliases: `count`, `c`, `l`
- `series` (required): Requested series
- `start`: Inclusive start: integer index, date (YYYY-MM-DD), or timestamp (ISO 8601). Negative integers count from end. Aliases: `from`, `f`, `s`

### `get_series_count` (~30 tokens)

Series count

Returns the number of series available per index type.

REST operation: `GET /api/series/count`.

### `get_series_info` (~43 tokens)

Get series info

Returns the optional description, supported indexes, and value type for the specified series.

REST operation: `GET /api/series/{series}`.

Input parameters:

- `series` (required)

### `get_series_latest` (~60 tokens)

Get latest series value

Returns the single most recent value for a series, unwrapped (not inside a SeriesData object).

REST operation: `GET /api/series/{series}/{index}/latest`.

Input parameters:

- `index` (required): Aggregation index
- `series` (required): Series name

### `get_series_len` (~55 tokens)

Get series data length

Returns the total number of data points for a series at the given index.

REST operation: `GET /api/series/{series}/{index}/len`.

Input parameters:

- `index` (required): Aggregation index
- `series` (required): Series name

### `get_series_version` (~56 tokens)

Get series version

Returns the current version of a series. Changes when the series data is updated.

REST operation: `GET /api/series/{series}/{index}/version`.

Input parameters:

- `index` (required): Aggregation index
- `series` (required): Series name

### `get_sync_status` (~44 tokens)

Sync status

Returns the sync status of the indexer, including indexed height, tip height, blocks behind, and last indexed timestamp.

REST operation: `GET /api/server/sync`.

### `get_transaction_times` (~85 tokens)

Transaction first-seen times

Returns timestamps when transactions were first seen in the mempool. Returns 0 for mined or unknown transactions.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-transaction-times)*

REST operation: `GET /api/v1/transaction-times`.

Input parameters:

- `txId[]` (array, required): Transaction IDs to look up (max 250 per request).

### `get_tx` (~73 tokens)

Transaction information

Retrieve complete transaction data by transaction ID (txid). Returns inputs, outputs, fee, size, and confirmation status.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-transaction)*

REST operation: `GET /api/tx/{txid}`.

Input parameters:

- `txid` (required)

### `get_tx_by_index` (~52 tokens)

Txid by index

Retrieve the transaction ID (txid) at a given global transaction index. Returns the txid as plain text.

REST operation: `GET /api/tx-index/{index}`.

Input parameters:

- `index` (required)

### `get_tx_hex` (~72 tokens)

Transaction hex

Retrieve the raw transaction as a hex-encoded string. Returns the serialized transaction in hexadecimal format.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-transaction-hex)*

REST operation: `GET /api/tx/{txid}/hex`.

Input parameters:

- `txid` (required)

### `get_tx_merkle_proof` (~69 tokens)

Transaction merkle proof

Get the merkle inclusion proof for a transaction.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-transaction-merkle-proof)*

REST operation: `GET /api/tx/{txid}/merkle-proof`.

Input parameters:

- `txid` (required)

### `get_tx_merkleblock_proof` (~80 tokens)

Transaction merkleblock proof

Get the merkleblock proof for a transaction (BIP37 format, hex encoded).

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-transaction-merkleblock-proof)*

REST operation: `GET /api/tx/{txid}/merkleblock-proof`.

Input parameters:

- `txid` (required)

### `get_tx_outspend` (~98 tokens)

Output spend status

Get the spending status of a transaction output. Returns whether the output has been spent and, if so, the spending transaction details.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-transaction-outspend)*

REST operation: `GET /api/tx/{txid}/outspend/{vout}`.

Input parameters:

- `txid` (required): Transaction ID
- `vout` (required): Output index

### `get_tx_outspends` (~80 tokens)

All output spend statuses

Get the spending status of all outputs in a transaction. Returns an array with the spend status for each output.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-transaction-outspends)*

REST operation: `GET /api/tx/{txid}/outspends`.

Input parameters:

- `txid` (required)

### `get_tx_rbf` (~101 tokens)

RBF replacement history

Returns the RBF replacement tree for a transaction, if any. Both `replacements` and `replaces` are null when the tx has no known RBF history within the mempool monitor's retention window.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-transaction-rbf-history)*

REST operation: `GET /api/v1/tx/{txid}/rbf`.

Input parameters:

- `txid` (required)

### `get_tx_status` (~80 tokens)

Transaction status

Retrieve the confirmation status of a transaction. Returns whether the transaction is confirmed and, if so, the block height, hash, and timestamp.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-transaction-status)*

REST operation: `GET /api/tx/{txid}/status`.

Input parameters:

- `txid` (required)

### `get_urpd` (~161 tokens)

Latest URPD

URPD for the most recent available date in the cohort. The response's `date` field echoes which date was served. Returns `{ cohort, date, weight, aggregation, close, total_supply, buckets }`. `close` and each bucket's `price_floor`, `realized_cap`, and `unrealized_pnl` are USD; `total_supply` and bucket `supply` are BTC. `unrealized_pnl` can be negative.

REST operation: `GET /api/urpd/{cohort}`.

Input parameters:

- `agg`: Aggregation strategy. Default: raw (no aggregation). Accepts `bucket` as alias.
- `cohort` (required)
- `weight`: Supply weighting. Default: raw (unweighted).

### `get_urpd_at` (~186 tokens)

URPD at date

URPD for a (cohort, date) pair. Returns `{ cohort, date, weight, aggregation, close, total_supply, buckets }` where each bucket is `{ price_floor, supply, realized_cap, unrealized_pnl }`. `close`, `price_floor`, `realized_cap`, and `unrealized_pnl` are USD; `total_supply` and `supply` are BTC. `unrealized_pnl` can be negative.

REST operation: `GET /api/urpd/{cohort}/{date}`.

Input parameters:

- `agg`: Aggregation strategy. Default: raw (no aggregation). Accepts `bucket` as alias.
- `cohort` (required)
- `date` (string, required): Calendar date of the URPD snapshot in `YYYY-MM-DD` format.
- `weight`: Supply weighting. Default: raw (unweighted).

### `list_series` (~70 tokens)

Series list

Paginated flat list of all available series names. Use `page` query param for pagination.

REST operation: `GET /api/series/list`.

Input parameters:

- `page` (integer): Pagination index
- `per_page` (integer): Results per page (default: 1000, max: 1000)

### `list_urpd_cohorts` (~57 tokens)

Available URPD cohorts

Cohorts for which URPD data is available. Returns names like `all`, `sth`, `lth`, `utxos_under_1h_old`.

REST operation: `GET /api/urpd`.

### `list_urpd_dates` (~72 tokens)

Available URPD dates

Dates for which a URPD snapshot is available for the cohort and selected `weight`. One entry per UTC day, sorted ascending.

REST operation: `GET /api/urpd/{cohort}/dates`.

Input parameters:

- `cohort` (required)
- `weight`: Supply weighting. Default: raw (unweighted).

### `search_series` (~63 tokens)

Search series

Search series by name or descriptive terms. Matches metric names, descriptions, formulas, cohort aliases, partial words, and common typos.

REST operation: `GET /api/series/search`.

Input parameters:

- `limit`: Maximum number of results
- `q` (required): Search query string

### `validate_address` (~92 tokens)

Validate address

Validate a Bitcoin address and get information about its type and scriptPubKey. Returns `isvalid: false` with an error message for invalid addresses.

\*[Mempool.space docs](https://mempool.space/docs/api/rest#get-address-validate)*

REST operation: `GET /api/v1/validate-address/{address}`.

Input parameters:

- `address` (string, required): Bitcoin address to validate (can be any string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/bitcoinresearchkit-bitview/mcp#diagnostics

## Score history

- 2026-09-21: 81
- 2026-09-20: 81
- 2026-09-19: 80
- 2026-09-18: 80
- 2026-09-17: 79
- 2026-09-16: 79
- 2026-09-15: 78
- 2026-09-14: 78
- 2026-09-13: 77
- 2026-09-12: 77
- 2026-09-11: 76
- 2026-09-10: 76
- 2026-09-09: 76
- 2026-09-08: 75
- 2026-09-07: 75
- 2026-09-06: 74
- 2026-09-05: 74
- 2026-09-04: 73
- 2026-09-03: 73
- 2026-09-02: 72
- 2026-09-01: 72
- 2026-08-31: 71
- 2026-08-30: 71

## Common questions

### 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 81 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 79 tools: get_address, get_address_confirmed_txs, get_address_confirmed_txs_after, get_address_hash_prefix_matches, get_address_mempool_txs, and 74 more. Their descriptions and schemas cost roughly 6,568 tokens of context every time the server is loaded.

### Does the Bitview MCP server require authentication?

No. We connected to Bitview without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Bitview MCP server still maintained?

Bitview is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.bitview.space/
- Repository: https://github.com/bitcoinresearchkit/mono
- Website: https://mcp.bitview.space/
- Changelog RSS feed: https://verifymcp.io/servers/bitcoinresearchkit-bitview/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/bitcoinresearchkit-bitview/mcp.json
- HTML version of this page: https://verifymcp.io/servers/bitcoinresearchkit-bitview/mcp