Remote MCP · Endpoint

Digitalnz MCP server

No. Digitalnz answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://gateway.pipeworx.io/digitalnz/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/digitalnz
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
233 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
DigitalNZ MCP.
Listing
From the official MCP registry (active).
Recent checks of Digitalnz
CheckedResultHandshake
9 hours agoHandshake completed233 ms
1 day agoHandshake completed181 ms
3 days agoHandshake completed144 ms
3 days agoHandshake completed316 ms
4 days agoHandshake completed103 ms
6 days agoHandshake completed332 ms
8 days agoHandshake completed75 ms
10 days agoHandshake completed85 ms
13 days agoHandshake completed241 ms
15 days agoHandshake completed126 ms
17 days agoHandshake completed65 ms
19 days agoHandshake completed77 ms
21 days agoHandshake completed48 ms
23 days agoHandshake completed55 ms
25 days agoHandshake completed56 ms
27 days agoHandshake completed116 ms
28 days agoHandshake completed45 ms
29 days agoHandshake completed44 ms

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

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 Digitalnz and makes no claim about it beyond what these checks measured.