get_token_candles — BlockReq MCP Tool Read-only
get_token_candles
(get token candles) is one of 14 tools on the
BlockReq
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_token_candles from your client
- Claude Code BlockReq get_token_candles run in your project directory
- Claude Desktop BlockReq get_token_candles ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BlockReq get_token_candles ~/.cursor/mcp.json
- VS Code BlockReq get_token_candles .vscode/mcp.json
- Zed BlockReq get_token_candles ~/.config/zed/settings.json
- Windsurf BlockReq get_token_candles ~/.codeium/windsurf/mcp_config.json
- Cline BlockReq get_token_candles ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BlockReq get_token_candles ~/.gemini/settings.json
- Grok BlockReq get_token_candles .mcp.json (in your project root)
- ChatGPT BlockReq get_token_candles Settings → Connectors → Advanced → Developer mode
- Claude.ai BlockReq get_token_candles Settings → Connectors → Add custom connector
- LangChain BlockReq get_token_candles pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http rpc https://mcp.blockreq.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.