Log inSubmit server
Pineforge Codegen MCP logo

Pineforge Codegen MCP

by pineforge-4pass

Backtests Pine Script v6 strategies against crypto OHLCV and checks trade-by-trade parity with TradingView.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Pineforge Codegen 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-4pass-pineforge-codegen-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@pineforge/backtest-mcp"
      ]
    }
  }
}

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

Automated check passed— started and listed 12 tools correctly (10d ago).

Overview

The pineforge-4pass/pineforge-codegen-mcp MCP server runs deterministic Pine Script v6 backtests through PineForge's hosted engine. It transpiles strategy source, resolves supported crypto OHLCV by symbol, interval, venue, and date range, then returns performance data, trades, applied settings, warnings, and the resolved window. Use it to test strategies, reproduce TradingView results, inspect supported Pine features, or compare exported TradingView trades. The hosted service requires no API key but applies weekly per-IP quotas, monthly compute limits, crypto-only coverage, and a 365-day history limit.

Use cases

  • Backtest a Pine Script v6 strategy on supported crypto OHLCV
  • Compare PineForge trades with a TradingView trade-list export
  • Check whether a Pine v6 function or namespace is supported
  • Tune named strategy inputs through repeated cached runs
  • Inspect supported symbols and engine parameters

Key features

  • Deterministic Pine v6 backtesting
  • TradingView trade-by-trade parity checks
  • Crypto symbol discovery and filtering
  • Pine feature coverage lookup
  • Strategy input and runtime override support
  • Quota and waitlist management

Tools12

What Pineforge Codegen 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 2d ago

Recent health check succeeded.

13/14 checks healthy over the last 80d

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
Tool definitions changed on 2026-10-19. Review them if you approved this server earlier.
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age100 days
Maintainers1

Observed 2026-10-19 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 11d 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.
Last commit4d 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 activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Pineforge Codegen MCP works

What pineforge-4pass/pineforge-codegen-mcp does

The pineforge-4pass/pineforge-codegen-mcp MCP server exposes PineForge's hosted Pine Script v6 backtesting and TradingView comparison workflow through MCP. Its main execution tool, backtest_pine, accepts strategy source plus a symbol, interval, venue, and time window. PineForge transpiles the source and runs it against OHLCV resolved by its data service, returning a parsed report with summary statistics, trades, applied inputs and overrides, runtime details, elapsed time, warnings, and the resolved data window.

The service is intended for one configuration at a time. To tune a strategy, resend the same source and change the inputs or overrides values rather than editing literal parameter values in the Pine code. Reusing identical source enables the compile cache for faster follow-up runs.

How it works

check_tradingview_parity accepts a Pine v6 script and a TradingView Strategy Tester trade-list export in CSV or base64-encoded XLSX form. You also provide the chart ticker, timeframe, range start, and timezone. PineForge runs the script on the corresponding supported market and grades the resulting trade list against the export. The response includes a parity tier, thresholds, matched and unmatched counts, the first differing trades, diagnostic hints, and a timezone check.

The hosted engine runs in a sandboxed Cloudflare Container for backtests and parity checks. engine_info reports its mode, baked-in status, and version. list_symbols searches symbols available from the PineForge data API. list_engine_params documents strategy header overrides and runtime arguments without executing a backtest.

Before writing or debugging a strategy, use list_coverage_topics, get_coverage_topic, or check_pine_feature. These tools identify supported, partial, transpiler-handled, and unsupported Pine features. This matters because some constructs may compile but have no effect; for example, the provided catalog notes that plots, tables, and alerts do not produce effects, while line, box, and label objects can be read by a strategy.

Setup and configuration

The hosted endpoint is https://mcp.pineforge.dev/mcp and uses Streamable HTTP, so no local engine, Docker daemon, data file, or API key is required. Configure that endpoint in an MCP client that supports Streamable HTTP. The repository README also documents Claude Desktop, Cursor, and Claude Code client configurations, but those examples refer to the local @pineforge/backtest-mcp package and its bundled container rather than this hosted listing.

Backtest inputs can override named input.*() values through inputs; the key is the input's named-value argument. overrides changes supported strategy(...) header fields. list_engine_params provides the accepted keys and types. Call check_quota to inspect weekly usage; it does not consume quota. join_waitlist accepts an email and optional use case for notifications about the API-key tier and PineForge Studio.

Limitations and notes

The hosted service covers crypto markets only: Binance, Bybit, and OKX spot and USDT-perpetual markets, plus Coinbase spot. Free-tier requests cover the last 365 days, and the newest published bar is typically about one hour behind real time. Backtest ranges outside the available history are clamped with warnings, while parity requests outside the hosted range are refused. Backtests have a 50,000-bar output cap.

backtest_pine and check_tradingview_parity share a fixed weekly per-IP quota and also consume a monthly compute budget. Exceeding the weekly quota causes refusal; reaching the compute budget returns ok: false. Other tools are free of that quota but remain subject to per-IP rate limits. The hosted service supports one backtest configuration per call and does not provide sweeps. For unsupported markets or ranges, the material points to the local MCP package with user-supplied bars instead. The implementation covers a subset of Pine v6, so feature coverage should be checked before relying on a function or namespace.

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 Codegen MCP

pineforge-4pass/pineforge-codegen-mcp is an MCP server that connects AI clients to PineForge's hosted Pine Script v6 engine. Its main tools, backtest_pine and check_tradingview_parity, run deterministic crypto strategy backtests and compare trades with TradingView exports. Supporting tools inspect symbols, parameters, Pine feature coverage, engine status, quota, and updates.

Use the hosted Streamable HTTP endpoint `https://mcp.pineforge.dev/mcp`; no local installation, Docker daemon, or API key is required. The repository also documents a separate local `@pineforge/backtest-mcp` package, which uses Docker and local or fetched OHLCV data.

Yes, the README names Cursor as a supported MCP client. Its example config is for the separate local Docker-based `@pineforge/backtest-mcp` package; the hosted listing can be used through Cursor's Streamable HTTP MCP configuration.

Call `check_pine_feature` with the Pine identifier or namespace, such as `ta.supertrend`, `alert`, or `request.security`. It returns a status, topic, and catalog note; use `list_coverage_topics` and `get_coverage_topic` for broader feature-area details.

It backtests supported crypto markets from Binance, Bybit, and OKX spot or USDT-perpetual venues, plus Coinbase spot. Hosted free-tier data covers the last 365 days, with a typical delay of about one hour for the latest bar.

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 Codegen MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/pineforge-4pass-pineforge-codegen-mcp?style=directory)](https://allmcps.com/mcp/pineforge-4pass-pineforge-codegen-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/pineforge-4pass-pineforge-codegen-mcp"><img src="https://allmcps.com/api/badge/pineforge-4pass-pineforge-codegen-mcp?style=directory" alt="Pineforge Codegen MCP on AllMCPs" /></a>