Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.coinbucha/bitcoin-signals

REMOTE · COINBUCHA.COM · SCANNED SEP 20

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

Available components

0 this week 83 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability88
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2727 tokens (~113/item across 24 items; 8 tools + 16 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the com.coinbucha/bitcoin-signals MCP server?

com.coinbucha/bitcoin-signals is a hosted endpoint at https://coinbucha.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · coinbucha.com

# add to Claude Code
claude mcp add --transport http com-coinbucha-bitcoin-signals 'https://coinbucha.com/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-coinbucha-bitcoin-signals": {
      "url": "https://coinbucha.com/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-coinbucha-bitcoin-signals": {
      "type": "http",
      "url": "https://coinbucha.com/api/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add com-coinbucha-bitcoin-signals --url 'https://coinbucha.com/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-coinbucha-bitcoin-signals:
    url: "https://coinbucha.com/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-coinbucha-bitcoin-signals": {
      "Transport": "http",
      "Url": "https://coinbucha.com/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-coinbucha-bitcoin-signals -t streamable-http -u 'https://coinbucha.com/api/mcp'
// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 12 Sept 26 0
    • New tool “get_signal_history” functional
  • 4 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • New resource “snapshot 2026-09-04” functional
  • 2 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 159 → 106 functional
    • New prompt “hiring_velocity_check” functional
    • New prompt “sovereign_reserve_check” functional
    • New resource “Bhutan” functional
    • New resource “Brazil” functional
    • New resource “China” functional
    • New resource “Czech Republic” functional
    • New resource “El Salvador” functional
    • New resource “Finland” functional
    • New resource “Germany” functional
    • New resource “Pakistan” functional
    • New resource “Ukraine” functional
    • New resource “United Kingdom” functional
    • New resource “United States” functional
    • New resource “daily-brew” functional
    • New resource “sovereign-reserves” functional
    • New resource “treasury-holdings” functional
  • 28 Aug 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_etf_flows” rewrote its description, which is the text the model reads security
    • Server version: 0.1.1 → 0.1.2 functional
    • Tool “get_etf_flows” changed its title: Spot Bitcoin ETF flows → Spot Bitcoin ETF flows (retired) cosmetic
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

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

  • 16 Aug 26 0
    • Server version: 0.1.0 → 0.1.1 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://coinbucha.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=coinbucha.com CN=YR1,O=Let's Encrypt,C=US 9 Aug 2026 7 Nov 2026 RSA 2048 SHA256-RSA 6dad4d009ba10f09334fff799fbfb9041a6
SANs: coinbucha.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of coinbucha.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
coinbucha.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://coinbucha.com/api/mcp Verified 200
http (plaintext) http://coinbucha.com/api/mcp HTTPS enforced 308 https://coinbucha.com/api/mcp
MCP tools · 8 exposed · ~1,100 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_daily_brew ~72

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_etf_flows ~159

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_hiring_signal ~171

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.

NameTypeReqDescription
companystringCase-insensitive company filter

No output schema declared.

No examples provided.

get_network_signal ~63

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_signal_history ~203

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.

NameTypeReqDescription
daysintegerHow many of the most recent dated points to return (1-90)
signal_typestringyesWhich signal's history to return

No output schema declared.

No examples provided.

get_sovereign_reserves ~168

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.

NameTypeReqDescription
countrystringCountry name or ISO code
tierintegerHolding tier; 1 = largest holders

No output schema declared.

No examples provided.

get_treasury_holdings ~82

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scan_signals ~182

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.

NameTypeReqDescription
directionstringKeep only signals carrying this direction label
min_strengthnumberOnly signals with strength >= this
signal_typesarraye.g. ['sovereign_adoption','hiring_velocity']

No output schema declared.

No examples provided.

Common questions

What is the com.coinbucha/bitcoin-signals MCP server?

com.coinbucha/bitcoin-signals is an MCP server listed in the public MCP registry as com.coinbucha/bitcoin-signals. Leading non-price Bitcoin signals over MCP: sovereign, hiring, hashrate. Not financial advice. This page covers its hosted endpoint (https://coinbucha.com/api/mcp).

Is the com.coinbucha/bitcoin-signals MCP server safe to use?

com.coinbucha/bitcoin-signals scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.coinbucha/bitcoin-signals MCP server expose?

com.coinbucha/bitcoin-signals exposes 8 tools: scan_signals, get_hiring_signal, get_sovereign_reserves, get_treasury_holdings, get_etf_flows, and 3 more. Their descriptions and schemas cost roughly 1,100 tokens of context every time the server is loaded.

Does the com.coinbucha/bitcoin-signals MCP server require authentication?

No. We connected to com.coinbucha/bitcoin-signals without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.coinbucha/bitcoin-signals MCP server still maintained?

com.coinbucha/bitcoin-signals is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.