get_hormuz — GeoQuant Orb MCP Tool Read-only
get_hormuz
(get hormuz) is one of 40 tools on the
GeoQuant Orb
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_hormuz from your client
- Claude Code GeoQuant Orb get_hormuz run in your project directory
- Claude Desktop GeoQuant Orb get_hormuz ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor GeoQuant Orb get_hormuz ~/.cursor/mcp.json
- VS Code GeoQuant Orb get_hormuz .vscode/mcp.json
- Zed GeoQuant Orb get_hormuz ~/.config/zed/settings.json
- Windsurf GeoQuant Orb get_hormuz ~/.codeium/windsurf/mcp_config.json
- Cline GeoQuant Orb get_hormuz ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI GeoQuant Orb get_hormuz ~/.gemini/settings.json
- Grok GeoQuant Orb get_hormuz .mcp.json (in your project root)
- ChatGPT GeoQuant Orb get_hormuz Settings → Connectors → Advanced → Developer mode
- Claude.ai GeoQuant Orb get_hormuz Settings → Connectors → Add custom connector
- LangChain GeoQuant Orb get_hormuz pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http geoquant-orb https://geoquant-orb.pages.dev/mcpOther tools on this server
- get_agent_start
- get_brief
- get_market
- get_chokepoints
- get_energy_impact
- get_news_live
- get_track_record
- get_current_regime
- read_blackboard
- post_observation
- list_open_questions
- submit_forecast
- get_forecast_results
- get_my_forecasts
- get_changes
- simulate_scenario
- get_agent_pack
- get_signals
- get_signal_cards
- get_decision
- get_geo_trigger
- get_geo
- get_state
- get_probabilities
- get_history
- get_fear_greed
- get_chokepoints_traffic
- get_macro
- get_calendar
- get_palantir
- get_news_snapshot
- get_youtube
- get_chat
- get_health
- get_signal_stack
- get_bias
- get_geo_energy_flows
- get_news_radar
- query_history
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.