Skip to main content
Glama
PineForge-Codegen

PineForge-Codegen

Related Servers

Alternatives to PineForge-Codegen

  • F
    license
    Not graded
    quality
    Not graded
    maintenance
    exposes a remote MCP endpoint so agents can: run strategy backtests by symbol/timeframe/date range, pass strategy inputs programmatically, receive structured backtest results (trades, win rate, profit, drawdown), keep long-running runs observable via progress notifications, support Binance Futures tickers only, enforce a maximum of 1440 candles per backtest, apply a rate limit of 3 backtests per
    7
    -
  • A
    license
    A
    quality
    D
    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
    1
    MIT
  • A
    license
    B
    quality
    B
    maintenance
    Open-source MCP server for market analysis: screeners, multi-timeframe technical analysis and backtests for crypto, stocks, forex and futures. 39 tools. Hosted version: TradingMCP.
    37
    1,648 PyPI
    5,317
    MIT

Related Servers

TDQS

A4.1/5.0

Scored across 12 tools

Disambiguation4/5

Each tool targets a distinct action, and descriptions actively disambiguate (backtest_pine vs backtest_pine_grid, transpile-only vs run). The coverage trio (list_coverage_topics → get_coverage_topic → check_pine_feature) is well-nested by granularity, and check_engine_image vs pull_engine_image are clear. Minor overlap: check_tradingview_parity also runs the strategy, and binance_symbols/fetch_binance_ohlcv both touch the Binance API, but boundaries remain legible.

Naming Consistency4/5

Names consistently use snake_case with a verb_noun pattern (list_*, get_*, check_*, backtest_*, fetch_*, transpile_*, pull_*). The only deviation is binance_symbols, which despite listing/validating omits the list_ prefix. Otherwise highly predictable.

Tool Count5/5

Twelve tools sit squarely in the well-scoped 3-15 range. Each earns its place: core workflow (transpile, backtest, sweep, parity), data/infra (fetch, symbols, image management), and coverage discovery (list/get/check). No filler.

Completeness4/5

The Pine backtest lifecycle is well covered end-to-end: coverage discovery, transpile, single backtest, parameter sweeps, data fetching, parity verification, and engine/image management. Minor gaps exist, such as no tool to list or retrieve previously generated report_path files or manage saved artifacts, but agents can work around this via filesystem paths.

Maintenance

ActivityActive
ResponsivenessUsually handled