The live MCP gateway exposes HKEx filings to MCP clients over HTTP, fetching fresh data from the HKEx website on every call. It is the hosted companion to the MCP: where that server runs over stdio and reads a stored corpus from a database sink, this gateway is stateless, stores nothing, and needs no database.

Endpoint:

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

The endpoint speaks Streamable HTTP: send POST requests carrying JSON-RPC 2.0. It is not a web page — opening the URL in a browser sends GET, which the gateway answers with 405 Method Not Allowed (the MCP specification allows this when no server-sent-events stream is offered). Cross-origin clients are supported through an OPTIONS CORS preflight and an Origin allowlist.

The gateway is the hosted, database-free half of the project. The MCP is the local half; the same client can use either.

flowchart LR
    A["AI agent<br/>Claude · ChatGPT · Cursor · Copilot<br/>Gemini · opencode · Manus · Perplexity"]
    A -->|"Streamable HTTP · no API key"| G["Live MCP gateway<br/>stateless · no database"]
    G -->|"search_filings · list_filing_facets · get_filing"| H["HKEx API + documents"]
    A -->|"stdio · hkex-scraper-mcp"| S["Read-only MCP server"]
    S --> D["Your database<br/>postgres · mysql · sqlite · mongodb<br/>mariadb · neo4j · clickhouse · duckdb · surrealdb"]
    H -.->|"pip install + scrape"| D

If the diagram does not render, it is also available as an image — the tools and limits below are the full interface.

Every tool is read-only. The gateway never writes, never runs schema DDL, and never fetches an arbitrary URL — get_filing accepts only HKEx document hosts.

search_filings narrows a window with five optional, combinable filters:

Filters combine with AND. They apply to the filings fetched for the window, so raise max_results to catch rarer matches. Each returned filing carries the fileType, sizeText, category, and newsId metadata alongside its date, stock code, stock name, title, and link. Call list_filing_facets first to see which categories, document types, and stock codes a window holds.

Search a window for one company's filings whose title mentions dividends:

curl -sS https://hkex-listco-updates.ascent-partners.com/api/mcp \
  -H "content-type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "search_filings",
      "arguments": {
        "from_date": "2026-09-01",
        "to_date": "2026-09-30",
        "stock_code": "00700",
        "title_query": "dividend"
      }
    }
  }'

Browse what a window holds before drilling in — the categories, document types, and stock codes with their counts:

curl -sS https://hkex-listco-updates.ascent-partners.com/api/mcp \
  -H "content-type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
      "name": "list_filing_facets",
      "arguments": {"from_date": "2026-09-01", "to_date": "2026-09-30"}
    }
  }'

Pass a search result's link to get_filing to download and extract that document. For a long annual report, pass query (for example "final dividend") to find the relevant passages, then read around a match with offset and max_chars.

The model cannot raise these:

The gateway speaks Streamable HTTP (stateless, JSON responses) at /api/mcp and needs no authentication. The full client list — Claude, ChatGPT, Cursor, Copilot, Gemini, opencode, Manus, and Perplexity — is in AI-Agent-Support.

opencode (opencode.json):

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hkex-live": {
      "type": "remote",
      "url": "https://hkex-listco-updates.ascent-partners.com/api/mcp",
      "enabled": true
    }
  }
}

Claude — add it as a custom connector pointing at the endpoint URL, choosing "no authentication".

Cursor (~/.cursor/mcp.json):

{
  "mcpServers": {
      "hkex-live": {
        "url": "https://hkex-listco-updates.ascent-partners.com/api/mcp"
      }
  }
}

The gateway is a deliberately public, read-only API over public filings data. Its controls are:

• Read-only by construction — four read tools; no write, SQL, or arbitrary-fetch surface.
• SSRF allowlist — documents are fetched only from HKEx hosts (www1.hkexnews.hk).
• Origin validation — requests carrying a disallowed Origin are rejected (MCP's DNS-rebinding mitigation).
• No caching — responses are sent with Cache-Control: no-store.
• Rate limiting — a Vercel Firewall rule limits /api/mcp to 120 requests per 60 seconds per IP; excess requests are answered with 429 Too Many Requests.
• Liveness — GET /api/healthz returns {"ok":true} and reads nothing.
• Bounded responses — the limits above keep every response well within the platform body limit.

The gateway is a single Python function on Vercel, deployed from this repository alongside the documentation site. The transport is implemented directly in src/hkex_scraper/live_mcp.py (it needs no server SDK and no ASGI lifespan), and the Vercel entry point is api/mcp.py.

The project is linked to GitHub, so deployment is automatic: pushes to main deploy to production (https://hkex-listco-updates.ascent-partners.com/), and every other branch or pull request deploys an isolated preview. The function runs in the Hong Kong region (hkg1) with a Singapore failover (sin1), and it is configured with Fluid compute so document extraction can run within the function's execution budget.

The document-extraction libraries (PyMuPDF, pymupdf4llm, openpyxl) are AGPL-3.0, so they are not published dependencies of the distribution (see Legal); the deployment installs them through the deploy dependency group in pyproject.toml. pymupdf4llm is pinned to a release that depends only on PyMuPDF — its 1.x line pulls an additional layout model (onnxruntime and numpy) that exceeds the serverless bundle limit.

• AI-Agent-Support — configuration for Claude, ChatGPT, Cursor, Copilot, Gemini, opencode, Manus, and Perplexity.
• MCP — the stdio server over a stored corpus.
• Configuration — environment variables for the CLI and sinks.

Home