Skip to main content
Glama
janorium-mcp

janorium-mcp

Official

Related Servers

Alternatives to janorium-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Backtest PineScript v6 strategies locally from your AI agent: transpiles Pine to C++ and runs it on the deterministic, TradingView-validated PineForge engine via Docker. Tools for single backtests, parameter-grid sweeps, and Binance OHLCV fetch — no API key, data never leaves your machine.
      12
      50 npm
      9
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides tools to research crypto trading strategies via backtesting, walk-forward validation, and paper trading, with a deflated-Sharpe overfitting check. Enables natural-language-driven analysis and interpretation of strategy performance.
      2
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language management of Binance USDS-margin futures trading, including balance checks, order placement, stop-loss/take-profit, and strategy backtesting.
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to backtest trading strategies described in plain English, providing access to market data, technical indicators, and comprehensive performance reports.
      13
      1
      MIT

    TDQS

    B3.4/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools map to a clearly distinct resource and action: strategy lifecycle, backtest analytics, optimization, campaigns, and market data are cleanly separated. The few soft overlaps are research_scan vs research_job_create and generic wait vs the *_get tools, but the descriptions give enough guidance to choose correctly.

    Naming Consistency4/5

    The set uses consistent snake_case with a domain/resource prefix followed by an action (strategy_*, backtest_*, optimization_*, campaign_*). Minor deviations such as the bare wait and the longer strategy_set_visibility are still readable and predictable.

    Tool Count2/5

    At 28 tools the surface exceeds the 25+ threshold for a heavy toolset, even though each tool covers a real operation. The domain is broad, but the set would benefit from consolidation of repeated status/analytics patterns or grouping of related backtest diagnostics.

    Completeness3/5

    Core workflows are covered end-to-end: research, strategy validation/save, backtesting, optimization, campaign holdout, and market coverage. However, there are no listing/search tools for strategies, backtests, optimizations, or research jobs, and no strategy delete operation, so agents often need externally supplied IDs. Referenced docs:// resources are also not exposed as callable tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues