Skip to main content
Glama
kevynf

AKBridge MCP Server

by kevynf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to AKBridge MCP Server

No user-submitted related servers found.

    Related Servers

    • akshare-mcp

      xiaozhozho
      A
      license
      B
      quality
      D
      maintenance
      MCP server that wraps AKShare's 1000+ financial data functions, enabling LLMs to query Chinese stock, macro, futures, fund, bond, option, forex, and alternative data through standardized tools.
      14
      3
      Apache 2.0

    • ak-mcp

      Vaskka
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides access to over 1000 AKShare financial data interfaces (stocks, futures, bonds, funds, macro, and more) via MCP, with local MySQL caching for reduced latency.
      MIT

    • FinData MCP Server

      zlinzzzz
      A
      license
      A
      quality
      D
      maintenance
      Provides professional financial data access for LLMs via MCP, supporting providers like Tushare, Wind, and DataYes.
      14
      57
      Apache 2.0

    • AKShare MCP Server

      jadenmong
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to access comprehensive Chinese financial market data including stocks, funds, futures, and economic indicators via AKShare.
      5
      5
      MIT

    • a-stock-data-mcp

      droid-Q
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server adapter that exposes A-share stock data tools, prompts, and resources via FastMCP, enabling querying of stocks, K-lines, financials, sectors, and market hot spots through natural language.
      -
    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

    C2.5/5.0

    Scored across 1096 tools

    Disambiguation3/5

    With 1096 endpoints each targeting a specific data source, most tools have a distinct purpose, but there are large clusters of near-identical tools (e.g., the many macro_usa_* series, stock_zt_pool_* variants, futures_settle_* per exchange, numerous fund_* and option_* tools) where a slight name difference determines the result. Descriptions are detailed but an agent can easily misselect among similar-looking endpoints.

    Naming Consistency3/5

    The dominant pattern is snake_case source_topic_action (stock_zh_a_hist, macro_usa_cpi_monthly), but there is a significant minority of verb-first or unstructured names (get_cffex_daily, get_rank_sum, search, list_categories, interface_info, pro_api, set_token, match_main_contract). The mix of conventions makes the namespace feel less predictable than a single rule.

    Tool Count1/5

    1096 tools is an extreme over-exposure for any single server, far beyond the 3-15 range that an agent can reason about effectively. While each underlying endpoint is real, exposing them all as individual tools creates an unnavigable surface.

    Completeness4/5

    The surface covers an enormous breadth of financial domains (A/HK/US stocks, funds, bonds, futures, options, forex, macro, ESG, filings), and only a handful of tools lack descriptions. Almost any data need appears addressable, with only minor gaps like some undocumented endpoints.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources