Skip to main content
Glama
Sign In
NakamotoNotes Bitcoin Barometer

NakamotoNotes Bitcoin Barometer

by multiassist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

NakamotoNotes Bitcoin Barometer — MCP server

Read-only MCP server for the NakamotoNotes Bitcoin Barometer: Heat Score 0-100, zone, BTC price with 24h/7d change, the ten indicators with value and heat, and daily history.

Install

  • Hosted (no install): add https://nakamotonotes.com/mcp as a remote MCP server (Streamable HTTP, no auth).

    • Claude: one click from the Claude directory.

    • Grok: grok.com/connectors > New Connector > Custom, paste the URL.

    • Cursor and Grok Bot: install the nakamotonotes-bitcoin-barometer plugin (manifest in .cursor-plugin/plugin.json, server in mcp.json).

  • Claude Desktop (one click): download nakamotonotes-barometer.mcpb from nakamotonotes.com and open it.

  • Any MCP client (stdio): npx -y @nakamotonotes/mcp

{ "mcpServers": { "nakamotonotes": { "command": "npx", "args": ["-y", "@nakamotonotes/mcp"] } } }

Tools: get_market_snapshot, explain_indicator, get_history. No API key, no personal data; it reads the public feed at https://nakamotonotes.com/open/barometer.json.

Data licence: CC BY 4.0, attribute NakamotoNotes. The reading describes the current state against its history; it is not a forecast or investment advice.

Available Tools

3 tools
explain_indicatorExplain one Barometer indicatorB
Read-onlyIdempotent
Inspect

What one Barometer indicator measures, its current value and heat, and how it feeds the score.

Inputs: name (required). Returns: key, asOf, heat, name, +8 more

get_historyHeat Score historyA
Read-onlyIdempotent
Inspect

Heat Score history from the public daily history. from is required (YYYY-MM-DD), to defaults to the last day. interval day|week|month|auto (auto picks the finest that fits 400 points); max_points (1-400) caps the points: auto uses 180 by default, and with max_points the latest points are kept and truncated is set. A summary covers the whole range.

Inputs: from (required), to, interval, max_points. Returns: to, from, count, points, +8 more

get_market_snapshotBitcoin Barometer snapshotA
Read-onlyIdempotent
Inspect

Current Bitcoin Barometer reading: Heat Score 0-100, zone and zone bands, yesterday and last week, BTC price with 24h and 7d change, and the ten indicators with value, heat and a one-line meaning. Descriptive only.

Inputs: no named parameters. Returns: asOf, zone, price, score, +12 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool occupies a distinct slice: get_market_snapshot returns the current reading, explain_indicator drills into a single indicator, and get_history returns a time series. There is no plausible way for an agent to confuse these three purposes.

    Naming Consistency4/5

    All three names are snake_case verb_noun (get_market_snapshot, explain_indicator, get_history), which is predictable. The minor deviation is mixing the 'get_' prefix with 'explain_', though the verb choice is semantically justified.

    Tool Count4/5

    Three tools is on the thin side but appropriate for a focused, read-only data service with a single domain (Bitcoin Barometer readings). Nothing feels redundant or padded.

    Completeness4/5

    The surface covers the lifecycle of the data: current snapshot, per-indicator explanation, and historical heat scores with flexible interval/point controls. The main gap is that indicator-level values are only available 'now' via the snapshot, not historically.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Resources

    Related MCP Connectors

    Related MCP Servers