English Français العربية

Pine Script Strategy Audit

Registre officiel Sécurité

Static analysis for Pine Script v6 strategies — catches backtest-vs-live divergence traps.

Code source Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http pine-script-strategy-audit 'https://pinescript-audit-mcp.mcpize.run/mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "pine-script-strategy-audit": {
            "type": "http",
            "url": "https://pinescript-audit-mcp.mcpize.run/mcp"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. pinescript-audit-mcp
  2. The problem this solves
  3. What it catches
  4. Tools
  5. Use it
  6. Part of the AlgoForge suite
  7. License

pinescript-audit-mcp

An MCP server that statically audits Pine Script v6 strategies for the specific traps that compile clean, backtest beautifully, and then diverge from live behavior.

The problem this solves

Pine Script strategies can compile with zero errors and still behave differently live than in the backtester — fill-timing assumptions, ATR-smoothing mismatches, lookahead bias, VWAP-anchoring drift, and exit-drift are all silent, syntactically valid patterns that the compiler has no reason to flag. This catches them before they cost real money finding out live.

What it catches

  • Fill-timing traps — orders that backtest as filling at a price/bar the live broker can't actually match
  • ATR-smoothing mismatches — RMA vs. SMA vs. EMA smoothing assumptions that quietly change signal timing
  • Lookahead bias — request.security() and similar calls that leak future bar data into historical evaluation
  • VWAP-anchoring drift — anchor-period assumptions that behave differently on session boundaries live vs. in backtest
  • Exit-drift — exit logic that behaves differently depending on calc_on_every_tick and bar-close assumptions
  • Pine v6 syntax traps — v6-specific footguns that compile but change behavior from v5 equivalents

Tools

audit_pine_strategy

Runs the full static-analysis pass against a submitted Pine Script v6 strategy and returns every trap found, with the specific line and a plain-English explanation of the backtest-vs-live divergence it causes.

Use it

Hosted (recommended): MCPize — free tier, paid Pro tier for higher limits.

Self-host:

npm install
node server.js

Part of the AlgoForge suite

Prop-firm and quant-validation tools for algo traders: prop-rules-mcp, trade-journal-mcp, payout-calc-mcp, econ-calendar-mcp, montecarlo-validator-mcp, overfitting-audit-mcp, walkforward-validator-mcp, backtest-cost-sensitivity-mcp, pinescript-mcp.

License

MIT

Questions fréquentes

Qu'est-ce que Pine Script Strategy Audit ?

Static analysis for Pine Script v6 strategies — catches backtest-vs-live divergence traps.

Comment installer Pine Script Strategy Audit ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http pine-script-strategy-audit 'https://pinescript-audit-mcp.mcpize.run/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Pine Script Strategy Audit ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

Pine Script Strategy Audit est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Pine Script Strategy Audit ?

Il est publié par tylerscomic-lab. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.