Log inSubmit server
PineForge — offline PineScript v6 backtest MCP logo

PineForge — offline PineScript v6 backtest MCP

Run PineScript v6 backtests locally by transpiling strategies to C++ and testing them against OHLCV CSV data.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install PineForge — offline PineScript v6 backtest MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "pineforge-offline-pinescript-v6-backtest-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@pineforge/backtest-mcp"
      ],
      "env": {
        "PINEFORGE_IMAGE": "YOUR_VALUE_HERE",
        "PINEFORGE_DOCKER_TIMEOUT_MS": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 12 tools correctly (Today).

Overview

PineForge — offline PineScript v6 backtest MCP MCP server transpiles PineScript v6 into C++ and runs local backtests against OHLCV CSV files through MCP. It includes tools for single runs, parameter grids, TradingView trade-by-trade comparisons, Pine feature coverage checks, and Binance data retrieval. Use it when an agent needs reproducible local strategy testing without sending strategy code or local CSVs to a hosted service.

Use cases

  • Backtest PineScript v6 strategies against local OHLCV CSV files
  • Sweep strategy inputs and engine overrides
  • Compare PineForge trades with TradingView exports
  • Fetch Binance klines for reproducible test datasets
  • Check Pine v6 feature coverage before translating a strategy

Key features

  • PineScript v6 to C++ transpilation
  • Single backtests against OHLCV CSVs
  • Cartesian input and override grid sweeps
  • Trade-by-trade TradingView parity checks
  • Binance OHLCV and symbol tools
  • Pine feature coverage inspection

Tools12

What PineForge — offline PineScript v6 backtest MCP lets your agent do. Expand a tool for its parameters.

Verified live~11.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

6/6 checks healthy over the last 33d

What it can do

From the 12 tools this server returned when we ran it; 12 declare their own safety hints.

Can delete or modify data · 3Handles credentials · 2Makes network requests · 10Read-only tools · 9
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age103 days
Maintainers1

Observed 2026-10-22 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · @pineforge/backtest-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars7Stargazers on the source repository.
npm downloads1.9kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed12Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How PineForge — offline PineScript v6 backtest MCP works

What PineForge — offline PineScript v6 backtest MCP does

PineForge — offline PineScript v6 backtest MCP exposes PineScript v6 translation, backtesting, data preparation, and coverage inspection through MCP. The bundled pineforge-release engine converts Pine source into a C++ translation unit and executes the resulting backtest against OHLCV data. The server is designed for local use, with the Docker image running the engine in-process and without requiring a host Docker daemon.

backtest_pine runs one strategy against a CSV. backtest_pine_grid sweeps the Cartesian product of supplied inputs and engine overrides, transpiling once and compiling and testing each combination. check_tradingview_parity compares a TradingView Strategy Tester export with PineForge results on a trade-by-trade basis. The server can also fetch Binance spot or USDT-perpetual klines into a backtest-ready CSV and search Binance symbols.

How it works

The Docker distribution communicates over stdio. Mount the directory containing input and output files at /work, then pass absolute container paths such as /work/btc.csv to the tools. PineScript translation and backtesting happen locally inside the container. Binance symbol and OHLCV tools use Binance public endpoints, while local lookups such as engine parameters and Pine feature coverage do not require network access.

Coverage tools report supported, partial, transpiler-supported, and unsupported Pine v6 topics. engine_info reports details about the bundled release when using the Docker image. The npm package has a different image-management interface: it adds image pull and image-check tools and uses Docker to run the engine for each transpilation or backtest.

Setup and configuration

Run PineForge — offline PineScript v6 backtest MCP with Docker using the published image and an interactive stdio stream. The documented command mounts the current directory at /work; do not add a TTY because it can corrupt MCP JSON-RPC traffic. On Linux, passing the host user and group IDs can keep generated files owned by the invoking user.

The npm and npx route requires Node 20 or newer and a running Docker daemon. It uses PINEFORGE_IMAGE to select the engine image, defaulting to ghcr.io/pineforge-4pass/pineforge-release:latest. PINEFORGE_DOCKER_TIMEOUT_MS controls the image-pull timeout and defaults to 120 seconds. The npm package confines paths to its working directory by default.

Claude Desktop, Cursor, and Claude Code examples are provided in the repository. For Claude Desktop and Cursor, configure the Docker command and mount an absolute host path. Claude Code can register the same command with claude mcp add.

Tools and capabilities

  • Translate PineScript v6 to C++ without running a backtest.
  • List accepted engine overrides and runtime parameters.
  • Run one backtest or a grid of inputs and overrides.
  • Compare results with a TradingView Strategy Tester export.
  • Fetch Binance spot or USDT-perpetual OHLCV data and write it to CSV.
  • List or filter Binance symbols with a five-minute in-process cache.
  • Inspect Pine feature support and detailed coverage topics.
  • Report the bundled engine release in the Docker image.

Limitations and notes

PineForge — offline PineScript v6 backtest MCP is local for source and user-provided CSV processing, but Binance tools make public API requests. The parity checker can also make an outbound request when no bars are supplied. No API key is required for those documented public endpoints.

The hosted endpoint described by the repository is separate from this local distribution: it is metered, crypto-focused, and does not provide the local server's transpile or grid tools. The local Docker image is the better fit when you need your own CSV files, local execution, or unmetered grid sweeps. Files written to a path can replace an existing file, so output paths should be selected deliberately.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about PineForge — offline PineScript v6 backtest MCP

PineForge — offline PineScript v6 backtest MCP is an MCP server that connects AI agents to a bundled PineScript-to-C++ engine and OHLCV data files. Its main tools transpile Pine v6, run single or grid backtests, compare trades with TradingView exports, fetch Binance data, and inspect Pine feature coverage locally.

Install it by running the published Docker image over stdio, mounting your data directory at `/work`; Docker is the only requirement for that route. You can also run `npx -y @pineforge/backtest-mcp`, which requires Node 20 or newer and a running Docker daemon.

Yes, Cursor is documented as a supported client. Add a project or user `.cursor/mcp.json` entry that runs the Docker image with `--rm -i` and mounts `${workspaceFolder}` at `/work`.

No, it does not require an API key for the documented Binance public endpoints. The Binance tools can fetch symbols or klines, while local backtests can use CSV files you provide.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPineForge — offline PineScript v6 backtest MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/pineforge-offline-pinescript-v6-backtest-mcp?style=directory)](https://allmcps.com/mcp/pineforge-offline-pinescript-v6-backtest-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/pineforge-offline-pinescript-v6-backtest-mcp"><img src="https://allmcps.com/api/badge/pineforge-offline-pinescript-v6-backtest-mcp?style=directory" alt="PineForge — offline PineScript v6 backtest MCP on AllMCPs" /></a>