mcp-hkex-filing
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SQLITE_PATH | No | Path to SQLite database file (used when sqlite is in DATABASE_TARGET). | |
| POSTGRES_DSN | No | PostgreSQL connection string (used when postgres is in DATABASE_TARGET). | |
| DATABASE_TARGET | Yes | Ordered, comma-separated list of sink ids; order decides which sink serves reads. Valid ids: postgres, mysql, sqlite, mongodb, mariadb, neo4j, clickhouse, duckdb, surrealdb. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_server_infoA | Use this first to learn the server version, configured sinks, and read sink. Use include="config" for the raw configuration values or list_sinks for per-sink detail.
|
| list_sinksA | Use this when the user asks which databases are configured or their capabilities. Use get_server_info (with include="config") for the raw DATABASE_TARGET string or a
one-line summary instead. Pass |
| describe_schemaA | Use this before filtering or interpreting results to learn the canonical fields. Use search_filings or search_documents to query filings once you know the field names.
Pass |
| list_companiesA | Use this to list companies, or just their ticker codes, that have filings.
|
| search_filingsA | Use this to find filings by ticker, type, status, date range, or title text. Prefer search_documents for full-text search over extracted text, and get_filing or
get_filings to read filings whose ids you already have. Filters are optional and
combinable; comma-separate a value to match several (e.g. |
| search_documentsA | Use this for full-text search over extracted document text. Use search_filings instead to filter by metadata without a text query. Matches
|
| get_statisticsA | Use this to count filings grouped by one dimension, or per sink. Choose between: this tool gives a grouped breakdown of one population (or per-sink totals
when |
| get_filingA | Use this to read one filing's metadata and extracted document content. Returns the canonical filing and document fields. |
| get_filingsA | Use this to read several filings in one call (up to 50 ids). Use get_filing instead to read a single filing. Returns each filing's metadata plus,
when |
| get_coverageA | Use this to report scrape coverage per monthly chunk, with totals. Use get_statistics for filing counts grouped by a dimension, or verify_sinks for cross-sink
comparison. |
| verify_sinksA | Use this to check that configured sinks agree on their filings.
|
| list_referencesA | Use this to explore the graph edges between companies and filings. Use search_filings(ticker=...) for a company's own filings or search_filings(
referenced_ticker=...) to find mentions via the filing column. This reads the canonical
edge tables keyed on |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| schema_resource | |
| coverage_resource |
TDQS
Scored across 12 tools
Most tools are clearly separated by resource and action, and descriptions explicitly cross-reference alternatives. The main overlap is list_sinks versus get_server_info(include="sinks"), which return the same payload; get_server_info also overlaps with describe_schema and the sink-listing behavior.
All tool names use consistent snake_case verb_noun patterns (list_sinks, get_statistics, search_filings, get_filing, verify_sinks, etc.). Singular/plural distinctions like get_filing vs get_filings are handled cleanly and predictably.
Twelve tools is well-scoped for a filing-data server covering discovery, search, retrieval, statistics, coverage, sink verification, and references. Each tool has an apparent role, and the set avoids both thinness and bloat.
For a read-only HKEX filing server, the surface covers the full exploration lifecycle: schema discovery, sink inspection, company lookup, metadata search, full-text search, single/bulk filing retrieval, statistics, coverage checks, sink parity, and graph references. No obvious core read operation is missing.