Bitview

io.github.bitcoinresearchkitPublished by GitHub account bitcoinresearchkitv0.13.0Updated Oct 31, 2026

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

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

Read-only MCP adapter for the Bitview REST API, giving assistants Bitcoin blockchain, mempool, mining, market and on-chain analytics without an API key.

What you can do
  • Query Bitcoin blockchain and on-chain analytics data
  • Inspect mempool and mining information
  • Retrieve market data
  • Forward each tool call as a GET request to the configured Bitview REST origin
  • Expose the MCP-visible OpenAPI operations as generated tools
When to use it
Useful when an assistant needs read-only Bitcoin data — chain, mempool, mining, market or on-chain metrics — and you want a hosted endpoint that needs no API key or account.
Requirements
A remote Streamable HTTP endpoint at mcp.bitview.space, or a locally run binary started with the required --api, --url and --name options. No authentication, API key or environment variables are needed. Network access to the upstream Bitview REST origin is required.
Before you install
The server is read-only and forwards every tool call as a GET request to the configured upstream origin, so queries and their parameters go to that third party. When self-hosting, point --api only at a trusted origin, since all requests are sent there. No caching or session retention is done by the server itself.

Installation

In SourceWeft

  1. Open Bitview in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.bitcoinresearchkit%2Fbitview/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "bitview": {
      "type": "http",
      "url": "https://mcp.bitview.space/"
    }
  }
}

README

bitview_mcp

bitview_mcp is a stateless, read-only MCP adapter for the Bitview REST API. It exposes the MCP-visible OpenAPI operations as generated tools and forwards every tool call to the configured public REST origin as a GET request.

The official public endpoint is mcp.bitview.space; it requires no authentication.

The server also serves an instance landing page, /privacy, /terms, /support, and /logo.png. The icon is embedded in the binary and advertised in MCP discovery metadata.

Caching model

bitview_mcp does not cache API responses or retain MCP sessions. Point it at the public Cloudflare-fronted REST origin so its upstream GET requests use the existing Cloudflare cache:

text
MCP client -> bitview_mcp -> Cloudflare-cached REST API -> Bitview server

Cloudflare does not need to cache the MCP endpoint. The MCP catalog TTL is a client-side cache hint for the static discovery and tool-list metadata.

Run

From the workspace:

sh
cargo run -p bitview_mcp -- \  --api https://bitview.space \  --url https://mcp.bitview.space/ \  --name Bitview

For an installed binary, replace cargo run -p bitview_mcp -- with bitview_mcp.

All three options are required:

  • --api is the upstream Bitview REST origin.
  • --url is this server's public MCP URL.
  • --name is the human-readable instance name shown on the landing page and in MCP discovery metadata.

For local development:

sh
bitview_mcp \  --api http://127.0.0.1:3110 \  --url http://127.0.0.1:3111/ \  --name "Local Bitview"

The Streamable HTTP endpoint is http://127.0.0.1:3111/ by default. If that port is unavailable, the server tries each port through 3211. The server supports MCP protocol version 2026-07-28.

Both URLs must be absolute HTTP(S) origins without a path, query, or credentials. The public URL is normalized with a trailing slash.

Generated catalog

cargo bindgen generates the tool catalog (generated/manifest.json, embedded at compile time) and the MCP Registry server.json; see bitview_bindgen.

Source: crates/bitview_mcp/README.md at commit 39e0aaf

Tools

0
SourceWeft has not read this server's tools yet.

Version history

2
  1. v0.13.0LatestOct 31, 2026
  2. v0.12.2Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts