bitcoin-signals
Signal-first Bitcoin intelligence: sovereign, hiring & hashrate signals over MCP.
https://coinbucha.com/api/mcpCurrent observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- coinbucha
- Version
- 0.1.1
- Capability keys
- tools, resources, prompts
- Tool names
- scan_signals, get_hiring_signal, get_sovereign_reserves, get_treasury_holdings, get_etf_flows, get_network_signal, get_daily_brew
CoinBucha serves leading, NON-PRICE Bitcoin indicators: sovereign reserve adoption, hiring velocity at Bitcoin and crypto-infrastructure employers, corporate treasury holdings, spot-ETF flow figures as reported, and network hashrate. Every signal is dated, attributed to primary sources, and expressed as a 0-100 strength with a direction (tailwind | headwind | neutral) and a one-line `why`. Start with `scan_signals` for the ranked cross-signal view, then drill into a single domain with `get_sovereign_reserves`, `get_hiring_signal`, `get_treasury_holdings`, `get_etf_flows` or `get_network_signal`. `get_daily_brew` is the pre-written digest of the whole set. Read the `coinbucha://methodology` resource for how each strength is computed. Every payload carries `as_of` — cite it. When a source is missing, stale or unreadable the tool says so explicitly in `status` and `note` instead of serving a figure it cannot stand behind; pass that absence through rather than filling it in, and never
Reported Aug 17, 2026, 05:00 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 280ms
- respondsMCP initialize · 8s limit · HTTP 200 · 696ms
- respondsMCP initialize · 8s limit · HTTP 200 · 293ms
- respondsMCP initialize · 8s limit · HTTP 200 · 381ms