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
Arguments
{
"chokepoint": "Hormuz",
"days": 30
}
curl
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":{"chokepoint":"Hormuz","days":30}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('chokepoint_daily_traffic', {
"chokepoint": "Hormuz",
"days": 30
});
More examples
{
"chokepoint": "Suez Canal"
}
Response shape
Always returns: source, portid, portname, days_returned, latest, summary, series
| Field | Type | Description |
|---|---|---|
source | string | |
portid | string | |
portname | string | |
days_returned | number | |
latest | object | |
data_lag_days | number | null | |
freshness_note | string | |
summary | object | |
series | array |
Full JSON Schema
{
"type": "object",
"description": "Daily vessel transits through a maritime chokepoint. PortWatch publishes on a lag — data_lag_days and freshness_note say how stale the newest row is.",
"properties": {
"source": {
"type": "string"
},
"portid": {
"type": "string"
},
"portname": {
"type": "string"
},
"days_returned": {
"type": "number"
},
"latest": {
"type": "object",
"properties": {
"date": {
"type": "string"
},
"n_total": {
"type": [
"number",
"null"
]
},
"n_container": {
"type": [
"number",
"null"
]
},
"n_dry_bulk": {
"type": [
"number",
"null"
]
},
"n_general_cargo": {
"type": [
"number",
"null"
]
},
"n_roro": {
"type": [
"number",
"null"
]
},
"n_tanker": {
"type": [
"number",
"null"
]
},
"capacity_dwt": {
"type": [
"number",
"null"
]
}
}
},
"data_lag_days": {
"type": [
"number",
"null"
]
},
"freshness_note": {
"type": "string"
},
"summary": {
"type": "object",
"properties": {
"avg_vessels_7d": {
"type": [
"number",
"null"
]
},
"avg_vessels_30d": {
"type": [
"number",
"null"
]
},
"recent_vs_baseline_ratio": {
"type": [
"number",
"null"
]
}
}
},
"series": {
"type": "array",
"items": {
"type": "object",
"properties": {
"date": {
"type": "string"
},
"n_total": {
"type": [
"number",
"null"
]
},
"n_container": {
"type": [
"number",
"null"
]
},
"n_dry_bulk": {
"type": [
"number",
"null"
]
},
"n_general_cargo": {
"type": [
"number",
"null"
]
},
"n_roro": {
"type": [
"number",
"null"
]
},
"n_tanker": {
"type": [
"number",
"null"
]
},
"capacity_dwt": {
"type": [
"number",
"null"
]
}
}
}
}
},
"required": [
"source",
"portid",
"portname",
"days_returned",
"latest",
"summary",
"series"
]
}
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.