get_rail_freight_status — risk intelligence MCP Tool Read-only
get_rail_freight_status
(get rail freight status) is one of 33 tools on the
risk intelligence
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_rail_freight_status from your client
- Claude Code risk intelligence get_rail_freight_status run in your project directory
- Claude Desktop risk intelligence get_rail_freight_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor risk intelligence get_rail_freight_status ~/.cursor/mcp.json
- VS Code risk intelligence get_rail_freight_status .vscode/mcp.json
- Zed risk intelligence get_rail_freight_status ~/.config/zed/settings.json
- Windsurf risk intelligence get_rail_freight_status ~/.codeium/windsurf/mcp_config.json
- Cline risk intelligence get_rail_freight_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI risk intelligence get_rail_freight_status ~/.gemini/settings.json
- Grok risk intelligence get_rail_freight_status .mcp.json (in your project root)
- ChatGPT risk intelligence get_rail_freight_status Settings → Connectors → Advanced → Developer mode
- Claude.ai risk intelligence get_rail_freight_status Settings → Connectors → Add custom connector
- LangChain risk intelligence get_rail_freight_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport sse risk-intelligence https://www.supplymaven.com/api/mcpOther tools on this server
- supply_chain_risk_assessment
- risk_pillar_breakdown
- manufacturing_output_indicator
- commodity_price_monitor
- port_congestion_monitor
- supply_chain_disruption_alerts
- get_action_signals
- get_border_delays
- get_chokepoint_traffic
- get_air_cargo_disruptions
- get_trade_policy_impacts
- get_energy_breakdown
- get_freight_transportation_index
- get_economic_indicators
- get_natural_disaster_alerts
- get_corridor_risk
- get_predictive_signals
- get_manufacturing_anomalies
- get_supply_chain_weekly_brief
- get_signal_narratives
- get_energy_forecast
- get_gdi_trend_analysis
- get_commodity_volatility_alerts
- get_port_congestion_trends
- get_intelligence_briefs
- get_weekly_content_package
- get_freight_rate_observations
- get_customs_trade_events
- get_labor_actions
- get_freight_rate_pressure
- get_customs_friction_baseline
- get_disaster_events
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.