MCP.Market

PineForge — offline PineScript v6 backtest MCP server

by pineforge-4pass·io.github.pineforge-4pass/pineforge-codegen-mcp·v0.9.18·7 stars

Offline PineScript v6 → C++ backtests at deterministic TradingView parity, run locally via MCP.

A85/100grade A
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
Growing

7 stars

Reviews

Write one

Nobody has reviewed PineForge — offline PineScript v6 backtest MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

PineForge — offline PineScript v6 backtest MCP tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How PineForge — offline PineScript v6 backtest MCP compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 70% of 48,255 servers
GitHub stars
7
more than 86% of 28,688 servers

Install PineForge — offline PineScript v6 backtest MCP in Claude Code, Cursor or VS Code

claude mcp add pineforge-codegen-mcp -- docker run -i --rm ghcr.io/pineforge-4pass/pineforge-codegen-mcp:v0.9.18
Add to Cursor

What the publisher says

From the PineForge — offline PineScript v6 backtest MCP repository's README, as published. We do not edit it. Read it on GitHub

@pineforge/backtest-mcp

Self-contained stdio MCP server: an AI agent writes PineScript v6, and the bundled pineforge-release image transpiles it to C++ and backtests it against Binance market data — all in one container, in-process. Fully local — the image bundles the pineforge-codegen transpiler, so Pine → C++ → backtest run with no host Docker daemon. No API key, nothing leaves the box.

Tools

Install

Runs as a self-contained container over stdio — engine bundled, in-process, no host Docker daemon, no API key. Mount a working dir at /work so the server can read/write your CSVs:

docker run --rm -i -v "$PWD:/work" ghcr.io/pineforge-4pass/pineforge-backtest-mcp:latest

Only requirement: Docker, and outbound network for the Binance fetch tools. Wire it into your MCP client below.

The image's :latest and npm's latest always carry a stable release. A pineforge-release prerelease (such as 1.0.0-rc.1) produces a prerelease of this server (X.Y.Z-alpha.N, -beta.N or -rc.N): the image :vX.Y.Z-rc.N, built FROM that pineforge-release prerelease, and npm @pineforge/backtest-mcp@next, which, like any npm install, runs the engine image named by PINEFORGE_IMAGE (default pineforge-release:latest, the stable engine). Prereleases are not listed in the MCP Registry.

Hosted (no-install) alternative

Want the fastest try with no Docker and no API key? Paste the Streamable HTTP endpoint into any MCP client:

https://mcp.pineforge.dev/mcp

Tradeoff vs this repo: the hosted server is metered (per-IP weekly quota on backtestpine + Cloudflare edge rate-limiting) and runs against a fixed, sealed crypto data-lake (Binance spot + USDT-perp). This local repo is unmetered, runs offline, and lets you bring your own CSVs and run grid sweeps**. Repo: pineforge-mcp-public.

Client configuration

Mount a directory at /work; point fetchbinanceohlcv / backtest_pine at paths under it. (-i is required; never add -t — a TTY corrupts the stdio JSON-RPC stream.)

Claude Desktop / Cursor / generic JSON

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

PineForge — offline PineScript v6 backtest MCP: common questions

Is PineForge — offline PineScript v6 backtest MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the PineForge — offline PineScript v6 backtest MCP safety report
How do I install PineForge — offline PineScript v6 backtest MCP?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does PineForge — offline PineScript v6 backtest MCP need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is PineForge — offline PineScript v6 backtest MCP maintained?
The last commit was 40 days ago (2026-09-25). The latest release is v0.9.18.
What can I use instead of PineForge — offline PineScript v6 backtest MCP?
Servers from other publishers that do the same job: TradingMCP MCP server.
How does PineForge — offline PineScript v6 backtest MCP compare with other MCP servers?
safety score 85/100 (higher than 70% of 48,255 servers); github stars 7 (more than 86% of 28,688 servers). Full comparison.

Alternatives to PineForge — offline PineScript v6 backtest MCP

Same job from other publishers: the closest match first, then the best rated.

  • TradingMCP
    Market analysis for AI assistants: screeners, multi-timeframe analysis, backtests, in-chat charts.
    A