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.
      1
      MIT
    • io.github.akfamily/aktools by akfamily

      io.github.akfamily/aktoolsofficial

      akfamily
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants such as Claude and Cursor to search AKShare financial data interfaces, inspect their parameters, and retrieve financial data through natural-language requests.
      3
      754 PyPI
      1,503
      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
    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/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct role in a clear discovery-to-invocation pipeline: search finds candidate interfaces, describe confirms metadata, and call executes. The descriptions explicitly state ordering and boundaries, leaving no overlapping purpose.

    Naming Consistency5/5

    All tools follow a consistent akbridge_ prefix plus a concise verb/noun pattern: search, describe, call. The convention is predictable and easy to scan.

    Tool Count5/5

    Three tools are tightly scoped to the server's purpose of safely resolving and calling AKShare interfaces. Each tool earns its place, and adding more would likely add confusion rather than capability.

    Completeness4/5

    The surface covers the key lifecycle: discover via search, verify via describe, and execute via call. Minor gaps exist, such as no explicit browse/list-all or batch-invocation operation, but agents can work around these through search.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources