Global Fishing Watch
NPM · @PIPEWORX/MCP-GLOBAL-FISHING-WATCH · 2 COMPONENTS
Global Fishing Watch — AIS-derived fishing vessel identity, at-sea events (apparent fishing…
Available components
Last scanned (22 hours ago)
Scores higher than 65% of npm servers
Category Maps and Location
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-global-fishing-watch). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability55
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 +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.
- 30 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 77
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/@pipeworx/mcp-global-fishing-watch@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-global-fishing-watch |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-global-fishing-watch/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637325566 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7562972b2fa9d55d91dceb9be0b9718b61ca5214c8264c454fb61dee0c8ac1696fd67aac52e8786381e785c03bc782aac9e67a23e693a88d894f7ea2f |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
gfwfish_4wings_report ~443
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | 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 | yes | Start date, YYYY-MM-DD. |
| temporal_resolution | string | – | One of "HOURLY", "DAILY", "MONTHLY", "YEARLY", "ENTIRE". Default "ENTIRE". |
No output schema declared.
No examples provided.
gfwfish_events ~292
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
gfwfish_vessels_search ~292
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | 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. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-global-fishing-watch
claude mcp add pipeworx-io-global-fishing-watch -- npx -y @pipeworx/mcp-global-fishing-watch
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 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 4 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.