HKEx Filings
REMOTE · HKEX-LISTCO-UPDATES.ASCENT-PARTNERS.COM · 2 COMPONENTS · SCANNED SEP 21
Live HKEx (Hong Kong Stock Exchange) regulatory filings for AI agents.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 385 tokens (~128/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the HKEx Filings MCP server?
HKEx Filings is a hosted endpoint at https://hkex-listco-updates.ascent-partners.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · hkex-listco-updates.ascent-partners.com
claude mcp add --transport http simonplmak-cloud-hkex-filings 'https://hkex-listco-updates.ascent-partners.com/api/mcp'
{
"mcpServers": {
"simonplmak-cloud-hkex-filings": {
"url": "https://hkex-listco-updates.ascent-partners.com/api/mcp"
}
}
} {
"servers": {
"simonplmak-cloud-hkex-filings": {
"type": "http",
"url": "https://hkex-listco-updates.ascent-partners.com/api/mcp"
}
}
} [mcp_servers.simonplmak-cloud-hkex-filings] url = "https://hkex-listco-updates.ascent-partners.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"simonplmak-cloud-hkex-filings": {
"type": "remote",
"url": "https://hkex-listco-updates.ascent-partners.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add simonplmak-cloud-hkex-filings --url 'https://hkex-listco-updates.ascent-partners.com/api/mcp' --transport streamable-http
mcp_servers:
simonplmak-cloud-hkex-filings:
url: "https://hkex-listco-updates.ascent-partners.com/api/mcp" {
"McpServers": {
"simonplmak-cloud-hkex-filings": {
"Transport": "http",
"Url": "https://hkex-listco-updates.ascent-partners.com/api/mcp"
}
}
} assistant mcp add simonplmak-cloud-hkex-filings -t streamable-http -u 'https://hkex-listco-updates.ascent-partners.com/api/mcp'
{
"mcpServers": {
"simonplmak-cloud-hkex-filings": {
"type": "http",
"url": "https://hkex-listco-updates.ascent-partners.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 20 Sept 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://hkex-listco-updates.ascent-partners.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.ascent-partners.com | CN=YR2,O=Let's Encrypt,C=US | 18 Aug 2026 | 16 Nov 2026 | RSA 2048 | SHA256-RSA | 60ef6c381e1a219e6810dd52f2158edca94 |
| SANs: *.ascent-partners.com, ascent-partners.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hkex-listco-updates.ascent-partners.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ascent-partners.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hkex-listco-updates.ascent-partners.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://hkex-listco-updates.ascent-partners.com/api/mcp | HTTPS enforced | 308 | https://hkex-listco-updates.ascent-partners.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_filing ~116
Download one HKEx document by its URL and extract its text and tables. ``link`` must be an HKEx document URL (host ``www1.hkexnews.hk``); any other host is rejected. With ``extract=True`` the response includes extracted ``document_text`` (truncated) and up to 30 ``tables``; set ``extract=False`` for size/content-type only.
| Name | Type | Req | Description |
|---|---|---|---|
| extract | boolean | – | Extract text and tables |
| link | string | yes | HKEx document URL |
No output schema declared.
No examples provided.
get_server_info ~25
Report this live gateway's version, transport, and hard limits. Reads nothing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_filings ~162
Search live HKEx filings in a date window (at most 31 days). ``from_date``/``to_date`` accept YYYY-MM-DD or DD/MM/YYYY. When ``stock_code`` is set, results are filtered to that code (e.g. ``01461`` or ``1461``). ``max_results`` caps the number of filings fetched and returned (hard cap 200). Returns the parsed filings plus the HKEx-reported total for the window.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | yes | YYYY-MM-DD or DD/MM/YYYY |
| max_results | integer | – | – |
| stock_code | string | – | Optional HKEx stock code |
| to_date | string | yes | YYYY-MM-DD or DD/MM/YYYY |
No output schema declared.
No examples provided.
What is the HKEx Filings MCP server?
HKEx Filings is an MCP server listed in the public MCP registry as io.github.simonplmak-cloud/hkex-filings. Live HKEx (Hong Kong Stock Exchange) regulatory filings for AI agents. This page covers its hosted endpoint (https://hkex-listco-updates.ascent-partners.com/api/mcp).
Is the HKEx Filings MCP server safe to use?
HKEx Filings scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the HKEx Filings MCP server expose?
HKEx Filings exposes 3 tools: get_server_info, search_filings, get_filing. Their descriptions and schemas cost roughly 303 tokens of context every time the server is loaded.
Does the HKEx Filings MCP server require authentication?
No. We connected to HKEx Filings without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HKEx Filings MCP server still maintained?
HKEx Filings is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.