Remote MCP · Endpoint

Who Euro MCP server

No. Who Euro answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://gateway.pipeworx.io/who-euro/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/who-euro
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
59 ms
Tools exposed
Not measured yet
Uptime, last 30 days
87.5% from 16 checks
Described by its publisher as
WHO Regional Office for Europe — Data Warehouse API v5.
Listing
From the official MCP registry (active).
Recent checks of Who Euro
CheckedResultHandshake
2 days agoHandshake completed59 ms
4 days agoFailed - the request timed out—
5 days agoHandshake completed54 ms
7 days agoHandshake completed65 ms
8 days agoHandshake completed213 ms
9 days agoFailed - the request timed out—
12 days agoHandshake completed48 ms
13 days agoHandshake completed42 ms
15 days agoHandshake completed51 ms
17 days agoHandshake completed71 ms
18 days agoHandshake completed37 ms
19 days agoHandshake completed44 ms
20 days agoHandshake completed56 ms
20 days agoHandshake completed38 ms
21 days agoHandshake completed35 ms
23 days agoHandshake completed71 ms

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

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