Remote MCP · Endpoint

Global Forest Watch MCP server

No. Global Forest Watch answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://gateway.pipeworx.io/global-forest-watch/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/global-forest-watch
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
71 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
The Global Forest Watch Data API from WRI and the University of Maryland — browse the datasets…
Listing
From the official MCP registry (active).
Recent checks of Global Forest Watch
CheckedResultHandshake
42 minutes agoHandshake completed71 ms
9 days agoHandshake completed132 ms
10 days agoHandshake completed260 ms
11 days agoHandshake completed109 ms
12 days agoHandshake completed54 ms
14 days agoHandshake completed154 ms
15 days agoHandshake completed98 ms
15 days agoHandshake completed168 ms
17 days agoHandshake completed204 ms
19 days agoHandshake completed66 ms
22 days agoHandshake completed88 ms
24 days agoHandshake completed94 ms
26 days agoHandshake completed113 ms
28 days agoHandshake completed120 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Global Forest Watch and makes no claim about it beyond what these checks measured.