Skip to main content
Glama
multiassist

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
      B
      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
      A
      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
      306 npm
      MIT
    • BRS Signals MCP Server by brssignals

      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.
      35 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.6/5.0

    Scored across 3 tools

    Disambiguation4/5

    Each tool has a distinct angle: get_market_snapshot is the current full reading, get_history is a time series, and explain_indicator is a deep dive on a single indicator. There is mild overlap since the snapshot already includes indicator values and one-line meanings, but the descriptions distinguish 'current overview' from 'explanation' clearly enough.

    Naming Consistency4/5

    All names are snake_case verb_noun, but two use the get_ prefix while explain_indicator uses explain_. The deviation is minor and readable, so the pattern is still mostly predictable.

    Tool Count4/5

    Three tools is on the lean side, but for a read-only, descriptive barometer the small surface is well-scoped: one for the current reading, one for history, one for indicator education. Nothing feels redundant.

    Completeness4/5

    The lifecycle of a read-only data source is largely covered: current snapshot, historical series, and per-indicator explanation. Minor gaps remain, such as listing all valid indicator names or fetching a full snapshot for a past date, but agents can work around these via get_history.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources