Skip to main content
Glama

Related Servers

Alternatives to mcp-tradecanvas

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      A minimal MCP server providing a normalized API for code navigation and repository inspection through tools like symbol searching and call tracing. It enables AI agents to perform structured analysis of codebases by mapping endpoints, inspecting file trees, and tracing symbol relationships.
      3
      -
    • A
      license
      A
      quality
      C
      maintenance
      MCP server that indexes your codebase's public API at startup and serves it via compact tool responses, saving tokens vs reading source files.
      5
      70 PyPI
      21
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for romaco-charts. Control your trading chart from Claude, Cursor, or any MCP-compatible AI agent.
      27
      10 npm
      1
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server that provides LLMs with introspection data and documentation for the Freqtrade codebase. It enables AI tools to access class signatures, method details, and configuration schemas to assist in writing more reliable trading strategies.
      13
      18
      GPL 3.0
    • A
      license
      A
      quality
      C
      maintenance
      A type-safe MCP server that enables AI agents to control TradingView Desktop via Chrome DevTools Protocol, allowing chart state reading, symbol/timeframe changes, and OHLCV data fetching.
      11
      85 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server exposing a registry of paper-backed quantitative trading methods plus a deterministic, no-LLM decision helper for reproducible trading research.
      13
      31 PyPI
      MIT

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource or action: indicator discovery has separate list and get tools, while drawing tools, constructor options, widget features, style keys, and option validation each cover a different area. The descriptions explicitly distinguish the option-related tools, so an agent can tell them apart.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: list_indicators, get_indicator, list_drawing_tools, list_options, list_widget_features, list_style_keys, validate_options. The single get_ tool is the standard counterpart to its list_ tool.

    Tool Count5/5

    Seven tools is well-scoped for a chart-library discovery and validation server. Each tool earns its place by covering a distinct lookup or validation need without bloating the surface.

    Completeness4/5

    The set covers the main discovery workflows: indicators, drawing tools, constructor options, widget features, style keys, and option validation. Minor gaps exist, such as no dedicated get_drawing_tool detail tool and no validator for indicator params or drawing-tool options, but agents can largely work around these using the list tools.

    Maintenance

    ActivityActive
    ResponsivenessResponsive