Remote MCP · Endpoint

China Exchange Data MCP server

No. China Exchange Data answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://gateway.pipeworx.io/china-exchange-data/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/china-exchange-data
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
53 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
China Exchange Data MCP (SZSE + SSE). Keyless.
Listing
From the official MCP registry (active).
Recent checks of China Exchange Data
CheckedResultHandshake
2 days agoHandshake completed53 ms
4 days agoHandshake completed60 ms
5 days agoHandshake completed46 ms
7 days agoHandshake completed100 ms
8 days agoHandshake completed51 ms
9 days agoHandshake completed37 ms
12 days agoHandshake completed43 ms
13 days agoHandshake completed41 ms
15 days agoHandshake completed53 ms
16 days agoHandshake completed56 ms
18 days agoHandshake completed39 ms
19 days agoHandshake completed49 ms
20 days agoHandshake completed45 ms
20 days agoHandshake completed43 ms
21 days agoHandshake completed46 ms
23 days agoHandshake completed57 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 Exchange Data and makes no claim about it beyond what these checks measured.