Remote MCP · Endpoint

Hk Stocks MCP server

No. Hk Stocks answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/hk-stocks/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/hk-stocks
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
197 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Hong Kong equities MCP. Keyless.
Listing
From the official MCP registry (active).
Recent checks of Hk Stocks
CheckedResultHandshake
1 hour agoHandshake completed197 ms
22 hours agoHandshake completed125 ms
2 days agoHandshake completed178 ms
3 days agoHandshake completed234 ms
4 days agoHandshake completed97 ms
5 days agoHandshake completed256 ms
6 days agoHandshake completed188 ms
8 days agoHandshake completed137 ms
11 days agoHandshake completed82 ms
13 days agoHandshake completed76 ms
16 days agoHandshake completed464 ms
18 days agoHandshake completed56 ms
20 days agoHandshake completed66 ms
22 days agoHandshake completed190 ms
24 days agoHandshake completed54 ms
26 days agoHandshake completed53 ms
27 days agoHandshake completed56 ms
29 days agoHandshake completed58 ms

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

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