Remote MCP · Endpoint

Data Govt Nz MCP server

No. Data Govt Nz answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/data-govt-nz/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/data-govt-nz
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
229 ms
Tools exposed
55 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
data.govt.nz CKAN MCP.
Listing
From the official MCP registry (active).
Recent checks of Data Govt Nz
CheckedResultHandshake
1 hour agoHandshake completed229 ms
1 day agoHandshake completed73 ms
2 days agoHandshake completed192 ms
3 days agoHandshake completed112 ms
4 days agoHandshake completed102 ms
5 days agoHandshake completed95 ms
6 days agoHandshake completed237 ms
8 days agoHandshake completed139 ms
11 days agoHandshake completed89 ms
13 days agoHandshake completed81 ms
16 days agoHandshake completed84 ms
18 days agoHandshake completed79 ms
20 days agoHandshake completed71 ms
22 days agoHandshake completed70 ms
24 days agoHandshake completed80 ms
26 days agoHandshake completed50 ms
27 days agoHandshake completed73 ms
29 days agoHandshake completed68 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 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 Data Govt Nz and makes no claim about it beyond what these checks measured.