Remote MCP · Endpoint

Un Sdg MCP server

No. Un Sdg answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/un-sdg/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/un-sdg
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
76 ms
Tools exposed
41 tools
Uptime, last 30 days
88.2% from 17 checks
Described by its publisher as
UN Sustainable Development Goals (SDG) Indicators MCP — UN Statistics Division.
Listing
From the official MCP registry (active).
Recent checks of Un Sdg
CheckedResultHandshake
1 hour agoHandshake completed76 ms
2 days agoHandshake completed66 ms
4 days agoFailed - the request timed out—
6 days agoHandshake completed56 ms
7 days agoHandshake completed73 ms
8 days agoHandshake completed76 ms
9 days agoHandshake completed55 ms
12 days agoFailed - the request timed out—
14 days agoHandshake completed328 ms
15 days agoHandshake completed78 ms
17 days agoHandshake completed42 ms
18 days agoHandshake completed47 ms
19 days agoHandshake completed41 ms
20 days agoHandshake completed48 ms
21 days agoHandshake completed37 ms
22 days agoHandshake completed59 ms
23 days agoHandshake completed61 ms

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

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