Remote MCP · Endpoint

Hsa Singapore MCP server

No. Hsa Singapore answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://gateway.pipeworx.io/hsa-singapore/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/hsa-singapore
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
119 ms
Tools exposed
40 tools
Uptime, last 30 days
93.3% from 15 checks
Described by its publisher as
Singapore HSA registered therapeutic products — the Health Sciences
Listing
From the official MCP registry (active).
Recent checks of Hsa Singapore
CheckedResultHandshake
1 day agoHandshake completed119 ms
3 days agoHandshake completed60 ms
5 days agoHandshake completed77 ms
7 days agoHandshake completed67 ms
9 days agoFailed - the request timed out—
11 days agoHandshake completed78 ms
12 days agoHandshake completed58 ms
14 days agoHandshake completed2.86 s
15 days agoHandshake completed83 ms
17 days agoHandshake completed39 ms
19 days agoHandshake completed42 ms
21 days agoHandshake completed82 ms
22 days agoHandshake completed46 ms
23 days agoHandshake completed55 ms
25 days agoHandshake completed2.42 s

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

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