Skip to main content
Glama
openbot-coder

quantdb-mcp

by openbot-coder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to quantdb-mcp

No user-submitted related servers found.

    Related Servers

    • dsh-quant-data-mcp

      helibeiqi
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server providing A-share market data tools (daily OHLCV, real-time quotes, financials, northbound capital flow, sector lists) with zero dependencies, also serving as a template for building custom MCP servers.
      2
      MIT

    • stock-mcp

      jamespud
      A
      license
      B
      quality
      B
      maintenance
      MCP server that syncs and queries comprehensive stock data (quotes, financials, dividends, analyst forecasts, options, news) from Yahoo Finance and Investing.com into an external MySQL database.
      2
      27
      213 npm
      MIT

    • ashare-mcp

      lolifamily
      A
      license
      A
      quality
      B
      maintenance
      A-share market data MCP server via baostock. Full-stack coverage: K-line, financials, DCF/DDM/PEG valuation, 11 technical indicators with proper split-day volume handling (OBV/MFI on raw bars), CN-style KDJ (J=3K-2D), risk metrics (Beta/Sharpe/MaxDD with stock-suspension-aware aligned returns), and PBoC macro data.
      25
      11
      MIT

    • 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
    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.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only a single tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as executing read-only SQL queries against a specified set of tables, so agents can directly know what it does.

    Naming Consistency5/5

    The sole tool is named 'query', which is a simple, predictable, and consistent name. Since there is only one tool, there are no mixed conventions or inconsistent patterns to confuse an agent.

    Tool Count4/5

    A single tool might seem thin, but it serves a comprehensive purpose as a generic SQL query interface covering many tables. While additional metadata tools could be useful, the count is slightly under but acceptable for a focused read-only database server.

    Completeness4/5

    The tool provides complete read-only access to all listed tables, supporting SELECT/WITH queries with a row limit. A minor gap is the lack of schema/metadata exploration tools, but the description partially fills this by listing the available tables, making it workable for most use cases.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources