Remote MCP · Endpoint

HKEx Filings MCP server

No. HKEx Filings answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://hkex-listco-updates.ascent-partners.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.ascent-partners/hkex-filings
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
879 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Live HKEx (Hong Kong Stock Exchange) regulatory filings for AI agents.
Listing
From the official MCP registry (active).
Recent checks of HKEx Filings
CheckedResultHandshake
13 minutes agoHandshake completed879 ms
10 days agoHandshake completed707 ms
10 days agoHandshake completed883 ms
11 days agoHandshake completed899 ms
13 days agoHandshake completed870 ms
14 days agoHandshake completed659 ms
14 days agoHandshake completed802 ms
15 days agoHandshake completed773 ms
17 days agoHandshake completed644 ms
19 days agoHandshake completed967 ms
21 days agoHandshake completed861 ms
24 days agoHandshake completed880 ms
26 days agoHandshake completed656 ms
28 days agoHandshake completed740 ms

The last 14 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 HKEx Filings and makes no claim about it beyond what these checks measured.