Bitview
REMOTE · MCP.BITVIEW.SPACE · SCANNED SEP 20
Read-only Bitcoin blockchain, mempool, mining, market, and on-chain analytics; no API key.
Available components
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 6640 tokens (~84/item across 79 items; 79 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 49% of tool parameters carry a description.Partial
- Structured output schemas are declared (90% 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 79 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 80 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
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/'
{
"mcpServers": {
"bitcoinresearchkit-bitview": {
"url": "https://mcp.bitview.space/"
}
}
} {
"servers": {
"bitcoinresearchkit-bitview": {
"type": "http",
"url": "https://mcp.bitview.space/"
}
}
} [mcp_servers.bitcoinresearchkit-bitview] url = "https://mcp.bitview.space/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bitcoinresearchkit-bitview": {
"type": "remote",
"url": "https://mcp.bitview.space/",
"enabled": true
}
}
} openclaw mcp add bitcoinresearchkit-bitview --url 'https://mcp.bitview.space/' --transport streamable-http
mcp_servers:
bitcoinresearchkit-bitview:
url: "https://mcp.bitview.space/" {
"McpServers": {
"bitcoinresearchkit-bitview": {
"Transport": "http",
"Url": "https://mcp.bitview.space/"
}
}
} assistant mcp add bitcoinresearchkit-bitview -t streamable-http -u 'https://mcp.bitview.space/'
{
"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.
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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 9 Sept 26 +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.
- 7 Sept 26 +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.
- 5 Sept 26 +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.
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 20 Sept 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 | 16 Aug 2026 | 14 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | fa84d57fc7e16dc50ecad136260a12a8 |
| 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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| 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 ~86
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_address_confirmed_txs Address confirmed transactions ~95
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_address_confirmed_txs_after Address confirmed transactions (paginated) ~112
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | yes | – |
| after_txid | – | yes | Last txid from the previous page (return transactions strictly older than this) |
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/{addr_type}/{prefix}`.
| Name | Type | Req | Description |
|---|---|---|---|
| addr_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 ~80
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_address_txs Address transactions ~132
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_address_utxos Address UTXOs ~84
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_block Block information ~70
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_block_by_height Block hash by height ~65
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| height | – | yes | – |
No output schema declared.
No examples provided.
get_block_by_timestamp Block by timestamp ~66
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| timestamp | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_block_fee_rates Block fee rates ~134
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| time_period | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_block_fees Block fees ~108
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| time_period | – | 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 | – |
No output schema declared.
No examples provided.
get_block_rewards Block rewards ~115
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| time_period | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_block_sizes_weights Block sizes and weights ~111
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| time_period | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_block_status Block status ~79
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_block_tip_hash Block tip hash ~54
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`.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_block_tip_height Block tip height ~54
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`.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_block_txid Transaction ID at index ~90
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 | Bitcoin block hash |
| index | – | yes | Transaction index within the block (0-based) |
No output schema declared.
No examples provided.
get_block_txs_from_index Block transactions (paginated) ~100
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | – | yes | Bitcoin block hash |
| 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 ~53
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`.
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 ~92
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}`.
| 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 ~71
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| height | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_cpfp CPFP info ~82
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}`.
| 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) ~67
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`.
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 ~110
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| time_period | – | yes | – |
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 ~109
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| time_period | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_historical_price Historical price ~70
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| timestamp | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_indexes List available indexes ~37
Returns all available indexes with their accepted query aliases. Use any alias when querying series. REST operation: `GET /api/series/indexes`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_mempool Mempool statistics ~63
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`.
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_hash Mempool content hash ~74
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`.
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_oracle_histogram_outputs Output value histogram at height or day ~119
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| point | string | yes | Confirmed block height as decimal digits (`840000`) or calendar date in `YYYY-MM-DD` format. |
Structured output declared, but exposes no named fields.
No examples provided.
get_oracle_histogram_outputs_live Live output value histogram ~80
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`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_oracle_histogram_payments Payment output histogram at height or day ~117
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| point | string | yes | Confirmed block height as decimal digits (`840000`) or calendar date in `YYYY-MM-DD` format. |
Structured output declared, but exposes no named fields.
No examples provided.
get_oracle_histogram_payments_live Live payment output histogram ~73
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`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_pool Mining pool details ~71
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}`.
| 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 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`.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_pool_blocks_from Mining pool blocks from height ~84
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}`.
| 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_stats Mining pool statistics ~104
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| time_period | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_pools List all mining pools ~57
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`.
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) ~63
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`.
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 ~106
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| time_period | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.