io.github.akarazhev/bitcoin-risk-brief
NPM · @AKARAZHEV/BITCOIN-RISK-BRIEF-MCP
Daily Bitcoin risk with freshness state on every response. Research context, not advice.
Available components
Last scanned (5 hours ago)
Scores higher than 58% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security83
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/server 2.0.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 79 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 309 tokens (~61/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 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.
- 4 Nov 26 −1
- Stability: pass → 0.93 functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 21 Oct 26 −5
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111770 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
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 5 Nov 2026 · Analysed npm/@akarazhev/bitcoin-risk-brief-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 5 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-jm63-cq47-j5jp | CVE-2026-111770 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:H | yes |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 4 packages
| Packages resolved | 4 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_readiness ~57
Report whether today's Bitcoin risk data can be trusted: the seven readiness checks, the date the data covers, how many days old it is, and the tolerance. Call this first when freshness matters. Analytics and research context, not financial advice.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_brief ~71
Return the daily written brief in one locale: summary, what changed, what to avoid now, and what to confirm next. Available locales are en, ru, zh, de, fr, es, ar; defaults to en. Analytics and research context, not financial advice.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | – |
No output schema declared.
No examples provided.
get_current_risk ~72
Return the latest Bitcoin risk observation: the 0.0-1.0 risk value, its band (low, neutral, high), the HLC3 model price from the last completed daily candle (not a live quote), and that day's low and high. Analytics and research context, not financial advice.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_risk_history ~55
Return the daily Bitcoin risk series, oldest first, for trend and charting questions. Defaults to the last 90 days; maximum 730. Analytics and research context, not financial advice.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
get_risk_levels ~54
Return the solved price ladder: the BTC prices at which the model would report each risk level. Use this to answer what would have to change for the risk band to move. Analytics and research context, not financial advice.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.akarazhev/bitcoin-risk-brief MCP server?
io.github.akarazhev/bitcoin-risk-brief runs locally as an npm package, launched with npx -y @akarazhev/bitcoin-risk-brief-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @akarazhev/bitcoin-risk-brief-mcp
claude mcp add akarazhev-bitcoin-risk-brief -- npx -y @akarazhev/bitcoin-risk-brief-mcp
What is the io.github.akarazhev/bitcoin-risk-brief MCP server?
io.github.akarazhev/bitcoin-risk-brief is an MCP server listed in the public MCP registry as io.github.akarazhev/bitcoin-risk-brief. Daily Bitcoin risk with freshness state on every response. Research context, not advice. This page covers its npm package (@akarazhev/bitcoin-risk-brief-mcp).
Is the io.github.akarazhev/bitcoin-risk-brief MCP server safe to use?
io.github.akarazhev/bitcoin-risk-brief scores 78 out of 100 on VerifyMCP. We recorded 5 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.akarazhev/bitcoin-risk-brief MCP server expose?
io.github.akarazhev/bitcoin-risk-brief exposes 5 tools: check_readiness, get_current_risk, get_risk_history, get_risk_levels, get_brief. Their descriptions and schemas cost roughly 309 tokens of context every time the server is loaded.
Is the io.github.akarazhev/bitcoin-risk-brief MCP server still maintained?
io.github.akarazhev/bitcoin-risk-brief is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.akarazhev/bitcoin-risk-brief MCP server under?
io.github.akarazhev/bitcoin-risk-brief declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.