query_ports — eYKON Intelligence MCP Tool Read-only
query_ports
(query ports) is one of 24 tools on the
eYKON Intelligence
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call query_ports from your client
- Claude Code eYKON Intelligence query_ports run in your project directory
- Claude Desktop eYKON Intelligence query_ports ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor eYKON Intelligence query_ports ~/.cursor/mcp.json
- VS Code eYKON Intelligence query_ports .vscode/mcp.json
- Zed eYKON Intelligence query_ports ~/.config/zed/settings.json
- Windsurf eYKON Intelligence query_ports ~/.codeium/windsurf/mcp_config.json
- Cline eYKON Intelligence query_ports ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI eYKON Intelligence query_ports ~/.gemini/settings.json
- Grok eYKON Intelligence query_ports .mcp.json (in your project root)
- ChatGPT eYKON Intelligence query_ports Settings → Connectors → Advanced → Developer mode
- Claude.ai eYKON Intelligence query_ports Settings → Connectors → Add custom connector
- LangChain eYKON Intelligence query_ports pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http intelligence https://eykon.ai/api/mcpOther tools on this server
- query_vessels
- query_aircraft
- query_conflicts
- query_refineries
- query_mines
- query_power_plants
- query_pipelines
- query_airports
- query_weather
- query_thermal_anomalies
- query_nightlights
- query_agent_reports
- query_posture_scores
- query_convergences
- query_shadow_fleet_leads
- query_dark_contact_events
- query_calibration
- query_precursor_matches
- run_chokepoint_scenario
- run_sanctions_wargame
- query_regime_shifts
- query_entities
- expand_actor_network
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.