BPE (Bitcoin Pricing Engine)

Official registry AI and agents

Consolidated Bitcoin market data for AI agents: BBO pricing, ML signals, funding skew, briefings.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @bxetech/bpe-mcp
Claude Code
claude mcp add bpe-bitcoin-pricing-engine -e 'BPE_API_KEY=<your bpe_api_key>' -e 'BPE_BASE_URL=https://mcp.bxetech.com' -- npx -y @bxetech/bpe-mcp@0.2.1
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "bpe-bitcoin-pricing-engine": {
            "command": "npx",
            "args": [
                "-y",
                "@bxetech/bpe-mcp@0.2.1"
            ],
            "env": {
                "BPE_API_KEY": "<your bpe_api_key>",
                "BPE_BASE_URL": "https://mcp.bxetech.com"
            }
        }
    }
}

Environment variables

  • BPE_API_KEY required secret Your BPE API key. Free tier available for evaluation; Agent tier unlocks the full briefing endpoint with ML signals, funding skew, and sentiment. Request at https://bxetech.com/contact.
  • BPE_BASE_URL Override the BPE backend endpoint. Defaults to https://mcp.bxetech.com. Use https://mcp-qa1.bxetech.com for QA testing.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. BPE MCP Server
  2. Why use it
  3. Tools (v0.2)
  4. Install
  5. Configuration
  6. Local development
  7. Roadmap
  8. License

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:

  1. 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.
  2. 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)

ToolWhat it does
get_consolidated_priceCurrent BTC price aggregated across the BPE network
get_market_briefing~4 lines (brief) or 6–8 (detailed) natural-language summary — price, funding skew, ML signal, sentiment, anomalies
get_funding_skewPer-venue annualised funding rates + max-spread pair
get_ml_signalCurrent ML prediction (direction, probability, confidence) at the requested horizon
get_sentiment_snapshotCrypto Fear & Greed index, news sentiment, mempool stress

Install

npm install -g @bxetech/bpe-mcp

Or use npx with no install (recommended for Claude Desktop):

// ~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "bpe": {
      "command": "npx",
      "args": ["-y", "@bxetech/bpe-mcp"],
      "env": {
        "BPE_API_KEY": "bpe_..."
      }
    }
  }
}

Restart Claude Desktop. The five tools appear under the MCP server picker.

Configuration

Env varDefaultNotes
BPE_API_KEY(required)Get one at https://bxetech.com/contact
BPE_BASE_URLhttps://mcp.bxetech.comOverride for self-hosted / local dev
BPE_TIMEOUT_MS5000Per-request timeout

Local development

git clone https://github.com/bxetech/bpe-mcp
cd bpe-mcp
npm install
npm run build
BPE_API_KEY=... npm run dev

To dogfood in Claude Desktop while iterating, point at the local build:

{
  "mcpServers": {
    "bpe-dev": {
      "command": "node",
      "args": ["/abs/path/to/mcp-server/dist/index.js"],
      "env": {
        "BPE_API_KEY": "...",
        "BPE_BASE_URL": "http://localhost:8082"
      }
    }
  }
}

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.

Frequently asked questions

What is BPE (Bitcoin Pricing Engine)?

Consolidated Bitcoin market data for AI agents: BBO pricing, ML signals, funding skew, briefings.

How do I install BPE (Bitcoin Pricing Engine)?

It runs on your machine. In Claude Code: claude mcp add bpe-bitcoin-pricing-engine -e 'BPE_API_KEY=<your bpe_api_key>' -e 'BPE_BASE_URL=https://mcp.bxetech.com' -- npx -y @bxetech/bpe-mcp@0.2.1. For other clients, paste the JSON configuration from this page into their MCP settings.

Does BPE (Bitcoin Pricing Engine) need an API key?

Yes. It expects BPE_API_KEY, which you set in its configuration.

Is BPE (Bitcoin Pricing Engine) open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains BPE (Bitcoin Pricing Engine)?

It is published by bxetech. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.