rvn_node_status — robotbase mcp MCP Tool
rvn_node_status
(rvn node status) is one of 25 tools on the
robotbase mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call rvn_node_status from your client
- Claude Code robotbase mcp rvn_node_status run in your project directory
- Claude Desktop robotbase mcp rvn_node_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor robotbase mcp rvn_node_status ~/.cursor/mcp.json
- VS Code robotbase mcp rvn_node_status .vscode/mcp.json
- Zed robotbase mcp rvn_node_status ~/.config/zed/settings.json
- Windsurf robotbase mcp rvn_node_status ~/.codeium/windsurf/mcp_config.json
- Cline robotbase mcp rvn_node_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI robotbase mcp rvn_node_status ~/.gemini/settings.json
- Grok robotbase mcp rvn_node_status .mcp.json (in your project root)
- ChatGPT robotbase mcp rvn_node_status Settings → Connectors → Advanced → Developer mode
- Claude.ai robotbase mcp rvn_node_status Settings → Connectors → Add custom connector
- LangChain robotbase mcp rvn_node_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http robotbase-mcp https://robotbase.cc/mcp
Other tools on this server
- list_chains
- chain_status
- zec_chain_info
- zec_recent_blocks
- btc_fee_estimates
- btc_mempool_summary
- btc_tx_lookup
- btc_block_summary
- btc_address_summary
- kas_node_status
- kas_pool_status
- rvn_pool_status
- pow_halving_oracle
- pow_network_mining_intel
- get_recommended_fee_rate
- mempool_congestion_status
- zec_shielded_pools_metrics
- kas_pool_attribution_intel
- robotbase_pool_worker_query
- broadcast_raw_transaction
- zec_block_attribution_intel
- rvn_asset_lookup
- utxo_chain_status
- robotbase_services
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.