chokepoint_status
Pack: imf-portwatch · Endpoint: https://gateway.pipeworx.io/imf-portwatch/mcp
Chokepoint traffic status for one maritime chokepoint: the most recent settled day of vessel transits scored against a trailing baseline, so an agent can tell at a glance whether shipping through that strait or canal is above, below, or at its normal run rate. Answers “is shipping through the Strait of Hormuz down”, “Suez Canal transit volume this week”, “Panama Canal ship counts vs normal”, “maritime chokepoint disruption check”, “tanker traffic anomaly at Bab el-Mandeb”. Returns the latest day (total vessels, per-vessel-type counts, aggregate capacity in deadweight tonnage), data_lag_days plus a freshness_note, the baseline mean with delta / percent deviation / direction (above, below, normal), 7-day and 30-day means, the same percent deviation per vessel type (tanker, container, dry_bulk, general_cargo, roro — a tanker-only drop at Hormuz is the tradeable signal), and the min and max daily total in the window with their dates. Source is IMF PortWatch daily AIS-derived transit counts, published with a multi-day lag, so the “latest” day is the most recent settled day rather than a live count. Accepts forgiving names — “Hormuz”, “Strait of Hormuz”, “hormuz”, “Suez”, “Panama”, “Bab el-Mandeb”, “Malacca”, “Taiwan”, “Bosphorus”, “Gibraltar”, “Dover” — or a PortWatch portid like “chokepoint6”. Examples: chokepoint_status({chokepoint: “Hormuz”}); chokepoint_status({chokepoint: “Suez Canal”, baseline_days: 30}); chokepoint_status({chokepoint: “Panama”}).
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
chokepoint | string | yes | Chokepoint name, alias, or portid — e.g. “Hormuz”, “Strait of Hormuz”, “Suez Canal”, “Bab el-Mandeb”, “chokepoint6” |
baseline_days | number | no | Length of the trailing baseline window in days, measured backward from the day before the latest settled day (default 90, min 7, max 364). |
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_status","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.