Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PineForge — offline PineScript v6 backtest MCP

OCI · GHCR.IO/PINEFORGE-4PASS/PINEFORGE-BACKTEST-MCP

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

0 this week 49 Trust /100

Last scanned (21 hours ago)

Scores higher than 63% of OCI servers

Category Testing and QA

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency32
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • License check failed: the license (Apache-2.0 AND LicenseRef-PineForge-Source-License-1.2) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 1 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 5906 tokens (~536/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (12)

  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (4)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  • Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1
    • Stability: 0.97 → pass security
  • 19 Nov 26 −1
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Stability: pass → 0.97 functional
    • Package version: v0.9.44 → v0.9.46 functional
  • 13 Nov 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail ▼ functional
  • 12 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 −2
    • Stability: pass → 0.87 functional
  • 30 Oct 26 +1
    • Stability: 0.97 → pass security
  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed oci/ghcr.io/pineforge-4pass/pineforge-backtest-mcp@v0.9.46

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 11 exposed · ~5,558 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
backtest_pine ~1,337

Run a real, deterministic backtest of a PineScript v6 strategy — prefer this over estimating its trades or P&L by reasoning, which is unreliable for Pine (series semantics, intrabar fills, and strategy.* order logic do not reproduce from approximation). Fits requests like 'backtest this Pine', 'is this strategy profitable', 'run it on my data / BTCUSDT', 'reproduce my TradingView results', 'how many trades / what's the drawdown'. Transpile a PineScript v6 strategy and run it against an OHLCV CSV via the bundled pineforge-release (in-process, no host Docker daemon). Fully local — transpile + backtest run in this image; nothing leaves the box, no API key. Optional `inputs` overrides input.*() named values from the Pine source (keys = the second arg of input.*(...) calls, e.g. 'Fast Length'). Optional `overrides` overrides strategy(...) header fields (initial_capital, commission_value, default_qty_value, pyramiding, slippage, default_qty_type, commission_type, process_orders_on_close). Returns the parsed JSON report (summary, trades, applied_inputs, applied_overrides, applied_runtime, elapsed_seconds). The instrument matters: pass `symbol` (a Binance symbol) or `syminfo` (your own qty_step, mintick, ...); a CSV from fetch_binance_ohlcv carries its instrument and needs neither. The lot size is TradingView's own reading for the symbol, from a measured table shipped with this server (Binance's LOT_SIZE.stepSize only for a symbol TradingView does not list; TradingView's usual 0.001 for a listing newer than the table); the tick size and currencies come from Binance's public exchangeInfo (or from the sidecar next to a CSV fetched by fetch_binance_ohlcv). `syminfo` goes over all of it. What was applied is in applied_runtime.syminfo; when the lot grid is unknown, or its lot size is not a TradingView reading, the result has a `warnings` entry. If the report is too large to return inline it is written to report_path and a compact summary (with that path) is returned instead. Us…

NameTypeReqDescription
imagestring–Docker image override. Defaults to ghcr.io/pineforge-4pass/pineforge-release@sha256:84e55d77b6a61467efd2543c31eac260b0802f7936091f00ed3d649f8fad2d93.
inputsobject–Map of Pine input.*() names → value (string/number/bool). Sent as PINEFORGE_INPUTS env var to the runtime.
marketstring–'spot' (default; a warning says when it is assumed) or 'usdt_perp'; the Binance market `symbol` is looked up in. A CSV fetched by fetch_binance_ohlcv for the same symbol keeps the market it was fetch…
ohlcv_csv_pathstringyesAbsolute or cwd-relative path to OHLCV CSV with header 'timestamp,open,high,low,close,volume' (timestamp = UNIX ms UTC).
overridesobject–strategy(...) header overrides. Each key maps to a single argument of the Pine `strategy()` call; only the keys you set are applied. Sent as PINEFORGE_OVERRIDES env var. Call list_engine_params for t…
report_pathstring–Where to write the full JSON report IF it is too large to return inline. Large backtests (long trade lists + equity curves) are offloaded to this file and the tool returns a compact summary + report_…
runtimeobject–Engine runtime args (NOT strategy() header) controlling timeframe semantics and intra-bar fill simulation. input_tf / script_tf set the chart and strategy timeframes — script_tf must be coarser than…
sourcestringyesPineScript v6 source.
symbolstring–Binance symbol the CSV holds, e.g. 'BTCUSDT'. The lot size is TradingView's own reading for the symbol, from a measured table shipped with this server (Binance's LOT_SIZE.stepSize only for a symbol T…
syminfoobject–The instrument's own values, for a CSV of any other instrument; they win over what `symbol` or the CSV's sidecar gives. Applied to the engine: qty_step (the lot grid) and mincontract, mintick, pointv…

No output schema declared.

No examples provided.

backtest_pine_grid ~1,258

Use when the user wants to optimize, sweep, tune, or compare PineScript parameter values (e.g. 'try fast length 8/12/19', 'find the best commission/qty settings') rather than test a single configuration — for one fixed configuration use backtest_pine. Run a parameter sweep: transpile the Pine source ONCE (in-process, no host Docker), then compile (g++) and backtest that C++ against the OHLCV CSV once per combination in the cartesian product of `inputs` × `overrides` grids. Returns a ranked list of {inputs, overrides, summary, elapsed_seconds} entries sorted by `sort_by` descending, plus the top entry under `best`. Cap: max_combinations (default 64). Takes the same `symbol` / `market` / `syminfo` as backtest_pine and applies the instrument to every combination (the result's `instrument` shows it). The lot size is TradingView's own reading for the symbol, from a measured table shipped with this server (Binance's LOT_SIZE.stepSize only for a symbol TradingView does not list; TradingView's usual 0.001 for a listing newer than the table); the tick size and currencies come from Binance's public exchangeInfo (or from the sidecar next to a CSV fetched by fetch_binance_ohlcv). `syminfo` goes over all of it. Set concurrency > 1 to run backtests in parallel — 2-4 is usually plenty.

NameTypeReqDescription
concurrencyinteger–Parallel backtests. Default 1.
fixed_inputsobject–Inputs applied to every combo (overridden by per-combo `inputs` keys).
fixed_overridesobject–Overrides applied to every combo (overridden by per-combo `overrides` keys).
imagestring–Docker image override. Defaults to ghcr.io/pineforge-4pass/pineforge-release@sha256:84e55d77b6a61467efd2543c31eac260b0802f7936091f00ed3d649f8fad2d93.
include_tradesboolean–Include the per-trade list in each result. Default false (saves tokens).
inputsobject–Grid of input.*() names → list of values to sweep. Example: {"Fast Length": [8, 12, 19], "Slow Length": [21, 26, 39]}
marketstring–'spot' (default; a warning says when it is assumed) or 'usdt_perp'; the Binance market `symbol` is looked up in. A CSV fetched by fetch_binance_ohlcv for the same symbol keeps the market it was fetch…
max_combinationsinteger–Hard cap on combinations. Default 64.
ohlcv_csv_pathstringyesPath to OHLCV CSV (same format as backtest_pine).
overridesobject–Grid of strategy(...) header overrides → list of values, one axis per key. Example: {"default_qty_value": [1, 5], "commission_value": [0.04]}. Call list_engine_params for the full catalog with types…
report_pathstring–Where to write the full sweep JSON IF it is too large to return inline. Oversized sweeps are offloaded here and the tool returns the best + top-ranked combinations + report_path; read the file for al…
runtimeobject–Engine runtime args applied to every combo in the sweep. Same shape as backtest_pine.runtime — input_tf / script_tf / bar_magnifier / magnifier_samples / magnifier_dist. Currently fixed across the gr…
sort_bystring–summary.* field to rank by, descending. Default net_pnl.
sourcestringyesPineScript v6 source.
symbolstring–Binance symbol the CSV holds, e.g. 'BTCUSDT'. The lot size is TradingView's own reading for the symbol, from a measured table shipped with this server (Binance's LOT_SIZE.stepSize only for a symbol T…
syminfoobject–The instrument's own values, for a CSV of any other instrument; they win over what `symbol` or the CSV's sidecar gives. Applied to the engine: qty_step (the lot grid) and mincontract, mintick, pointv…

No output schema declared.

No examples provided.

binance_symbols ~220

List/validate symbols available on the Binance public API for OHLCV fetching. Filters: `query` (substring of the symbol), `quote_asset` (e.g. 'USDT'), `base_asset` (e.g. 'BTC'), `status` (e.g. 'TRADING'), `contract_type` (futures only, e.g. 'PERPETUAL'). Results are cached 5 min in process. Free.

NameTypeReqDescription
base_assetstring–Filter by base asset (e.g. 'BTC').
contract_typestring–Futures only. 'PERPETUAL' for usdt_perp swaps.
limitinteger–Max symbols to return. Default 200.
marketstringyes'spot' or 'usdt_perp'.
querystring–Case-insensitive substring of the symbol.
quote_assetstring–Filter by quote asset (e.g. 'USDT').
statusstring–Filter by status. 'TRADING' returns active only.

No output schema declared.

No examples provided.

check_pine_feature ~264

Answer "does PineForge support X?" for a specific Pine v6 identifier or namespace (e.g. 'ta.supertrend', 'alert', 'array.new', 'request.financial'). Use it (a) BEFORE relying on any function you are unsure about while writing a strategy, and (b) to DIAGNOSE a backtest that compiled but behaved wrong or empty — plots, tables and alerts (plot, bgcolor, table, alert) are accepted and produce NO effect, while line, box and label objects are data the strategy can read back. Resolves by exact feature match, then longest namespace prefix, then alias, returning {query, status, topic, note} where status is supported / partial / unsupported / via_transpiler / not_found (via_transpiler = works end-to-end; unsupported = refused, not compiling, stopping the run, or no effect) and the note quotes the catalog entry, which says what THIS server can and cannot do (e.g. request.security on another symbol). Local, free, no engine run.

NameTypeReqDescription
featurestringyesPine identifier or namespace to look up, e.g. 'ta.supertrend', 'alert', 'array.new', 'strategy.entry', 'request.dividends'.

No output schema declared.

No examples provided.

check_tradingview_parity ~1,407

Check how closely PineForge reproduces a TradingView backtest, trade by trade. Give the Pine v6 script and TradingView's own Strategy Tester export: the "List of trades" CSV, or the XLSX report as base64. PineForge runs the script on the same market and window and grades the two trade lists with the grader behind its recorded parity figures (pineforge-engine v1.2.0 scripts/verify_corpus.py, byte-identical in v1.3.0 and the frozen 1.4.0 candidate). The execution harness run_strategy.py is copied byte-for-byte from frozen engine candidate b3192bfc2f5a24bf4efd6d1d01e01e8fe619dfed; file identity is not a new native corpus parity result. Returns the tier (excellent, strong, moderate, weak, minimal), each check with its value and thresholds, matched and unmatched trade counts, the first mismatches side by side with hints, and a timezone check. Bars: pass ohlcv_csv or ohlcv_csv_path for any market; without them, BINANCE:<SYMBOL> (spot) and BINANCE:<SYMBOL>.P (USDT-M perpetual) bars are fetched from Binance's public API (at most 100,000 bars); any other symbol needs your bars. No quota and no history window beyond that. Scripts declaring use_bar_magnifier=true also fetch 1-minute bars through the last chart bar's close, counted in that limit, on charts the harness magnifies (coarser than 1 minute, at most 1 day) unless runtime.bar_magnifier is false. With your own bars, optionally pass magnifier_ohlcv_csv or magnifier_ohlcv_csv_path; a script that declares the magnifier but runs without one gets a warning that fills inside bars may differ from TradingView's. Settings the XLSX Properties sheet states are used; an explicit input that disagrees with one is an error. The run applies the instrument's lot size and tick size as backtest_pine does, for BINANCE:<SYMBOL> and BINANCE:<SYMBOL>.P. The lot size is TradingView's own reading for the symbol, from a measured table shipped with this server (Binance's LOT_SIZE.stepSize only for a symbol TradingView does not list; TradingView'…

NameTypeReqDescription
chart_timezonestring–IANA timezone TradingView printed the trade times in (its chart timezone), e.g. 'Asia/Taipei', 'UTC', 'America/New_York'. Required unless the export states it.
inputsobject–Pine input overrides (TradingView's Inputs tab), as in backtest_pine.
magnifier_ohlcv_csvstring–Optional 1-minute bars for a declared bar magnifier, in the same formats as ohlcv_csv and with the same 67,108,864-character limit. Cover the first chart bar's open through the last chart bar's close.
magnifier_ohlcv_csv_pathstring–Path to optional 1-minute magnifier bars (same formats and path rules as ohlcv_csv_path, no size limit). Pass this or magnifier_ohlcv_csv, not both.
max_mismatchesinteger–How many mismatching trades to list (default 10, at most 50); the counts are always complete.
ohlcv_csvstring–Your bars as CSV text: header timestamp,open,high,low,close,volume (epoch ms), or TradingView's chart export time,open,high,low,close,Volume (epoch seconds or ISO 8601). At most 67,108,864 characters…
ohlcv_csv_pathstring–Path to your bars CSV (same formats as ohlcv_csv, no size limit; same path rules as backtest_pine's ohlcv_csv_path, checked after resolving '..' and symlinks).
pinestringyesThe Pine v6 strategy source TradingView ran (at most 262,144 bytes of UTF-8).
range_endstring–ISO 8601 end of TradingView's range. Default: the export's last row (the result says so).
range_startstring–ISO 8601 date or datetime of the first bar TradingView computed (UTC unless it has an offset). Required unless the XLSX states it.
runtimeobject–Engine runtime args of list_engine_params (input_tf, script_tf, bar_magnifier, magnifier_samples, magnifier_dist).
strategy_overridesobject–TradingView's Properties tab: the 9 strategy() knobs of list_engine_params.
symbolstring–TradingView ticker the backtest ran on, e.g. 'BINANCE:ETHUSDT.P'. Required unless the XLSX states it or you pass bars.
syminfoobject–The instrument's own values (qty_step, mintick, pointvalue, ...), as in backtest_pine: they win over what the symbol resolves, and are the whole instrument for a market other than Binance. Without a…
timeframestring–TradingView resolution of the chart: '1', '5', '15', '60', '240', '1D', '1W', ... Required unless the XLSX states it.
tradingview_tradesstringyesTradingView's Strategy Tester export: the "List of trades" CSV text, or the XLSX report file base64-encoded (it starts with UEsDB). The CSV needs the columns Trade number, Type, Date and time and a P…

No output schema declared.

No examples provided.

engine_info ~38

Report the bundled backtest engine: mode, baked-in flag, and version. This image runs the engine in-process (no host Docker daemon needed).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fetch_binance_ohlcv ~366

Fetch OHLCV candles from Binance public API and write a backtest-ready CSV (header: timestamp,open,high,low,close,volume; timestamp = open time in UNIX ms UTC). Supports `spot` and `usdt_perp` (USDT-margined perpetual futures). Requests larger than 1000 bars are paginated automatically. Also records the symbol's instrument in <output_path>.instrument.json (lot size: TradingView's own reading from a measured table shipped with this server, Binance's LOT_SIZE.stepSize for a symbol TradingView does not list, TradingView's usual 0.001 for a listing newer than the table; tick size and currencies from Binance's public exchangeInfo), which backtest_pine and backtest_pine_grid pick up; the result's `instrument` shows what was recorded. The output path must live inside the MCP cwd unless PINEFORGE_ALLOW_ANYWHERE=1.

NameTypeReqDescription
end_timeinteger–UNIX ms UTC. Defaults to now.
intervalstringyesKline interval. Spot supports 1s + 1m..1M; usdt_perp supports 1m..1M (no 1s).
limitinteger–Total bars to fetch. Default 1000. Paginated above 1000.
marketstring–'spot' (default) or 'usdt_perp'.
output_pathstringyesPath to write the CSV (will create parent dirs as needed).
start_timeinteger–UNIX ms UTC. If unset, derived from end_time/now and limit.
symbolstringyesBinance symbol, e.g. 'BTCUSDT'. Use binance_symbols to validate.

No output schema declared.

No examples provided.

get_coverage_topic ~162

Returns the full detail plus the exact supported[], partial[], via_transpiler[] and unsupported[] feature lists for ONE coverage topic id (ids from list_coverage_topics, e.g. 'ta', 'strategy_orders', 'request_security', 'drawing_plotting_alerts'). Use when you are about to work in a feature area and need to know precisely which functions there are implemented vs skipped — e.g. before using request.security, the ta.* library, or strategy risk knobs. Unknown ids return an error marker listing the valid ids. Local, free, no engine run.

NameTypeReqDescription
topicstringyesCoverage topic id from list_coverage_topics (e.g. 'ta', 'strategy_orders', 'request_security', 'drawing_plotting_alerts').

No output schema declared.

No examples provided.

list_coverage_topics ~181

START HERE before writing, porting, or backtesting a Pine v6 strategy on PineForge. PineForge implements a SUBSET of Pine v6, so checking coverage first avoids a strategy that compiles but silently misbehaves vs TradingView. Lists every coverage topic with a one-line status (supported / partial / unsupported / via_transpiler) and summary, plus the legend (note: via_transpiler still works end-to-end; unsupported means refused, not compiling, stopping the run where its value is read, or accepted with no effect) and the coverage version. Statuses describe what a backtest on THIS server can do. Cheap, free, local — no engine run, no I/O. Then drill in with get_coverage_topic for one area's per-feature lists, or check_pine_feature to look up a single identifier.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_engine_params ~159

Returns the full catalog of engine knobs accepted by backtest_pine / backtest_pine_grid in two groups: strategy_overrides (the 9 strategy(...) header fields the runtime reads via PINEFORGE_OVERRIDES — initial_capital, pyramiding, slippage, commission_value, commission_type, default_qty_value, default_qty_type, process_orders_on_close, close_entries_rule) and runtime_args (input_tf, script_tf, bar_magnifier, magnifier_samples, magnifier_dist — args to run_backtest_full, NOT part of the strategy() header). Each entry is {key, type, enum?, description}. Does not run the engine. Use this to discover what knobs the engine exposes before issuing a backtest.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

transpile_pine ~166

Transpile PineScript v6 source to a C++ translation unit locally, using the pineforge-codegen transpiler bundled in this image (in-process, no host Docker). No API key, no network — source never leaves the machine. Returns the generated C++ as text. Use backtest_pine if you also want to run the strategy.

NameTypeReqDescription
imagestring–Docker image override. Defaults to ghcr.io/pineforge-4pass/pineforge-release@sha256:84e55d77b6a61467efd2543c31eac260b0802f7936091f00ed3d649f8fad2d93.
sourcestringyesPineScript v6 source (must include //@version=6).

No output schema declared.

No examples provided.

Install

How do I install the PineForge — offline PineScript v6 backtest MCP server?

PineForge — offline PineScript v6 backtest MCP runs locally as a container image, launched with docker run --rm -i ghcr.io/pineforge-4pass/pineforge-backtest-mcp:v0.9.46. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/pineforge-4pass/pineforge-backtest-mcp

# add to Claude Code
claude mcp add pineforge-4pass-pineforge-backtest-mcp -- docker run --rm -i ghcr.io/pineforge-4pass/pineforge-backtest-mcp:v0.9.46
Common questions

What is the PineForge — offline PineScript v6 backtest MCP server?

PineForge — offline PineScript v6 backtest MCP is listed in the public MCP registry as io.github.pineforge-4pass/pineforge-backtest-mcp. Offline PineScript v6 → C++ backtests at deterministic TradingView parity, run locally via MCP. This page covers its container image (ghcr.io/pineforge-4pass/pineforge-backtest-mcp).

Is the PineForge — offline PineScript v6 backtest MCP server safe to use?

PineForge — offline PineScript v6 backtest MCP scores 49 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the PineForge — offline PineScript v6 backtest MCP server expose?

PineForge — offline PineScript v6 backtest MCP exposes 11 tools: transpile_pine, backtest_pine, backtest_pine_grid, check_tradingview_parity, fetch_binance_ohlcv, and 6 more. Their descriptions and schemas cost roughly 5,558 tokens of context every time the server is loaded.

Is the PineForge — offline PineScript v6 backtest MCP server still maintained?

PineForge — offline PineScript v6 backtest MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the PineForge — offline PineScript v6 backtest MCP server?

VerifyMCP ran 12 checks on PineForge — offline PineScript v6 backtest MCP, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about PineForge — offline PineScript v6 backtest MCP: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.