Skip to main content
Glama
Sign In
NakamotoNotes Bitcoin Barometer

NakamotoNotes Bitcoin Barometer

by multiassist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to NakamotoNotes Bitcoin Barometer

No user-submitted related servers found.

    Related Servers

    • btc-public-data

      matthewrball
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying public Bitcoin network data including fees, mempool status, hashrate, transactions, address stats, and Lightning network information without requiring API keys.
      MIT

    • startmining-mcp

      TIBSP
      A
      license
      A
      quality
      B
      maintenance
      Bitcoin mining data from a self-hosted Bitcoin Core node: live hashprice, difficulty, halving, mempool, ASIC profitability and breakeven calculators, calendar-month averages and history since 2009. 12 tools, no API key.
      13
      72 npm
      MIT
    • BRS Signals MCP Server

      BRS Signals MCP Serverofficial

      brssignals
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides real-time Bitcoin market regime detection by fusing on-chain, derivatives, and absence sensors into a convergence score, enabling AI agents to make informed trading decisions.
      49 PyPI
      1
      MIT
    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
    ResponsivenessOutdated data

    Resources