get_history — NakamotoNotes Bitcoin Barometer MCP Tool Read-only
get_history
(get history) is one of 3 tools on the
NakamotoNotes Bitcoin Barometer
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_history from your client
- Claude Code NakamotoNotes Bitcoin Barometer get_history run in your project directory
- Claude Desktop NakamotoNotes Bitcoin Barometer get_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor NakamotoNotes Bitcoin Barometer get_history ~/.cursor/mcp.json
- VS Code NakamotoNotes Bitcoin Barometer get_history .vscode/mcp.json
- Zed NakamotoNotes Bitcoin Barometer get_history ~/.config/zed/settings.json
- Windsurf NakamotoNotes Bitcoin Barometer get_history ~/.codeium/windsurf/mcp_config.json
- Cline NakamotoNotes Bitcoin Barometer get_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI NakamotoNotes Bitcoin Barometer get_history ~/.gemini/settings.json
- Grok NakamotoNotes Bitcoin Barometer get_history .mcp.json (in your project root)
- ChatGPT NakamotoNotes Bitcoin Barometer get_history Settings → Connectors → Advanced → Developer mode
- Claude.ai NakamotoNotes Bitcoin Barometer get_history Settings → Connectors → Add custom connector
- LangChain NakamotoNotes Bitcoin Barometer get_history pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http barometer https://nakamotonotes.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 17 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.