Labsco
pineforge-4pass logo

PineForge Codegen

β˜… 2

from pineforge-4pass

Local MCP server: AI writes PineScript v6, bundled engine transpiles to C++ and backtests against Binance data β€” no API key, fully local.

πŸ”₯πŸ”₯πŸ”₯βœ“ VerifiedFreeAdvanced setup

⌁ labsco summary β€” our analysis, not the vendor's

What it is β€” A self-contained local MCP server where an AI writes PineScript v6 and a bundled engine transpiles it to C++ and backtests it against Binance data β€” no API key, fully local.

What you get β€”

  • Pine β†’ C++ β†’ backtest β€” transpile_pine, backtest_pine (against an OHLCV CSV), and backtest_pine_grid for a Cartesian sweep of inputs and overrides reusing one compile.
  • Binance data β€” fetch_binance_ohlcv writes a backtest-ready CSV from spot or USDT-perp klines; binance_symbols lists/filters symbols.
  • Coverage introspection β€” check_pine_feature, list_coverage_topics, and get_coverage_topic report which Pine v6 features are supported.
  • Engine info β€” list_engine_params and engine_info expose every backtest knob and the bundled engine version.

Requirements β€” Nothing account-based β€” env is empty and no API key. Requires Docker and outbound network access for the Binance fetch tools.

Cost snapshot β€” Open source under MIT; the transpiler engine is bundled and runs in-process β€” no paid service. Binance's public market API is used for data.

Setup effort β€” Self-host via Docker: docker run --rm -i -v "$PWD:/work" ghcr.io/pineforge-4pass/pineforge-codegen-mcp:latest, or use the hosted https://mcp.pineforge.dev/mcp endpoint.

Our take β€” A powerful, private way to let an agent iterate on trading strategies without leaking code to a cloud. Caveat: it requires Docker, and Pine v6 coverage is partial (the coverage-topic tools exist precisely because some identifiers are unsupported) β€” check check_pine_feature before relying on a language construct.

Source: the project README β€” summarized 2026-07-08.