Bitcoin Signals MCP Server

by coinbucha Your server? Claim it

answering

Bitcoin Signals is answering right now. Last checked 4 min ago. It exposes 8 tools. Last commit 8 Sep 2026.

Leading non-price Bitcoin signals over MCP: sovereign, hiring, hashrate. Not financial advice.

Uptime history 47 days of history · worst day 34%

47 days agonow

34.8%

Uptime 24h

32 of 92 checks

Tools

read from the server

404 ms

Response time

average over 24h

Stars

last commit 8 Sep 2026

What changed 6

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 August 2026. No other catalogue keeps this.

12 Sep a tool appeared get_signal_history

27 Aug a tool description was rewritten get_etf_flows

27 Aug a tool changed version

15 Aug a tool changed version

13 Aug a tool description was rewritten get_hiring_signal

11 Aug a tool description was rewritten get_sovereign_reserves

Bitcoin Signals does not always answer

Over the last week it answered 36.7% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add bitcoin-signals --transport http https://coinbucha.com/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "bitcoin-signals": {
      "url": "https://coinbucha.com/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.bitcoin-signals]
url = "https://coinbucha.com/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "bitcoin-signals": {
      "url": "https://coinbucha.com/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "bitcoin-signals": {
      "url": "https://coinbucha.com/api/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

daily

get_daily_brew

The day's machine-readable digest of the whole signal set — the CoinBucha Daily Brew. Takes no arguments. Returns { date, btc_price_usd, headline, signals_summary[] }, one summary line per signal with its strength, direction and one-line why. Example: {}. Information, not financial advice.

etf

get_etf_flows

RETIRED: this tool is no longer advertised and serves no flow figures. No spot-Bitcoin-ETF flow source is available that is both key-free and permitted to redistribute, so CoinBucha never had a licensed figure to serve here. It remains callable so existing integrations do not break: it takes no arguments and returns { available: false, status, as_of, date_basis, unit, note, disclaimer }, stating the absence explicitly. Read that absence as absent — never as a zero flow. For live signals use scan_signals, get_sovereign_reserves, get_treasury_holdings, get_hiring_signal, get_network_signal or get_daily_brew. Example: {}. Information, not financial advice.

hiring

get_hiring_signal

Hiring velocity across tracked Bitcoin and crypto-infrastructure employers, counted from their live ATS boards. Returns { as_of, companies[], note, why, disclaimer }; each company carries company, ticker, category, ats, careers_url, open_roles, open_roles_30d_ago, open_roles_90d_ago and the derived delta_30d, delta_90d and pct_30d. Example: {"company": "coinbase"} for one employer, or {} for every employer tracked. When a company filter matches no tracked employer the response adds coverage_note and tracked_count, saying that the name is outside the tracked set — a limit of coverage, not a finding about whether that company is hiring. Information, not financial advice.

network

get_network_signal

Bitcoin network hashrate level and trend. Takes no arguments. Returns { as_of, hashrate_eh (exahashes per second), pct_30d, pct_90d, why, disclaimer }. Example: {}. Information, not financial advice.

scan

scan_signals

Ranked cross-signal feed of CoinBucha's leading, non-price Bitcoin indicators. Returns { as_of, btc_price_usd, count, signals[], disclaimer }, where each signal carries id, type, title, value, unit, signal_strength (0-100), direction (tailwind | headwind | neutral), a one-line why, sources[] and its own as_of. Optional filters narrow by strength, direction or signal type. Example: {"min_strength": 70, "direction": "tailwind"} — call with {} for the full ranked list. Observational data; information, not financial advice.

signal

get_signal_history

Dated strength history for one CoinBucha signal, newest first. Returns { as_of, signal_type, title, unit, count, points[], truncated, available_points, tier_window_points, freshness, why, disclaimer, cite }, where each point carries date, signal_strength (0-100) and direction (tailwind | headwind | neutral). Example: {"signal_type": "network_hashrate", "days": 30}. `signal_type` is one of sovereign_adoption, hiring_velocity, corporate_treasury, network_hashrate. Anonymous and free-tier callers receive the most recent points only and are told so by `truncated` and `available_points`; no figure is ever altered or interpolated to fit a window. Observational data; information, not financial advice.

sovereign

get_sovereign_reserves

Nation-state Bitcoin holdings, ranked largest first. Returns { as_of, btc_price_usd, count, sovereigns[], disclaimer }; each row carries country_name, country_code, holdings_btc, status, tier (1 = largest holders), framework, sources[], its own as_of, and source_quality (primary = confirmed against the state's own publication; secondary = reported, not confirmed at source — derived from that row's sources[]). Filter by country name or ISO code, or by tier. Example: {"country": "US"} or {"tier": 1} — call with {} for the full ranking. Information, not financial advice.

treasury

get_treasury_holdings

Bitcoin held on the balance sheets of tracked public companies, in aggregate and by largest holder. Takes no arguments. Returns { as_of, total_btc, company_count, total_value_usd, top[], why, disclaimer }, where top[] lists the largest holders as { name, symbol, btc }. Example: {}. Information, not financial advice.

Endpoints

URL	Transport	State	Latency	Checked
https://coinbucha.com/api/mcp	streamable-http	answering	349 ms	4 min ago

Alternatives to Bitcoin Signals

same job, measured the same way

Alphaassay

by alphaassay

Fail-closed backtest/signal validation: overfitting, leakage, deflated Sharpe. NOT financial advice.

21 tools answering

Headless Tracker

by tamaspetki

Read-only MCP server: your AI sees your crypto portfolio, never your keys. Not financial advice.

66 installs/wk local only

Quantustik

by quantustik

Live S&P 500 quantum-model signals, forecasts and trade plans. Educational, not financial advice.

36 installs/wk 26 tools answering

Nordic Financial MCP

by aidatanordic

Semantic search over Nordic filings, press releases, macro data and electricity prices.

7 tools answering

Marketing Compliance

by northpoint

Crypto marketing compliance rulesets over MCP: MiCA, FCA, GDPR, SEC, MAS, VARA. Not legal advice.

13 tools answering

DESK LEAD x402 — high-ticket packs $50/$100/$150

by workers-desk-x402-gh-desk-x402

~17 tools; HT packs $50/$100/$150. tools/list free; tools/call USDC Base x402. Not financial advice.

17 tools answering

Toolstem MCP Server

by toolstem

Financial intelligence MCP for AI agents — DCF, ratios, comparisons. Pre-computed signals.

69 installs/wk local only

Ozon Seller MCP Server

by woyaxnini

MCP server for Ozon Seller API. 26 tools: products, prices, orders, analytics, finance, rating.

61 installs/wk local only

Bitcoin Signals — questions

Answers built from our own checks of this server.

What can Bitcoin Signals do?

It exposes 8 tools, read directly from the server on our last check. Among them: get_daily_brew, get_etf_flows, get_hiring_signal, get_network_signal, get_signal_history, get_sovereign_reserves and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Bitcoin Signals working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 32 of 92 checks got a reply (34.8%), average response time 404 ms. The bar chart above shows every period we have measured.

How do I connect Bitcoin Signals?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Bitcoin Signals need an API key?

No. Bitcoin Signals completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Bitcoin Signals?

It answers our handshake in 404 ms on average, which is faster than 37% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Bitcoin Signals open source?

Yes — it is published under the MIT licence, written in Python and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.