io.github.akarazhev/bitcoin-risk-brief
NPM · @AKARAZHEV/BITCOIN-RISK-BRIEF-MCP · SCANNED AUG 20
Daily Bitcoin risk with freshness state on every response. Research context, not advice.
Available components
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 →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 3 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 2 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @akarazhev/bitcoin-risk-brief-mcp
claude mcp add akarazhev-bitcoin-risk-brief -- npx -y @akarazhev/bitcoin-risk-brief-mcp
codex mcp add akarazhev-bitcoin-risk-brief -- npx -y @akarazhev/bitcoin-risk-brief-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"akarazhev-bitcoin-risk-brief": {
"type": "local",
"command": [
"npx",
"-y",
"@akarazhev/bitcoin-risk-brief-mcp"
],
"enabled": true
}
}
} openclaw mcp add akarazhev-bitcoin-risk-brief --command npx --arg -y --arg @akarazhev/bitcoin-risk-brief-mcp
mcp_servers:
akarazhev-bitcoin-risk-brief:
command: "npx"
args: ["-y", "@akarazhev/bitcoin-risk-brief-mcp"] {
"mcpServers": {
"akarazhev-bitcoin-risk-brief": {
"command": "npx",
"args": [
"-y",
"@akarazhev/bitcoin-risk-brief-mcp"
]
}
}
} 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.
- 18 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Aug 26 52
First indexed and scored.
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 Aug 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 |
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| Tree resolution | Complete |
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.
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.