HKEx Filings
REMOTE · HKEX-LISTCO-UPDATES.ASCENT-PARTNERS.COM · 2 COMPONENTS
Live HKEx (Hong Kong Stock Exchange) regulatory filings for AI agents.
Available components
Last scanned (18 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Finance and Payments
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1024 tokens (~256/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 16 Oct 26 +3
- HSTS header: fail → pass ▲ security
- Server version: 0.0.1.dev1+g01597174e → 0.0.1.dev1+g7d3e0144b functional
- 15 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 14 Oct 26 70
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 16 Oct 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=YE2,O=Let's Encrypt,C=US | 13 Oct 2026 | 11 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5022c93727c48b52a7127597de7a37383be |
| SANs: *.ascent-partners.com, ascent-partners.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
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=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
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 Read HKEx Filing ~296
Download one HKEx document by its URL and read, page through, or search its text. ``link`` must be an HKEx document URL from search_filings (host ``www1.hkexnews.hk``); any other host is rejected. With ``extract=True`` (default) the response includes up to 30 ``tables`` and a window of extracted ``document_text``: ``max_chars`` characters starting at ``offset``. Long reports return ``next_offset``; call again with it to read the next window. Pass ``query`` to search the whole document instead: the response then lists up to 20 case-insensitive matches with their offsets and surrounding text, plus ``match_count`` — use a match offset to read that part. Set ``extract=False`` for size and content type only.
| Name | Type | Req | Description |
|---|---|---|---|
| extract | boolean | – | Extract text and tables; false returns size and content type only |
| link | string | yes | HKEx document URL from a search_filings result (host www1.hkexnews.hk) |
| max_chars | integer | – | Maximum characters of document_text to return in this window |
| offset | integer | – | Character offset where the returned text window starts (use next_offset to page) |
| query | string | – | Optional text to find in the whole document; returns matches with offsets instead of a text window |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | The downloaded document, with text and tables when extract is true. |
No examples provided.
get_server_info Gateway Info ~25
Report this live gateway's version, transport, and hard limits. Reads nothing.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | Gateway version, transport, tool list, filters, and hard limits. |
No examples provided.
list_filing_facets Browse Filing Facets ~195
Browse what filings exist in a date window (at most 31 days) without downloading. ``from_date``/``to_date`` accept YYYY-MM-DD or DD/MM/YYYY. Returns counts of the categories (headline categories), document types, and stock codes present in the window, each sorted by frequency and capped at 50 values, plus the distinct counts. Optionally narrow to one ``stock_code``. Use this to discover valid filter values before calling search_filings; it fetches the window once and extracts no document text.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | yes | YYYY-MM-DD or DD/MM/YYYY |
| max_results | integer | – | Maximum filings to scan (default 50, cap 200) |
| stock_code | string | – | Optional exact HKEx stock code to narrow the facets |
| to_date | string | yes | YYYY-MM-DD or DD/MM/YYYY |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | Counts of the window's categories, document types, and stock codes. |
No examples provided.
search_filings Search HKEx Filings ~380
Search live HKEx filings in a date window (at most 31 days). ``from_date``/``to_date`` accept YYYY-MM-DD or DD/MM/YYYY. All filters are optional and combine with AND semantics: ``stock_code`` matches exactly (e.g. ``01461`` or ``1461``); ``title_query``, ``category`` and ``stock_name`` are case-insensitive substrings (e.g. category ``Dividend``); ``document_type`` matches the file type exactly (e.g. ``PDF`` or ``HTML``). Filters are applied to the fetched window, so widen ``max_results`` to catch rarer matches. ``max_results`` caps the number of filings fetched and returned (hard cap 200). Returns the matching filings — each carrying ``fileType``, ``sizeText``, ``category`` and ``newsId`` metadata — plus the HKEx-reported total for the window. Use list_filing_facets first to see which categories, types and codes exist in a window.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional case-insensitive substring of the headline category |
| document_type | string | – | Optional exact file type, e.g. PDF, HTML, XLS, DOC |
| from_date | string | yes | YYYY-MM-DD or DD/MM/YYYY |
| max_results | integer | – | Maximum filings to fetch and return (default 50, cap 200) |
| stock_code | string | – | Optional exact HKEx stock code, e.g. 01461 |
| stock_name | string | – | Optional case-insensitive substring of the stock short name |
| title_query | string | – | Optional case-insensitive substring of the filing title |
| to_date | string | yes | YYYY-MM-DD or DD/MM/YYYY |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | The filings matching the window and filters. |
No examples provided.
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 com-ascent-partners-hkex-filings 'https://hkex-listco-updates.ascent-partners.com/api/mcp'
What is the HKEx Filings MCP server?
HKEx Filings is an MCP server listed in the public MCP registry as com.ascent-partners/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 73 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 4 tools: get_server_info, search_filings, list_filing_facets, get_filing. Their descriptions and schemas cost roughly 896 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 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.