NakamotoNotes Bitcoin Barometer

Bitcoin Barometer: Heat Score, BTC price, ten indicators and daily history. Read-only.

Should I use this

Quality & Safety

A
Description quality
90%
Schema completeness
77%
Naming quality
93%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (1)

  • LOWTool 'get_history' description lacks action verbin get_history

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~350Tokens (tool definitions)
~408 BTypical response size
Minimal attention impact (0.27% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "barometer": {
      "command": "uvx",
      "args": [
        "https://github.com/multiassist/nakamotonotes-mcp/releases/download/v0.1.0/nakamotonotes-barometer.mcpb"
      ]
    }
  }
}

Runnable packages

mcpbhttps://github.com/multiassist/nakamotonotes-mcp/releases/download/v0.1.0/nakamotonotes-barometer.mcpb0.1.0stdio

Remote endpoints

https://nakamotonotes.com/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢get_market_snapshot

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

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢explain_indicator(name)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Indicator name"
    }
  },
  "required": [
    "name"
  ],
  "additionalProperties": false
}
🟢get_history(from, to)

Daily Heat Score and zone between two dates (YYYY-MM-DD, inclusive), from the public daily history.

Input Schema

{
  "type": "object",
  "properties": {
    "from": {
      "type": "string",
      "description": "First day, YYYY-MM-DD"
    },
    "to": {
      "type": "string",
      "description": "Last day, YYYY-MM-DD"
    }
  },
  "required": [
    "from",
    "to"
  ],
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools