chokepoint_daily_traffic
Pack: imf-portwatch · Endpoint: https://gateway.pipeworx.io/imf-portwatch/mcp
Daily vessel counts and aggregate capacity (deadweight tonnage) transiting a specific chokepoint. Returns time series ordered most-recent-first, with per-cargo-type breakdown (container / dry bulk / general cargo / RoRo / tanker). Use for “is Suez traffic back to normal after the Houthi attacks”, “Hormuz throughput vs 30d average”, or any bet predicated on a chokepoint disruption persisting. Accepts friendly names (suez / panama / hormuz / bab-el-mandeb / etc.) or PortWatch portid (chokepoint1..8).
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
chokepoint | string | yes | Friendly name (e.g. “Hormuz”, “Suez Canal”) or portid (“chokepoint7”) |
days | number | no | Lookback window in days (default 30, max 365). Data is daily. |
Example call
curl -X POST https://gateway.pipeworx.io/imf-portwatch/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"chokepoint_daily_traffic","arguments":{}}}'Connect
Add this to your MCP client config, or use one-click install buttons:
{
"mcpServers": {
"imf-portwatch": {
"url": "https://gateway.pipeworx.io/imf-portwatch/mcp"
}
}
}See Getting Started for client-specific install steps.