# com.coinbucha/bitcoin-signals (remote · coinbucha.com)

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

- Trust score: 71/100 (medium)
- Change this week: +13
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `coinbucha.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-coinbucha-bitcoin-signals/api-mcp.md), [page](https://verifymcp.io/servers/com-coinbucha-bitcoin-signals/api-mcp)

## Channel facts

- Endpoint: `https://coinbucha.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1175 tokens (~146/item across 8 items; 7 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-coinbucha-bitcoin-signals": {
      "type": "remote",
      "url": "https://coinbucha.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-coinbucha-bitcoin-signals --url https://coinbucha.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-coinbucha-bitcoin-signals:
    url: "https://coinbucha.com/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-coinbucha-bitcoin-signals": {
      "type": "http",
      "url": "https://coinbucha.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 69, +8)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 61, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 60, +2)

- [security] Tool “get_etf_flows” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 34 → 38

### 2026-07-27 (score 58, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 57)

First indexed and scored.

## MCP tools (7)

### `scan_signals` (~182 tokens)

Scan Bitcoin 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.

Input parameters:

- `direction` (string): Keep only signals carrying this direction label
- `min_strength` (number): Only signals with strength >= this
- `signal_types` (array): e.g. ['sovereign_adoption','hiring_velocity']

### `get_hiring_signal` (~129 tokens)

Bitcoin hiring velocity

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.

Input parameters:

- `company` (string): Case-insensitive company filter

### `get_sovereign_reserves` (~139 tokens)

Sovereign Bitcoin 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.

Input parameters:

- `country` (string): Country name or ISO code
- `tier` (integer): Holding tier; 1 = largest holders

### `get_treasury_holdings` (~82 tokens)

Corporate Bitcoin treasuries

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.

### `get_etf_flows` (~112 tokens)

Spot Bitcoin 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.

### `get_network_signal` (~63 tokens)

Bitcoin network hashrate

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.

### `get_daily_brew` (~72 tokens)

CoinBucha 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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-coinbucha-bitcoin-signals/api-mcp#diagnostics

## Score history

- 2026-08-03: 71
- 2026-08-02: 70
- 2026-08-01: 70
- 2026-07-31: 69
- 2026-07-30: 61
- 2026-07-29: 60
- 2026-07-28: 60
- 2026-07-27: 58
- 2026-07-26: 57

## Links

- Remote endpoint: https://coinbucha.com/api/mcp
- Website: https://coinbucha.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-coinbucha-bitcoin-signals/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-coinbucha-bitcoin-signals/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-coinbucha-bitcoin-signals/api-mcp