# Global Fishing Watch (npm · @pipeworx/mcp-global-fishing-watch)

Global Fishing Watch — AIS-derived fishing vessel identity, at-sea events (apparent fishing…

- Trust score: 81/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-global-fishing-watch/global-fishing-watch-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-global-fishing-watch/global-fishing-watch-mcp)
- npm · `@pipeworx/mcp-global-fishing-watch`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-global-fishing-watch/pipeworx-mcp-global-fishing-watch.md), [page](https://verifymcp.io/servers/pipeworx-io-global-fishing-watch/pipeworx-mcp-global-fishing-watch)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-global-fishing-watch`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-global-fishing-watch).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1083 tokens (~361/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Global Fishing Watch MCP server?

Global Fishing Watch runs locally as an npm package, launched with npx -y @pipeworx/mcp-global-fishing-watch. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-global-fishing-watch -- npx -y @pipeworx/mcp-global-fishing-watch
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-global-fishing-watch": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-global-fishing-watch"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-global-fishing-watch": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-global-fishing-watch"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-global-fishing-watch -- npx -y @pipeworx/mcp-global-fishing-watch
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-global-fishing-watch": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-global-fishing-watch"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-global-fishing-watch --command npx --arg -y --arg @pipeworx/mcp-global-fishing-watch
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-global-fishing-watch:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-global-fishing-watch"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-global-fishing-watch": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-global-fishing-watch"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-global-fishing-watch -t stdio -c npx -a -y @pipeworx/mcp-global-fishing-watch
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-global-fishing-watch": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-global-fishing-watch"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 80, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 64, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-01 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 78, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 77)

First indexed and scored.

## MCP tools (3)

### `gfwfish_vessels_search` (~292 tokens)

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.

Input parameters:

- `_apiKey` (string): Your own Global Fishing Watch API token (BYO). Get one free for non-commercial use at globalfishingwatch.org/our-apis/tokens: sign in, request an API access token, and pass it here.
- `datasets` (string): Comma-separated GFW vessel datasets. Default "public-global-vessel-identity:latest".
- `includes` (string): Comma-separated extras to return: MATCH_CRITERIA, OWNERSHIP, AUTHORIZATIONS.
- `limit` (number): Max vessels to return (1-50, default 10).
- `query` (string, required): Vessel name, MMSI, IMO or call sign — at least 3 characters, e.g. "ARCTIC LOON" or "224224000".
- `since` (string): Paging CURSOR from a previous call's next_since. This endpoint pages by cursor, not by offset — an offset argument is rejected upstream.

### `gfwfish_events` (~292 tokens)

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.

Input parameters:

- `_apiKey` (string): Your own Global Fishing Watch API token (BYO). Get one free for non-commercial use at globalfishingwatch.org/our-apis/tokens: sign in, request an API access token, and pass it here.
- `end_date` (string, required): End date, YYYY-MM-DD.
- `event_type` (string): One of "fishing", "encounter", "loitering", "port_visit", "gap". Default "fishing".
- `limit` (number): Max events to return (1-100, default 20).
- `offset` (number): Skip this many events (default 0). Events page by offset; the response returns next_offset.
- `start_date` (string, required): Start date, YYYY-MM-DD.
- `vessel_id` (string): GFW vessel id from gfwfish_vessels_search (comma-separate for several). Omit to search all vessels in the window.

### `gfwfish_4wings_report` (~443 tokens)

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.

Input parameters:

- `_apiKey` (string): Your own Global Fishing Watch API token (BYO). Get one free for non-commercial use at globalfishingwatch.org/our-apis/tokens: sign in, request an API access token, and pass it here.
- `bbox` (string): Bounding box as "minLon,minLat,maxLon,maxLat" in WGS84, e.g. "-80,-10,-70,0". Required unless you pass region_id instead.
- `datasets` (string): Comma-separated GFW effort datasets. Default "public-global-fishing-effort:latest".
- `end_date` (string, required): End date, YYYY-MM-DD.
- `filters` (string): Comma-separated upstream filter expressions, e.g. "geartype in ('trawlers')".
- `group_by` (string): One of "FLAG", "GEARTYPE", "VESSEL_ID", "FLAGANDGEARTYPE", "MMSI". Default "FLAG".
- `region_dataset` (string): Which region dataset region_id belongs to. Default "public-eez-areas"; also "public-mpa-all" and "public-rfmo".
- `region_id` (string): A named GFW region id instead of a bbox — e.g. an EEZ id such as "8371". Takes precedence over bbox.
- `spatial_resolution` (string): One of "LOW" (0.1 degree) or "HIGH" (0.01 degree). Default "LOW".
- `start_date` (string, required): Start date, YYYY-MM-DD.
- `temporal_resolution` (string): One of "HOURLY", "DAILY", "MONTHLY", "YEARLY", "ENTIRE". Default "ENTIRE".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-global-fishing-watch/pipeworx-mcp-global-fishing-watch#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 64
- 2026-11-01: 79
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 77

## Common questions

### What is the Global Fishing Watch MCP server?

Global Fishing Watch is an MCP server listed in the public MCP registry as io.github.pipeworx-io/global-fishing-watch. Global Fishing Watch, AIS-derived fishing vessel identity, at-sea events (apparent fishing… This page covers its npm package (@pipeworx/mcp-global-fishing-watch).

### Is the Global Fishing Watch MCP server safe to use?

Global Fishing Watch scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Global Fishing Watch MCP server expose?

Global Fishing Watch exposes 3 tools: gfwfish_vessels_search, gfwfish_events, gfwfish_4wings_report. Their descriptions and schemas cost roughly 1,027 tokens of context every time the server is loaded.

### Is the Global Fishing Watch MCP server still maintained?

Global Fishing Watch is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Global Fishing Watch MCP server under?

Global Fishing Watch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-global-fishing-watch
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-global-fishing-watch
- Repository: https://github.com/pipeworx-io/mcp-global-fishing-watch
- Website: https://pipeworx.io/packs/global-fishing-watch
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-global-fishing-watch/pipeworx-mcp-global-fishing-watch.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-global-fishing-watch/pipeworx-mcp-global-fishing-watch.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-global-fishing-watch/pipeworx-mcp-global-fishing-watch