backtest360SAFE
MCP server exposing the Backtest360 engine API as tools for AI agents.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://pypi.org/project/backtest360-mcp/) [](https://pypi.org/project/backtest360-mcp/) [](LICENSE) [](https://github.com/Backtest360/backtest360-mcp/actions/workflows/test.yml)
MCP server exposing the Backtest360 engine API as tools for AI agents.
Connect any MCP-capable AI client and drive real backtests conversationally: discover indicators, build and validate strategies, run backtests, and read the results — all against the deterministic Backtest360 engine. The server contains no AI and computes no numbers of its own; it is a thin, faithful adapter over the engine HTTP API. Your engine API key and its plan govern everything (permissions, rate limits, data access).
Two transports: a hosted HTTP endpoint at https://mcp.backtest360.com/mcp (send your key as an X-API-Key header) and local stdio (self-host — see below).
Install
pip install backtest360-mcp # or, from a clone: pip install -e .
Requires Python 3.10+ and a Backtest360 API key. Get one free, instantly at backtest360.com/api-access — submit your email and a key (format b360_...) is issued on the spot and emailed to you; no approval needed. Authentication is API-key only. The free tier runs backtests on data you upload; fetching historical price data from the engine server-side is a paid capability.
Configuration
Everything is environment-driven:
69e6bc6b1aa6OBSERVED · 2026-10-10Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add backtest360-mcp --env BACKTEST360_API_KEY=${BACKTEST360_API_KEY} -- None backtest360-mcp==0.5.0Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (4 observation(s))
- Shell
- declared (1 observation(s))
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (5)
module = importlib.import_module(_GUARDED_PACKAGE)
.gitleaks.toml
assert base64.b64decode(out["content_base64"]) == b"PK\x03\x04fake-xlsx"
sudo install /tmp/gitleaks /usr/local/bin/gitleaks
Gates applied: no_behavioural_pass.
69e6bc6b1aa6full audit observations/trust-audit/mcp-server/backtest360__backtest360-mcp.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-10 | 69e6bc6b1aa6 | SAFE | B | 89 | first audit |
Questions
What is the backtest360 MCP server?
MCP server exposing the Backtest360 engine API as tools for AI agents.
Is backtest360 safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does backtest360 need?
It reads BACKTEST360_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does backtest360 run?
It speaks stdio and streamable-http, so it runs as a local process your client starts. It is published on PyPI as backtest360-mcp.
How current is this page?
The grade is for one exact copy of the source (69e6bc6b1aa6), read on 2026-10-10. The repository is watched and re-audited when it changes.