Bitview
REMOTE · MCP.BITVIEW.SPACE · SCANNED SEP 21
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 Management73
- Stability observed for 22 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 21 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_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 ~75
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`.
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 ~188
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | yes | Aggregation index |
| limit | – | – | Maximum number of values to return (ignored if `end` is set). Aliases: `count`, `c`, `l` |
| series | – | yes | Series name |
| start | – | – | Inclusive start: integer index, date (YYYY-MM-DD), or timestamp (ISO 8601). Negative integers count from end. Aliases: `from`, `f`, `s` |
Structured output declared, but exposes no named fields.
No examples provided.
get_series_bulk Bulk series data ~196
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | yes | Index to query |
| limit | – | – | Maximum number of values to return (ignored if `end` is set). Aliases: `count`, `c`, `l` |
| series | – | yes | Requested series |
| start | – | – | Inclusive start: integer index, date (YYYY-MM-DD), or timestamp (ISO 8601). Negative integers count from end. Aliases: `from`, `f`, `s` |
Structured output declared, but exposes no named fields.
No examples provided.
get_series_count Series count ~30
Returns the number of series available per index type. REST operation: `GET /api/series/count`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_series_info Get series info ~43
Returns the optional description, supported indexes, and value type for the specified series. REST operation: `GET /api/series/{series}`.
| Name | Type | Req | Description |
|---|---|---|---|
| series | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_series_latest Get latest series value ~60
Returns the single most recent value for a series, unwrapped (not inside a SeriesData object). REST operation: `GET /api/series/{series}/{index}/latest`.
| Name | Type | Req | Description |
|---|---|---|---|
| index | – | yes | Aggregation index |
| series | – | yes | Series name |
Structured output declared, but exposes no named fields.
No examples provided.
get_series_len Get series data length ~55
Returns the total number of data points for a series at the given index. REST operation: `GET /api/series/{series}/{index}/len`.
| Name | Type | Req | Description |
|---|---|---|---|
| index | – | yes | Aggregation index |
| series | – | yes | Series name |
Structured output declared, but exposes no named fields.
No examples provided.
get_series_version Get series version ~56
Returns the current version of a series. Changes when the series data is updated. REST operation: `GET /api/series/{series}/{index}/version`.
| Name | Type | Req | Description |
|---|---|---|---|
| index | – | yes | Aggregation index |
| series | – | yes | Series name |
Structured output declared, but exposes no named fields.
No examples provided.
get_sync_status Sync status ~44
Returns the sync status of the indexer, including indexed height, tip height, blocks behind, and last indexed timestamp. REST operation: `GET /api/server/sync`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_transaction_times Transaction first-seen times ~85
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| txId[] | array | yes | Transaction IDs to look up (max 250 per request). |
Structured output declared, but exposes no named fields.
No examples provided.
get_tx Transaction information ~73
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| txid | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_tx_by_index Txid by index ~52
Retrieve the transaction ID (txid) at a given global transaction index. Returns the txid as plain text. REST operation: `GET /api/tx-index/{index}`.
| Name | Type | Req | Description |
|---|---|---|---|
| index | – | yes | – |
No output schema declared.
No examples provided.
get_tx_hex Transaction hex ~72
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| txid | – | yes | – |
No output schema declared.
No examples provided.
get_tx_merkle_proof Transaction merkle proof ~69
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| txid | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_tx_merkleblock_proof Transaction merkleblock proof ~80
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| txid | – | yes | – |
No output schema declared.
No examples provided.
get_tx_outspend Output spend status ~98
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| txid | – | yes | Transaction ID |
| vout | – | yes | Output index |
Structured output declared, but exposes no named fields.
No examples provided.
get_tx_outspends All output spend statuses ~80
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| txid | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_tx_rbf RBF replacement history ~101
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| txid | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_tx_status Transaction status ~80
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| txid | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_urpd Latest URPD ~161
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| agg | – | – | Aggregation strategy. Default: raw (no aggregation). Accepts `bucket` as alias. |
| cohort | – | yes | – |
| weight | – | – | Supply weighting. Default: raw (unweighted). |
Structured output declared, but exposes no named fields.
No examples provided.
get_urpd_at URPD at date ~186
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| agg | – | – | Aggregation strategy. Default: raw (no aggregation). Accepts `bucket` as alias. |
| cohort | – | yes | – |
| date | string | yes | Calendar date of the URPD snapshot in `YYYY-MM-DD` format. |
| weight | – | – | Supply weighting. Default: raw (unweighted). |
Structured output declared, but exposes no named fields.
No examples provided.
list_series Series list ~70
Paginated flat list of all available series names. Use `page` query param for pagination. REST operation: `GET /api/series/list`.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Pagination index |
| per_page | integer | – | Results per page (default: 1000, max: 1000) |
Structured output declared, but exposes no named fields.
No examples provided.
list_urpd_cohorts Available URPD cohorts ~57
Cohorts for which URPD data is available. Returns names like `all`, `sth`, `lth`, `utxos_under_1h_old`. REST operation: `GET /api/urpd`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_urpd_dates Available URPD dates ~72
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| cohort | – | yes | – |
| weight | – | – | Supply weighting. Default: raw (unweighted). |
Structured output declared, but exposes no named fields.
No examples provided.
search_series Search series ~63
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | Maximum number of results |
| q | – | yes | Search query string |
Structured output declared, but exposes no named fields.
No examples provided.
validate_address Validate address ~92
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}`.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Bitcoin address to validate (can be any string) |
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 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.