Remote MCP · Endpoint

Geonet Nz MCP server

No. Geonet Nz answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://gateway.pipeworx.io/geonet-nz/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/geonet-nz
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
210 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
GeoNet New Zealand MCP.
Listing
From the official MCP registry (active).
Recent checks of Geonet Nz
CheckedResultHandshake
2 hours agoHandshake completed210 ms
23 hours agoHandshake completed83 ms
2 days agoHandshake completed167 ms
3 days agoHandshake completed184 ms
4 days agoHandshake completed96 ms
5 days agoHandshake completed112 ms
6 days agoHandshake completed273 ms
8 days agoHandshake completed114 ms
11 days agoHandshake completed129 ms
13 days agoHandshake completed137 ms
16 days agoHandshake completed105 ms
18 days agoHandshake completed99 ms
20 days agoHandshake completed82 ms
22 days agoHandshake completed60 ms
24 days agoHandshake completed55 ms
26 days agoHandshake completed58 ms
27 days agoHandshake completed68 ms
29 days agoHandshake completed54 ms

The last 18 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 Geonet Nz and makes no claim about it beyond what these checks measured.