Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CloudCorpRecords/backtestport

OCI · GHCR.IO/CLOUDCORPRECORDS/BACKTESTPORT · 2 COMPONENTS

Backtesting engine client: indicators, strategy validation, backtests, signals and market data.

40 Trust /100

Last scanned (4 hours ago)

Scores higher than 41% of OCI servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 837 tokens (~44/item across 19 items; 19 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 39

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/backtestport@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 19 exposed · ~837 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_backtests ~83

Run several strategies on the same data, side by side.

NameTypeReqDescription
includearray–Sections to include in the response (optional).
max_series_pointsinteger–Maximum number of series points to return (optional).
response_detailstring–Level of detail for the response (optional).
strategiesarrayyesStrategy definitions or identifiers to compare.

No output schema declared.

No examples provided.

compute_stats ~30

Compute the metric set from an externally produced returns series.

NameTypeReqDescription
returnsarrayyesSeries of returns values.

No output schema declared.

No examples provided.

engine_info ~16

Engine version, API contract, health.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_catalog ~39

Reference catalogs: operators, execution modes, stop types, sizing methods, bar frequencies, metric sections.

NameTypeReqDescription
catalogstring–Catalog name to retrieve.

No output schema declared.

No examples provided.

get_data_range ~35

Available history and bar-count estimate for a symbol.

NameTypeReqDescription
symbolstringyesTicker symbol, e.g. AAPL.

No output schema declared.

No examples provided.

get_latest_signal ~55

Evaluate the most recent bar only (no P&L).

NameTypeReqDescription
strategyobject|stringyesStrategy definition, as an object or a JSON string.
symbolstring–Ticker symbol, e.g. AAPL.

No output schema declared.

No examples provided.

get_macro_series ~59

Fetch one macro series' observations.

NameTypeReqDescription
endstring–End date for the range (ISO 8601).
seriesstringyesSeries identifier.
startstring–Start date for the range (ISO 8601).

No output schema declared.

No examples provided.

get_me ~26

What the configured key can do: permission scopes, limits, current usage, capability flags.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_price_history ~85

OHLCV price history over a date range.

NameTypeReqDescription
endstring–End date for the range (ISO 8601).
frequencystring–Bar frequency, e.g. daily or weekly.
startstring–Start date for the range (ISO 8601).
symbolstringyesTicker symbol, e.g. AAPL.

No output schema declared.

No examples provided.

get_quote ~31

Latest available price for a symbol.

NameTypeReqDescription
symbolstringyesTicker symbol, e.g. AAPL.

No output schema declared.

No examples provided.

get_strategy_schema ~15

JSON Schema for strategy documents.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_ticker_info ~36

Symbol identity and data coverage in a single call.

NameTypeReqDescription
symbolstringyesTicker symbol, e.g. AAPL.

No output schema declared.

No examples provided.

list_indicators ~30

Indicator discovery; per-indicator parameter schemas.

NameTypeReqDescription
searchstring–Search text filter (optional).

No output schema declared.

No examples provided.

list_macro_series ~16

List the macroeconomic series catalog.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_templates ~43

Predesigned strategy templates — discover compactly, fetch one in full, ready to validate and run.

NameTypeReqDescription
idstring–Identifier of the record to operate on.

No output schema declared.

No examples provided.

list_tickers ~16

List the fetchable symbol universe.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

run_backtest ~156

Run a backtest of a strategy over historical data for the given symbol and date range.

NameTypeReqDescription
dataobject–Data payload for this call.
endstring–End date for the range (ISO 8601).
includearray–Sections to include in the response (optional).
max_series_pointsinteger–Maximum number of series points to return (optional).
response_detailstring–Level of detail for the response (optional).
startstring–Start date for the range (ISO 8601).
strategyobject|stringyesStrategy definition, as an object or a JSON string.
symbolstring–Ticker symbol, e.g. AAPL.

No output schema declared.

No examples provided.

search_tickers ~26

Search the fetchable symbol universe.

NameTypeReqDescription
querystringyesSearch query text.

No output schema declared.

No examples provided.

validate_strategy ~40

Validate a strategy without running it — returns structured, locatable errors.

NameTypeReqDescription
strategyobject|stringyesStrategy definition, as an object or a JSON string.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/backtestport MCP server?

io.github.CloudCorpRecords/backtestport runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/backtestport:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/cloudcorprecords/backtestport

# add to Claude Code
claude mcp add cloudcorprecords-backtestport -- docker run --rm -i ghcr.io/cloudcorprecords/backtestport:0.1.0
Common questions

What is the io.github.CloudCorpRecords/backtestport MCP server?

io.github.CloudCorpRecords/backtestport is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/backtestport. Backtesting engine client: indicators, strategy validation, backtests, signals and market data. This page covers its container image (ghcr.io/cloudcorprecords/backtestport).

Is the io.github.CloudCorpRecords/backtestport MCP server safe to use?

io.github.CloudCorpRecords/backtestport scores 40 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.CloudCorpRecords/backtestport MCP server expose?

io.github.CloudCorpRecords/backtestport exposes 19 tools: engine_info, get_me, get_catalog, list_indicators, list_templates, and 14 more. Their descriptions and schemas cost roughly 837 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/backtestport MCP server still maintained?

io.github.CloudCorpRecords/backtestport is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.CloudCorpRecords/backtestport MCP server under?

io.github.CloudCorpRecords/backtestport declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.