Remote MCP · Endpoint

China Stocks MCP server

No. China Stocks answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/china-stocks
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
49 ms
Tools exposed
54 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
China A-shares MCP. Keyless.
Listing
From the official MCP registry (active).
Recent checks of China Stocks
CheckedResultHandshake
1 day agoHandshake completed49 ms
3 days agoHandshake completed78 ms
5 days agoHandshake completed293 ms
7 days agoHandshake completed66 ms
8 days agoHandshake completed70 ms
9 days agoHandshake completed41 ms
12 days agoHandshake completed40 ms
13 days agoHandshake completed37 ms
15 days agoHandshake completed51 ms
16 days agoHandshake completed44 ms
18 days agoHandshake completed46 ms
19 days agoHandshake completed40 ms
20 days agoHandshake completed54 ms
20 days agoHandshake completed38 ms
21 days agoHandshake completed197 ms
22 days agoHandshake completed40 ms

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 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 China Stocks and makes no claim about it beyond what these checks measured.