get_status_history — mcp MCP Tool Read-only
get_status_history
(get status history) is one of 33 tools on the
mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_status_history from your client
- Claude Code mcp get_status_history run in your project directory
- Claude Desktop mcp get_status_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor mcp get_status_history ~/.cursor/mcp.json
- VS Code mcp get_status_history .vscode/mcp.json
- Zed mcp get_status_history ~/.config/zed/settings.json
- Windsurf mcp get_status_history ~/.codeium/windsurf/mcp_config.json
- Cline mcp get_status_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI mcp get_status_history ~/.gemini/settings.json
- Grok mcp get_status_history .mcp.json (in your project root)
- ChatGPT mcp get_status_history Settings → Connectors → Advanced → Developer mode
- Claude.ai mcp get_status_history Settings → Connectors → Add custom connector
- LangChain mcp get_status_history pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.ironflow.sh/mcpOther tools on this server
- get_price
- get_recent_trades
- get_candles
- get_funding_rates
- get_open_interest
- get_liquidations
- get_liquidation_summary
- get_fills
- get_mark_prices
- get_vault_operations
- get_liquidation_levels
- get_vault_leaderboard
- get_funding_stats
- get_user_state
- get_user_funding
- get_user_maker_taker
- get_user_ledger
- get_pnl_leaderboard
- get_market_top_wallets
- get_markets_snapshot
- get_user_summary
- get_wallet_labels
- get_user_pnl_series
- get_top_traders
- get_market_leaders
- get_early_movers
- get_trader_profile
- list_cohorts
- get_cohort_addresses
- get_status
- get_status_metrics
- list_markets
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.