Skip to main content
Glama
simonplmak-cloud

mcp-hkex-filing

by simonplmak-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp-hkex-filing

No user-submitted related servers found.

    Related Servers

    • MCP Knowledge Assistant

      channico
      F
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that enables AI clients to search a knowledge base and retrieve complete source documents via narrow search and fetch tools.
      2
      -

    • local-tools-mcp-server

      fenhuayue
      F
      license
      A
      quality
      C
      maintenance
      A read-only MCP server that enables AI assistants to search files, list directories, retrieve system info, and get file metadata on the local file system.
      4
      -

    • provgraf-mcp

      Inarus
      A
      license
      A
      quality
      C
      maintenance
      Read-only MCP server exposing a W3C PROV knowledge graph of verified facts with provenance, enabling AI agents to list, search, and check facts while enforcing that writes remain CLI-only.
      5
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 16 tools

    Disambiguation3/5

    Most tools have distinct purposes, but several boundaries blur: get_config, get_server_info, and list_sinks all describe configured sinks, while count_filings and get_statistics both provide counts. list_tickers/list_companies and search_filings/list_pending_filings also overlap, though the descriptions provide enough context to disambiguate with care.

    Naming Consistency5/5

    All names follow a consistent lowercase snake_case verb_noun pattern (describe_, count_, list_, get_, search_, verify_). The semantic mapping of verbs is coherent: list for enumerations, get for retrieval, search for filtered lookup, count for totals. The singular/plural pair get_filing/get_filings is handled predictably.

    Tool Count4/5

    At 16 tools, the surface is just at the upper boundary, but the extra tools are mostly administration/verification functions (coverage, parity, sinks, config) that serve a distinct operational purpose. It is slightly heavy for a read-only filing server but remains reasonable.

    Completeness4/5

    The core filing workflow is well covered: schema discovery, metadata search, full-text search, single and batch retrieval, and pending/status listing. Minor gaps exist, such as no obvious way to combine full-text search with metadata filters and graph edge kinds are mentioned but no graph query tool is exposed, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources