PineForge-Codegen (pineforge-4pass/pineforge-backtest-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 9 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
74/100

PineForge-Codegen

Backtest PineScript v6 strategies locally from your AI agent: transpiles Pine to C++ and runs it on the deterministic, TradingView-validated PineForge engine via Docker. Tools for single backtests, parameter-grid sweeps, and Binance OHLCV fetch — no API key, data never leaves your machine.

→ pineforge-4pass/pineforge-backtest-mcp· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

pineforge-4pass

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configPINEFORGE_ALLOW_ANYWHEREohlcv_csv_path (relax with =1).
configPINEFORGE_DOCKER_TIMEOUT_MSHard kill for docker pull / docker run
configPINEFORGE_HOST_WORKDIR
configPINEFORGE_IMAGEImage (engine runtime + bundled codegen) used for transpile + backtest
configPINEFORGE_MAX_INLINE_BYTES
configPINEFORGE_PREFIX
configPINEFORGE_VERSION
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

12/12 tools missing one or more hints — transpile_pine (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); backtest_pine (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); backtest_pine_grid (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +9 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

2 tools perform destructive updates without destructiveHint — backtest_pine deletes at line 158 (rm(tmp, { recursive: true, force: true })); backtest_pine_grid deletes at line 280 (rm(tmp, { recursive: true, force: true }))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool test coverage

Only 0/12 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/pineforge-4pass/pineforge-backtest-mcp?variant=verified)](https://m8ven.ai/mcp/pineforge-4pass/pineforge-backtest-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 7715f9870e27304a36aa715a56046d1bfa0040cc
code hash: ca46aa1c61ca537e001cb410a9412342690f4086aa11824020eee552b9835475
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client