Remote MCP · Endpoint

WalnutLink A-share Depth Desk MCP server

No. WalnutLink A-share Depth Desk answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://walnutlink.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.walnutlink/walnutlink-a-share
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
468 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
China A-share filings: why a number moved, does the trend continue, who supplies whom.
Listing
From the official MCP registry (active).
Recent checks of WalnutLink A-share Depth Desk
CheckedResultHandshake
1 hour agoHandshake completed468 ms
3 days agoHandshake completed453 ms
13 days agoHandshake completed449 ms
14 days agoHandshake completed728 ms
15 days agoHandshake completed436 ms
16 days agoHandshake completed441 ms
18 days agoHandshake completed606 ms
18 days agoHandshake completed412 ms
19 days agoHandshake completed449 ms
21 days agoHandshake completed461 ms
22 days agoHandshake completed486 ms
25 days agoHandshake completed758 ms

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

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 WalnutLink A-share Depth Desk and makes no claim about it beyond what these checks measured.