Remote MCP · Endpoint

AStockEvent MCP server

No. AStockEvent answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://astockevent.com/mcp/

The last check completed an MCP handshake.

Registry name
com.astockevent/astockevent
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.04 s
Tools exposed
9 tools
Uptime, last 30 days
61.5% from 13 checks
Described by its publisher as
A-share filings: reductions, penalties, regulatory letters and stock halts. Source-linked facts.
Listing
From the official MCP registry (active).
Recent checks of AStockEvent
CheckedResultHandshake
5 hours agoHandshake completed1.04 s
3 days agoHandshake completed903 ms
12 days agoHandshake completed661 ms
12 days agoHandshake completed641 ms
14 days agoHandshake completed669 ms
15 days agoFailed - the server returned an HTTP error—
16 days agoFailed - the server returned an HTTP error—
17 days agoFailed - the server returned an HTTP error—
18 days agoFailed - the server returned an HTTP error—
19 days agoFailed - the server returned an HTTP error—
22 days agoHandshake completed658 ms
25 days agoHandshake completed661 ms
27 days agoHandshake completed740 ms

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

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