Backtest MCP Server
@pineforge/backtest-mcp
npm
v0.9.30
Source verified
Published by pineforge-4pass — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Local MCP server: PineScript v6 → C++ + Docker backtest runner with parameter sweeps + Binance OHLCV exporter. Fully local (transpiler bundled in the engine image), no API key.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
high Shell/command execution in server code (dist/engine.js)MTC-SRC-002
In the server's implementation (`dist/engine.js:8`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: rt { spawn } from "node:child_process"; import { mkdtemp, writeFile, rm, readFile } from "node:fs/promises"; import { tm
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/engine.js
Tools 12
Each tool and what it can reach — statically extracted from the published source.
fetch_binance_ohlcvingests untrusted inputbacktest_pineno sensitive capabilitybacktest_pine_gridno sensitive capabilitybinance_symbolsno sensitive capabilitycheck_engine_imageno sensitive capabilitycheck_pine_featureno sensitive capabilityengine_infono sensitive capabilityget_coverage_topicno sensitive capabilitylist_coverage_topicsno sensitive capabilitylist_engine_paramsno sensitive capability
Show 2 more tools ↓
pull_engine_imageno sensitive capabilitytranspile_pineno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (12 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 5
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.9.30 latest |
A 94/100 | 1 | 1.13.0 | 2026-09-07 |
v0.9.27 |
A 94/100 | 1 | 1.13.0 | 2026-09-05 |
v0.9.26 |
A 94/100 | 1 | 1.12.1 | 2026-08-13 |
v0.9.24 |
A 100/100 | 1 | 1.5.0 | 2026-07-23 |
v0.9.22 |
A 100/100 | 1 | 1.5.0 | 2026-07-22 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @pineforge/backtest-mcp --onlineMore in Finance & Commerce
<img src="./public/logo.png" alt="1Money Logo" width="200"/>
Signed verification attestations for agent decisions: business, price, freshness, claim checks.
Actual Budget MCP server exposing API functionality
MCP server for Actual Budget - query and manage your personal finances through Claude
The Adyen Model Context Protocol server allows you to integrate with Adyen APIs through LLMs function calling utilizing various Clients. It currently supports the following tools:
Trusted agent-commerce hub: discover, trust-check, and route x402 payments with failover.