
BPE (Bitcoin Pricing Engine)
io.github.bxetechPublished by GitHub account bxetechv0.2.1Updated Oct 24, 2026
Consolidated Bitcoin market data for AI agents: BBO pricing, ML signals, funding skew, briefings.
Overview
Local MCP server that gives an AI assistant consolidated Bitcoin market data: aggregated pricing, ML signals, funding skew, sentiment and briefings.
- What you can do
- Retrieve the current BTC price aggregated across the BPE network of venues and get a natural-language market briefing covering price, funding skew, ML signal, sentiment and anomalies, in brief or detailed form. Query per-venue annualised funding rates with the max-spread pair, and read the current ML prediction with direction, probability and confidence at a chosen horizon. Fetch a sentiment snapshot with the Crypto Fear & Greed index, news sentiment and mempool stress.
- When to use it
- Useful when building or running an agent that needs Bitcoin market context without integrating many exchange APIs directly, since one key and one schema cover pricing, funding, signals and sentiment.
- Requirements
- Runs locally over stdio, typically via npx or a global npm install, so Node.js is needed. Requires a BPE API key in the BPE_API_KEY environment variable; a free tier exists for evaluation and the Agent tier unlocks the full briefing endpoint. Optional BPE_BASE_URL and BPE_TIMEOUT_MS settings. Network access to the BPE backend.
Installation
In SourceWeft
- Open BPE (Bitcoin Pricing Engine) in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
BPE MCP Server
Model Context Protocol server for the BPE market-data API. Lets Claude Desktop, Cursor, Goose, and other MCP-enabled agents query consolidated Bitcoin pricing, ML signals, funding-rate skew, and natural-language market briefings — without writing any HTTP boilerplate.
Status: v0.2 — five tools, local stdio transport, no LLM calls inside the briefing endpoint (template-rendered). API key required.
Listed in the official MCP Server Registry as io.github.bxetech/bpe-mcp. Install via npm install -g @bxetech/bpe-mcp or npx -y @bxetech/bpe-mcp.
Why use it
If you're building an agent that touches Bitcoin markets, you have two options today:
- Talk to 36 different exchange APIs directly. Each has a different schema, different auth, different rate limits, different reliability. Your agent burns tokens reasoning over inconsistent payloads.
- Use one consolidated source. BPE aggregates all 36 venues into a single normalised feed with derived signals (ML predictions, sentiment, funding skew, basis). One auth, one schema, one tool call.
This MCP server is option 2 dressed up as native tools your agent can discover and call.
Tools (v0.2)
Install
Or use npx with no install (recommended for Claude Desktop):
Restart Claude Desktop. The five tools appear under the MCP server picker.
Configuration
Local development
To dogfood in Claude Desktop while iterating, point at the local build:
Roadmap
- v0.2 —
get_sentiment_snapshot✅, friendly tier-aware errors ✅, timestamped briefings ✅ - v0.3 —
get_basis,subscribe_alert(webhook subscription), hosted HTTP transport for non-developer install (Cursor extension, ChatGPT Desktop) - v0.4 — Optional LLM-rendered briefing via Haiku (richer prose, with per-call cost)
See docs/research/AGENT_INTEGRATION_AND_MONETISATION_2026-04-27.md for the broader product / monetisation plan.
License
MIT — see LICENSE.
Source: README.md at commit dd4f64c
Tools
0Version history
1- v0.2.1LatestSep 16, 2026
Score
50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 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