node — Blockchair MCP Tool
node
(node) is one of 41 tools on the
Blockchair
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call node from your client
- Claude Code Blockchair node run in your project directory
- Claude Desktop Blockchair node ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Blockchair node ~/.cursor/mcp.json
- VS Code Blockchair node .vscode/mcp.json
- Zed Blockchair node ~/.config/zed/settings.json
- Windsurf Blockchair node ~/.codeium/windsurf/mcp_config.json
- Cline Blockchair node ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Blockchair node ~/.gemini/settings.json
- Grok Blockchair node .mcp.json (in your project root)
- ChatGPT Blockchair node Settings → Connectors → Advanced → Developer mode
- Claude.ai Blockchair node Settings → Connectors → Add custom connector
- LangChain Blockchair node pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http blockchair https://gateway.pipeworx.io/blockchair/mcpOther tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- stats
- block
- transaction
- address
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.