Remote MCP · Endpoint

Sdmx Structure MCP server

No. Sdmx Structure answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/sdmx-structure/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/sdmx-structure
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
122 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
SDMX Structure MCP — dataflow dimensions and code lists for any SDMX 2.1 registry: Eurostat, OECD…
Listing
From the official MCP registry (active).
Recent checks of Sdmx Structure
CheckedResultHandshake
1 hour agoHandshake completed122 ms
22 hours agoHandshake completed166 ms
1 day agoHandshake completed125 ms
2 days agoHandshake completed124 ms
4 days agoHandshake completed120 ms
7 days agoHandshake completed58 ms
9 days agoHandshake completed288 ms
12 days agoHandshake completed78 ms
14 days agoHandshake completed105 ms
16 days agoHandshake completed1.03 s
18 days agoHandshake completed2.10 s
20 days agoHandshake completed1.37 s
22 days agoHandshake completed91 ms
24 days agoHandshake completed62 ms

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

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