MCP servers observed by Lowdown
io.github.bitcoinresearchkit/bitview MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 71 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; tool definitions last changed on 2026-11-17 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.bitcoinresearchkit/bitview
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.bitcoinresearchkit/bitview?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 2 compared days.
- 2026-11-17: input or output schemas changed, descriptions changed, tool names changed; tool count 75 → 71
- 2026-11-14: input or output schemas changed, descriptions changed
What tools does it list?
71 tools on 2026-11-17:
get_addressget_address_confirmed_txsget_address_confirmed_txs_afterget_address_hash_prefix_matchesget_address_mempool_txsget_address_txsget_address_utxosget_blockget_block_by_timestampget_block_fee_rates_preciseget_block_feesget_block_hash_by_heightget_block_headerget_block_rewardsget_block_sizes_weightsget_block_statusget_block_tip_hashget_block_tip_heightget_block_txidget_block_txs_from_indexget_block_v1get_blocksget_blocks_from_heightget_blocks_v1get_blocks_v1_from_heightget_cpfpget_difficulty_adjustmentget_difficulty_adjustments_by_periodget_fullrbf_replacementsget_hashrate_by_periodget_historical_priceget_mempoolget_mempool_blocksget_mempool_recentget_poolget_pool_blocksget_pool_blocks_from_heightget_pool_hashrateget_pool_rankingget_poolsget_pools_hashrate_by_periodget_precise_feesget_pricesget_replacementsget_reward_statsget_seriesget_series_bulkget_series_countget_series_infoget_series_latestget_series_lenget_series_versionget_sync_statusget_transaction_timesget_txget_tx_hexget_tx_merkle_proofget_tx_merkleblock_proofget_tx_outspendget_tx_outspendsget_tx_rbfget_tx_statusget_txid_by_indexget_urpdget_urpd_latestget_utxo_set_difflist_indexeslist_serieslist_urpd_cohortssearch_seriesvalidate_address
MCP Registry declaration
- Registry name:
io.github.bitcoinresearchkit/bitview - Declared version: 0.13.0
- Status: active
- Declared hosts:
mcp.bitview.space
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.bitcoinresearchkit/bitview", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.bitcoinresearchkit/bitview?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).