Bitcoin Risk Brief MCP server
io.github.akarazhev/bitcoin-risk-brief·v0.1.1Daily Bitcoin risk with freshness state on every response. Research context, not advice.
0 stars47 downloads/wk
Reviews
Write oneNobody has reviewed Bitcoin Risk Brief yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Bitcoin Risk Brief tools (5)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
check_readinessget_briefget_current_riskget_risk_historyget_risk_levels
Public scan report
scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it
- Code scan6 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 2 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Bitcoin Risk Brief compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 95% of 48,255 servers
- Tools
- 5
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 47
- more than 39% of 12,191 servers with a package
What its tools let an agent do: 5 read
Install Bitcoin Risk Brief in Claude Code, Cursor or VS Code
Runs npx -y @akarazhev/bitcoin-risk-brief-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add bitcoin-risk-brief -- npx -y @akarazhev/bitcoin-risk-brief-mcp
What the publisher says
From the Bitcoin Risk Brief repository's README, as published. We do not edit it. Read it on GitHub
Bitcoin Risk Brief
Bitcoin Risk Brief is a free, open-source product that turns canonical daily BTC/USD data into a transparent risk score, freshness state, and scenario price ladder. It is free permanently: no paid tier, no accounts, no SLA. The owned source code, documentation, and configuration are Apache-2.0; bundled third-party BTC/USD market data is not.
First viewport captured on 2026-08-09; the values shown are a point-in-time example.
Live product: bitcoinriskbrief.minihub.app
Check readiness before using any current value:
curl --fail --silent --show-error https://bitcoinriskbrief.minihub.app/api/readinessResponse captured on 2026-08-09:
{
"status": "ready",
"checks": {
"risk_data_available": true,
"validation_available": true,
"risk_range_ok": true,
"validation_has_rows": true,
"latest_matches_validation_end": true,
"source_is_canonical": true,
"data_fresh": true
},
"data": {
"latest_date": "2026-08-08",
"covered_end": "2026-08-08",
"data_age_days": 1,
"max_age_days": 2,
"source": "coinmarketcap_csv",
"row_count": 5871,
"methodology_version": "crypto-scout-canonical-v1.1"
}
}What it does
- Computes a daily 0.0–1.0 Bitcoin risk metric from the canonical collector/btc-csv/btcusddaily.csv history.
- Shows the latest low, neutral, or high state alongside a two-year risk history chart.
- Displays completed-candle HLC3 model price context and a risk-level scenario ladder in 0.025 increments.
- Publishes a daily brief in English, Russian, Simplified Chinese, German, French, Spanish, and Arabic.
- Exposes read-only analytics endpoints and accepts email waitlist contacts server-side, never in browser storage; users should not submit sensitive information.
What makes it different
- Visible freshness and readiness. The UI shows the latest completed day and validation state; /api/readiness returns HTTP 503 when freshness or validation checks fail.
- Deterministic and reproducible. A versioned methodology recomputes the metric from the same canonical daily history, with validation metadata recording each import.
- Scenarios, not forecasts. The price ladder runs hypothetical prices through the same model to show where risk levels would change; it is not a prediction or trading instruction.
Current Status
Current operational status, evidence, and accepted limitations: Production Readiness.
For AI agents
Start with the repository llms.txt. This branch defines the machine-readable /api/openapi.json endpoint; deployment remains pending operator work. Use the Agent Access Pack for endpoint examples, cache semantics, and interpretation boundaries.
Agents must call /api/readiness first, bind reported values to its dates and freshness state, and preserve the analytics-not-advice framing.
Architecture
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Bitcoin Risk Brief: common questions
- Is Bitcoin Risk Brief MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Bitcoin Risk Brief safety report
- How do I install Bitcoin Risk Brief?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Bitcoin Risk Brief need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is Bitcoin Risk Brief maintained?
- The last commit was 3 days ago (2026-11-01). The latest release is v0.1.1.
- How does Bitcoin Risk Brief compare with other MCP servers?
- safety score 92/100 (higher than 95% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.