Provides read-only access to Bitcoin blockchain data, mempool status, mining information, and on-chain analytics via a REST API adapter.
Also known as bitcoinresearchkit/mono
- Stars
- 178
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.13.0
- Last commit
- Nov 15, 2026
- License
- MIT
What is Bitview MCP?
Bitview provides read-only access to Bitcoin blockchain data, mempool status, mining information, and on-chain analytics via a REST API adapter.
Summary generated from the project's README
About Bitview MCP server
Bitview acts as a stateless, read-only adapter that connects MCP clients to the Bitview REST API. It transforms OpenAPI operations into usable tools, allowing users to query Bitcoin blockchain data, mempool status, mining information, and various on-chain analytics. The server functions by forwarding tool calls as GET requests to a configured REST origin, such as the public endpoint at mcp.bitview.space which requires no authentication.
Developers can deploy this server locally or connect to a remote instance by specifying the API origin, the public MCP URL, and a human-readable name via command line arguments. It relies on the upstream Cloudflare cache for data efficiency rather than maintaining its own internal cache or session state. This architecture ensures that every request benefits from existing infrastructure while keeping the MCP server lightweight and focused on protocol translation.
Written from the project's README. Every use case is checked against a quote from it.
How to install Bitview MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Bitview MCP in Claude Code
$ claude mcp add --transport http bitview https://mcp.bitview.space/Install Bitview MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"bitview": {
"url": "https://mcp.bitview.space/"
}
}
}Install Bitview MCP in VS Code
.vscode/mcp.json
{
"servers": {
"bitview": {
"type": "http",
"url": "https://mcp.bitview.space/"
}
}
}Install Bitview MCP in VS Code CLI
$ code --add-mcp '{"name":"bitview","type":"http","url":"https://mcp.bitview.space/"}'Install Bitview MCP in Codex
$ codex mcp add bitview --url https://mcp.bitview.space/Install Bitview MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.bitview] url = "https://mcp.bitview.space/"
Install Bitview MCP in Gemini CLI
$ gemini mcp add -s user --transport http bitview https://mcp.bitview.space/Install Bitview MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"bitview": {
"url": "https://mcp.bitview.space/",
"type": "http"
}
}
}Automated checks
Ran Nov 12, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packageNot checked
- Remote endpoint uses HTTPSPass
- Destructive tools are labelledNot checked
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesNot checked
README
View on GitHubbitview_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:
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:
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:
--apiis the upstream Bitview REST origin.--urlis this server's public MCP URL.--nameis the human-readable instance name shown on the landing page and in MCP discovery metadata.
For local development:
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.
Bitview MCP questions
How do I add Bitview MCP to Claude Code?
Run claude mcp add --transport http bitview https://mcp.bitview.space/ in your terminal. Add --scope user to make it available in every project.
How do I add Bitview MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Does this server cache API responses?
The server is stateless and does not cache API responses or retain MCP sessions, relying instead on the upstream Cloudflare cache.