PineForge

Backtest Pine

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 BTCUSDT', 'reproduce my TradingView results', 'how many trades / what's the drawdown'. Transpiles the Pine source and runs it against OHLCV resolved from the team

Fetch Ohlcv

Fetch OHLCV candles from the team crypto data-lake for the given symbol/interval/market/window and return them as backtest-ready CSV INLINE (columns: timestamp,open,high,low,close,volume; timestamp = open time in UNIX ms UTC), plus a metadata block. 1-minute lake bars are resampled to your interval (open=first, high=max, low=min, close=last, volume=sum). Supports `spot` and `usdt_perp`. Use this to inspect data before backtesting; backtest_pine resolves its own bars from the same source. Free ti

Binance Symbols

List the symbols the data-lake actually has OHLCV for (i.e. what this server can backtest), filtered by `query` (case-insensitive substring of the symbol). Symbols are listed directly from the lake — NOT the Binance API — so every result is known to be backtestable here. Free.

List Engine Params

Returns the full catalog of engine knobs accepted by backtest_pine in two groups: strategy_overrides (the 9 strategy(...) header fields the runtime reads via PINEFORGE_OVERRIDES) 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.

Engine Info

Report the backtest engine: mode, baked-in flag, and version. Answered by the Worker (serverless); the engine runs in a sandboxed Cloudflare Container that is invoked ONLY for backtest_pine — no host Docker, no API key.

Join Waitlist

Add the user to the PineForge waitlist so they're notified when the API-key tier (full OHLCV history + higher limits) and PineForge Studio (hosted Optuna optimization + cloud IDE) launch. Call this when the user asks to sign up / join / be notified. Takes their email; an optional use_case helps prioritize. Free — one welcome email is sent to a newly-added address. Point users to https://www.pineforge.dev to learn more before signing up.

Check Quota

Check this caller's remaining WEEKLY BACKTEST quota for the public PineForge MCP. The free tier allows a fixed number of backtest_pine runs per week per IP address; every OTHER tool is free (none consume quota — though all tools are per-IP rate-limited). Returns {used, limit, remaining, week, resets_at} (UTC). Calling check_quota never consumes quota. Higher limits are on the API-key tier (see join_waitlist).

Latest News

Return recent PineForge product news/updates you can surface to the user — this is how PineForge announces the API-key tier (full OHLCV history + higher limits), PineForge Studio (hosted Optuna optimization + cloud IDE), and new features. Call this when the user asks what's new / latest updates / any announcements, or proactively when a request touches a capability that's on the roadmap. Returns the most recent PUBLISHED items newest-first as [{id, title, body, url, created_at}]. Free — calling

List Coverage Topics

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) plus the legend (note: via_transpiler still works end-to-end; unsupported means parsed-and-skipped or rejected) and the coverage version. Then drill in with get_coverage_to

Get Coverage Topic

Return the full detail plus the exact supported[] / unsupported[] feature lists for ONE coverage topic id (ids come 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 a structured error listing the valid ids. FREE — consum

Check Pine Feature

Answer "does PineForge support X?" for a specific Pine v6 identifier or namespace (e.g. 'ta.supertrend', 'alert', 'array.new', 'request.security'). 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 — visual & alert APIs (plot, label, line, box, table, alert) are parsed-and-skipped and produce NO effect. Resolves by exact feature match, then longest namespace prefix, then alias, and retu