NakamotoNotes Bitcoin Barometer
MCPB · NAKAMOTONOTES-BAROMETER.MCPB · 2 COMPONENTS
Bitcoin Barometer: Heat Score, BTC price, ten indicators and daily history. Read-only.
Available components
Last scanned (1 hour ago)
Scores higher than 78% of MCPB 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 Security13
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- No install/post-install scripts declared.Pass
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency45
- 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 (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 192 tokens (~64/item across 3 items; 3 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 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
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.
- 15 Oct 26 43
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 17 Oct 2026 · Analysed mcpb/https://github.com/multiassist/nakamotonotes-mcp/releases/download/v0.1.0/nakamotonotes-barometer.mcpb@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
explain_indicator ~83
What one Barometer indicator measures, its current value and heat, and how it feeds the score. Names: monthlyRSI, mayerMultiple, piCycleProximity, mvrvZScore, nupl, puellMultiple, twoYearHighProximity, roc90, fearAndGreed, searchInterestHeat.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Indicator name |
No output schema declared.
No examples provided.
get_history ~55
Daily Heat Score and zone between two dates (YYYY-MM-DD, inclusive), from the public daily history.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | First day, YYYY-MM-DD |
| to | string | yes | Last day, YYYY-MM-DD |
No output schema declared.
No examples provided.
get_market_snapshot ~54
Current Bitcoin Barometer reading: Heat Score 0-100, zone, BTC price with 24h and 7d change, and the ten indicators with value, heat and a one-line meaning. Descriptive only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the NakamotoNotes Bitcoin Barometer MCP server?
NakamotoNotes Bitcoin Barometer ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, e45efc974839527f2bc847dc6e4540d6aea60751e59d200019d8d2d38151f178; the commands to do that are on this page. If it does not match, do not open it.
mcpb · nakamotonotes-barometer.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
e45efc974839527f2bc847dc6e4540d6aea60751e59d200019d8d2d38151f178
macOS / Linux
echo "e45efc974839527f2bc847dc6e4540d6aea60751e59d200019d8d2d38151f178 nakamotonotes-barometer.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\nakamotonotes-barometer.mcpb).Hash -eq "e45efc974839527f2bc847dc6e4540d6aea60751e59d200019d8d2d38151f178"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the NakamotoNotes Bitcoin Barometer MCP server?
NakamotoNotes Bitcoin Barometer is an MCP server listed in the public MCP registry as com.nakamotonotes/barometer. Bitcoin Barometer: Heat Score, BTC price, ten indicators and daily history. Read-only. This page covers its MCPB bundle (https://github.com/multiassist/nakamotonotes-mcp/releases/download/v0.1.0/nakamotonotes-barometer.mcpb).
Is the NakamotoNotes Bitcoin Barometer MCP server safe to use?
NakamotoNotes Bitcoin Barometer scores 43 out of 100 on VerifyMCP. 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 NakamotoNotes Bitcoin Barometer MCP server expose?
NakamotoNotes Bitcoin Barometer exposes 3 tools: get_market_snapshot, explain_indicator, get_history. Their descriptions and schemas cost roughly 192 tokens of context every time the server is loaded.
What licence is the NakamotoNotes Bitcoin Barometer MCP server under?
NakamotoNotes Bitcoin Barometer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.