MCP server exposing 3 tools for global-fishing-watch.
This URL is a JSON-RPC 2.0 endpoint over HTTP. Issue POST requests with a JSON-RPC body. Browsers and search crawlers land here on GET.
POST https://gateway.pipeworx.io/global-fishing-watch/mcp
Content-Type: application/json
{"jsonrpc":"2.0","id":1,"method":"tools/list"}gfwfish_vessels_search — Search the Global Fishing Watch vessel identity database by name, MMSI, IMO or call sign. Returns each matching vessel with its GFW vessel id (pass it to gfwfish_events), flag state, gear type, registry names and the AIS transmission window. AUTHORITATIVE for identifying a fishing or carrier vessel across flag and name changes. Requires your own free GFW API token, passed as _apiKey.gfwfish_events — Global Fishing Watch vessel events over a date range — apparent fishing, encounters between vessels at sea, loitering, port visits and AIS gaps (transmission switched off). Each event carries its position, start/end time and the vessels involved. Answers "where was this vessel fishing", "did it meet another vessel at sea", "did it go dark". Requires your own free GFW API token, passed as _apiKey.gfwfish_4wings_report — Aggregate apparent fishing effort (hours) from Global Fishing Watch over a bounding box and date range, grouped by flag state, gear type or vessel. This is the AIS-derived fishing-pressure layer behind the GFW map — use it for "how much fishing happened in this area, by whose fleet". Requires your own free GFW API token, passed as _apiKey.Code samples (curl / TypeScript / one-click client install), schemas, and the live playground are on the pack page:
https://pipeworx.io/packs/global-fishing-watch/
Pipeworx is an open MCP gateway connecting AI agents to live data. pipeworx.io