Remote MCP · Endpoint

Who Ictrp MCP server

No. Who Ictrp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/who-ictrp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
192 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
WHO ICTRP — the International Clinical Trials Registry Platform search portal…
Listing
From the official MCP registry (active).
Recent checks of Who Ictrp
CheckedResultHandshake
1 hour agoHandshake completed192 ms
1 day agoHandshake completed122 ms
2 days agoHandshake completed106 ms
2 days agoHandshake completed60 ms
4 days agoHandshake completed225 ms
6 days agoHandshake completed67 ms
9 days agoHandshake completed59 ms
11 days agoHandshake completed417 ms
14 days agoHandshake completed59 ms
16 days agoHandshake completed61 ms
18 days agoHandshake completed404 ms
20 days agoHandshake completed63 ms
22 days agoHandshake completed74 ms
24 days agoHandshake completed93 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 Who Ictrp and makes no claim about it beyond what these checks measured.