Global Forest Watch
NPM · @PIPEWORX/MCP-GLOBAL-FOREST-WATCH · 2 COMPONENTS
The Global Forest Watch Data API from WRI and the University of Maryland — browse the datasets…
Available components
Last scanned (4 hours ago)
Scores higher than 72% of npm servers
Category Health and Science
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-forest-watch). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 878 tokens (~292/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 Management23
- Stability observed for 7 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.
- 5 Nov 26 +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.
- 4 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 78
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-global-forest-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-forest-watch |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-global-forest-watch/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637326350 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:34ddfdd411a125998d1e85b6170c60ffebf6427362d94cd8a6a4e8c69add0976e9c4d9558cb63105bae8d2e84b4d8390f02f1644f80cb9f0b1ca43ccb |
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 →
gfw_dataset ~136
Full detail for ONE Global Forest Watch dataset — metadata (source, citation, spatial resolution, geographic coverage, update frequency, cautions, licence) plus its version list. Pass a version (or "latest") to also get that version's status, assets and field/band list, which is what gfw_query needs to build a valid SQL statement. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | Dataset name from gfw_datasets, e.g. "umd_tree_cover_loss". |
| version | string | – | Optional version, e.g. "latest" or "v1.13". Omit for dataset-level metadata only. |
No output schema declared.
No examples provided.
gfw_datasets ~195
List or keyword-search the Global Forest Watch Data API catalogue — the WRI/UMD datasets behind GFW: annual tree cover loss and gain, primary forest extent, GLAD/RADD deforestation alerts, fire alerts (VIIRS/MODIS), protected areas, concessions, Aqueduct water risk, carbon flux. Returns each dataset name (pass it to gfw_dataset or gfw_query), its title, tags and published versions. Keyless. AUTHORITATIVE for what forest-change data GFW actually publishes.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max datasets to return (1-200, default 25). |
| page | number | – | Upstream page number, 1-based (default 1). Each upstream page holds up to 100 datasets. |
| query | string | – | Optional keyword filter, matched against dataset name, title and tags (e.g. "tree cover loss", "fire", "peat"). |
No output schema declared.
No examples provided.
gfw_query ~491
Run a read-only SQL SELECT against one Global Forest Watch dataset version — e.g. tree cover loss hectares by year inside an area, or deforestation alerts inside a bounding box. The table is always called `data`; use gfw_dataset to see the available columns first. Almost every GFW dataset (tree cover loss/gain, GLAD/RADD alerts, fire alerts, carbon, primary forest) is a RASTER TILE SET, not a plain table — a `geometry` (GeoJSON Polygon/MultiPolygon) is REQUIRED to scope the pixels queried, or the API answers 422 "Raster tile set queries require a geometry". Omit it only for the few vector-table datasets (e.g. wdpa_protected_areas). Requires your own free GFW API key, passed as _apiKey.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your own Global Forest Watch API key (BYO). Get one free at globalforestwatch.org: create an account, then POST /auth/token followed by POST /auth/apikey on data-api.globalforestwatch.org to mint an… |
| dataset | string | yes | Dataset name, e.g. "umd_tree_cover_loss". |
| geometry | object | – | GeoJSON Polygon or MultiPolygon ({"type":"Polygon","coordinates":[...]}) scoping the query spatially. REQUIRED for raster tile set datasets — which is most of them; see gfw_dataset's version_assets.… |
| limit | number | – | Row cap appended when your SQL has no LIMIT (1-1000, default 100). |
| sql | string | yes | A SELECT statement over the table `data`, e.g. "SELECT umd_tree_cover_loss__year, SUM(area__ha) AS loss_ha FROM data WHERE umd_tree_cover_loss__year > 0 GROUP BY umd_tree_cover_loss__year". SELECT on… |
| version | string | – | Version, e.g. "latest" or "v1.13". Default "latest". |
No output schema declared.
No examples provided.
How do I install the Global Forest Watch MCP server?
Global Forest Watch runs locally as an npm package, launched with npx -y @pipeworx/mcp-global-forest-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-forest-watch
claude mcp add pipeworx-io-global-forest-watch -- npx -y @pipeworx/mcp-global-forest-watch
What is the Global Forest Watch MCP server?
Global Forest Watch is an MCP server listed in the public MCP registry as io.github.pipeworx-io/global-forest-watch. The Global Forest Watch Data API from WRI and the University of Maryland, browse the datasets… This page covers its npm package (@pipeworx/mcp-global-forest-watch).
Is the Global Forest Watch MCP server safe to use?
Global Forest Watch scores 82 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 Forest Watch MCP server expose?
Global Forest Watch exposes 3 tools: gfw_datasets, gfw_dataset, gfw_query. Their descriptions and schemas cost roughly 822 tokens of context every time the server is loaded.
Is the Global Forest Watch MCP server still maintained?
Global Forest 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 Forest Watch MCP server under?
Global Forest 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.