mcpbeat

Bitcoin Signals MCP Server

com.coinbucha/bitcoin-signals
answering

Bitcoin Signals is answering right now. Last checked 4 min ago. It exposes 7 tools.

Signal-first Bitcoin intelligence: sovereign, hiring & hashrate signals over MCP.

Uptime history 39 hours of history · worst hour 0%
39 hours agonow
45.1%
Uptime 24h
41 of 91 checks
7
Tools
read from the server
384 ms
Response time
average over 24h
open, no key
Access
streamable-http

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.

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 7

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
Spot Bitcoin ETF net-flow figures exactly as the upstream source reports them — latest day plus trailing 5/30-day, per fund where the source breaks it out. Takes no arguments. Returns { available, status, as_of, date_basis, unit, note, disclaimer } plus the flow figures when a document is present; when the feed is absent, stale or unreadable it says so in status and serves no number rather than substituting a zero. 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. 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.
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[] and its own as_of. 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

URLTransportStateLatencyChecked
https://coinbucha.com/api/mcp streamable-http answering 298 ms 4 min ago

Bitcoin Signals — questions

Answers built from our own checks of this server.

What can Bitcoin Signals do?
It exposes 7 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_sovereign_reserves, get_treasury_holdings and 1 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 41 of 91 checks got a reply (45.1%), average response time 384 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 7 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 384 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.