# Imf Portwatch [Health: Active]

**Category:** 📦 Delivery  
**Repository:** https://github.com/pipeworx-io/mcp-imf-portwatch  
**GitHub Stars:** 2  
**npm Downloads (last month):** 463  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/imf-portwatch

## Description
IMF PortWatch MCP — global maritime trade & chokepoint signals (free, no auth)

## Tools
Capabilities this server exposes over MCP:

- **chokepoints_list** — List the 8 major maritime chokepoints PortWatch tracks (Suez, Panama, Bosphorus, Gibraltar, Dover, Malacca, Hormuz, Bab-el-Mandeb) with annual vessel counts, traffic mix by cargo type (container / dry bulk / tanker / RoRo / general), and top industries by volume. Use to discover what a chokepoint n…
- **chokepoint_daily_traffic** — 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", "…
- **port_search** — Search the PortWatch port database (1,500+ ports globally) by name, country, or ISO3. Returns matching ports with country, continent, latitude/longitude, annual vessel counts by cargo type, top industries, and the port's share of the country's maritime imports/exports. Useful for identifying which…
- **recent_disruptions** — Port-affecting disruption events tracked by PortWatch — tropical cyclones, floods, earthquakes, conflict events — with start/end dates, alert level (GREEN/ORANGE/RED), severity, affected port count, and impacted population. Filter by country, alert level, or year. Use for "what disrupted shipping i…
- **chokepoint_status** — 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 Strai…
- **chokepoint_compare** — Compare chokepoint traffic status across 2 to 6 maritime chokepoints side by side and rank them by how far each one has deviated from its own trailing baseline, so an agent can spot which strait or canal is the anomalous one. Answers "which maritime chokepoint is disrupted right now", "Suez Canal t…

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "imf-portwatch": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-imf-portwatch"]
  }
}
```

## Documentation

## What Imf Portwatch does

Imf Portwatch exposes maritime trade and disruption data from IMF PortWatch through MCP. Its tools cover eight tracked chokepoints—Suez, Panama, Bosphorus, Gibraltar, Dover, Malacca, Hormuz, and Bab-el-Mandeb—as well as a global port database containing more than 1,500 ports.

The server supports both historical context and recent status checks. You can inspect annual vessel volumes and cargo composition, retrieve daily vessel and deadweight-tonnage series, search ports by name or country, and review disruption events such as cyclones, floods, earthquakes, and conflict-related incidents.

## How it works

The hosted MCP endpoint is served by the Pipeworx gateway at `https://gateway.pipeworx.io/imf-portwatch/mcp`. A client can connect directly over HTTP, or launch the npm package as a local stdio bridge that forwards requests to the same gateway. The gateway endpoint also exposes shared Pipeworx meta-tools alongside the pack-specific tools; the local bridge lists the pack tools by default and can include the meta-tools when configured.

Chokepoint status and comparison results use the most recent settled day available from IMF PortWatch's daily AIS-derived transit data. Responses include the data lag and a freshness note. Baselines can show the mean, delta, percentage deviation, direction, and seven-day or 30-day averages, including vessel-type-specific changes.

## Setup and configuration

For a hosted connection, add the endpoint to an MCP client configuration:

```json
{
  "mcpServers": {
    "imf-portwatch": {
      "url": "https://gateway.pipeworx.io/imf-portwatch/mcp"
    }
  }
}
```

The npm bridge can be started with `npx`:

```json
{
  "mcpServers": {
    "imf-portwatch": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-imf-portwatch"]
    }
  }
}
```

The bridge requires network access and has no offline mode. Anonymous use is capped at 50 calls per day. Setting `PIPEWORX_API_KEY` with a key from Pipeworx raises the allowance to 200 calls per day. Set `PIPEWORX_META_TOOLS=1` to list shared tools such as `ask_pipeworx`, discovery, search, and memory tools. When using an HTTPS proxy, newer Node versions can use it with `NODE_USE_ENV_PROXY=1`.

## Tools and capabilities

- `chokepoints_list` provides annual counts, cargo mix, and leading industries for the eight tracked chokepoints.
- `chokepoint_daily_traffic` returns recent-first daily vessel counts, aggregate deadweight tonnage, and cargo-type breakdowns.
- `chokepoint_status` compares a chokepoint's latest settled day with a trailing baseline and reports above, below, or normal traffic.
- `chokepoint_compare` ranks two to six chokepoints by deviation from their respective baselines.
- `port_search` finds ports by name, country, or ISO3 and returns location, traffic, industry, and national trade-share data.
- `recent_disruptions` filters tracked events by country, alert level, or year and reports dates, severity, affected ports, and impacted population.

Chokepoint tools accept common names such as “Suez,” “Hormuz,” and “Bab el-Mandeb,” as well as PortWatch identifiers. The comparison tool sorts results by the largest absolute deviation.

## Limitations and notes

Traffic status is not real-time: “latest” refers to the most recent settled day in the source data. The `chokepoints_list` response may identify whether it came from a primary or fallback layer. In fallback mode, annual totals, coordinates, and top-industry fields can be omitted.

The hosted endpoint does not require an account for initial anonymous calls, but usage limits apply. The npm bridge forwards requests to the gateway rather than running a local copy of the data service. The project is an independent, unofficial integration and is not affiliated with the upstream provider.

_Full upstream README: https://allmcps.com/mcp/imf-portwatch/readme_