Skip to main content
Glama

Related Servers

Alternatives to algotest-backtester

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents and MCP hosts to drive a persistent headless Chromium browser through Playwright, navigating pages, mapping visible fields and actions, clicking, typing, scrolling, and capturing screenshots via stdio tool calls. It also powers a local AI Test Studio dashboard that generates and runs structured end-to-end test plans with assertions, per-step timing, and screenshot evidence.
      4
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Connects an AI assistant to a locally running TradingView Desktop app through Chrome DevTools Protocol, enabling chart analysis, Pine Script development, drawing, alerts, replay practice, screenshots, and multi-pane workflow automation.
      84 npm
      -
    • A
      license
      A
      quality
      D
      maintenance
      Drives your real local Chrome with profile isolation, allowing LLMs to interact with your logged-in sessions without modifying your actual profile.
      13
      37 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to control a local Chromium browser via CDP for page snapshots, screenshots, human-like interactions, autonomous crawling, API/GraphQL reconnaissance, authenticated differential testing, and Burp-like intercept, repeater, and intruder workflows with scope enforcement and audit logging.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables algorithmic trading on the Shoonya platform through natural language commands, with military-grade encryption for credential security.
      11
      11 npm
      ISC

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation2/5

    backtest_strategy overlaps heavily with both preview_backtest and run_backtest, since it can either preview or run a strategy depending on confirm. This makes it unclear when an agent should use backtest_strategy versus the more specific preview/run tools.

    Naming Consistency5/5

    All five tool names follow a consistent snake_case verb_noun pattern: backtest_strategy, preview_backtest, run_backtest, get_results, close_browser. This is predictable and easy to scan.

    Tool Count5/5

    Five tools is well-scoped for a browser-automation backtesting workflow. Each tool maps to a meaningful step in the process without unnecessary bloat.

    Completeness4/5

    The set covers the core workflow: preview, run, retrieve results, and clean up. Minor gaps exist, such as no explicit cancel or historical results retrieval, but agents can likely complete the main backtest lifecycle.

    Maintenance

    ActivityStale
    ResponsivenessSyncing