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.

Backtester

REMOTE · BACKTESTER.DAENADIGITAL.COM

Test a plain-words trading rule on historical prices and compare the trades with SPY. Not advice.

+3 this week 62 Trust /100

Last scanned (14 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability38
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 771 tokens (~70/item across 11 items; 9 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 15 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 11 Nov 26 +1

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

  • 9 Nov 26 +1
    • Tool “save_strategy” rewrote its description, which is the text the model reads security
    • Tool “share_report” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • Destructive annotations: 100 → pass functional
    • Tool “build_series” changed its title: Build data series cosmetic
    • Tool “build_signal” changed its title: Build trading signals cosmetic
    • Tool “get_prices” changed its title: Get historical prices cosmetic
    • Tool “list_data” changed its title: List available data cosmetic
    • Tool “list_strategies” changed its title: List saved strategies cosmetic
    • Tool “report” changed its title: Run a backtest report cosmetic
    • Tool “save_strategy” changed its title: Publish a report to the public website cosmetic
    • Tool “share_report” changed its title: Share a report publicly cosmetic
    • Tool “simulate” changed its title: Simulate past trades cosmetic
  • 8 Nov 26 56

    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 21 Nov 2026 · Probed https://backtester.daenadigital.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=daenadigital.com CN=WE1,O=Google Trust Services,C=US 2 Nov 2026 31 Jan 2027 ECDSA 256 ECDSA-SHA256 13106725b176432b0e17c03418eb9660
SANs: daenadigital.com, backtester.daenadigital.com, *.backtester.daenadigital.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of backtester.daenadigital.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
daenadigital.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://backtester.daenadigital.com/mcp Verified 200
http (plaintext) http://backtester.daenadigital.com/mcp HTTPS enforced 301 https://backtester.daenadigital.com/mcp
MCP tools · 9 exposed · ~756 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
build_series ~32

Build named time series from a run form. Needs version, data, and series.

NameTypeReqDescription
runobjectyes–

No output schema declared.

No examples provided.

build_signal ~34

Build named trading signals from a run form. Needs version, data, series, and signals.

NameTypeReqDescription
runobjectyes–

No output schema declared.

No examples provided.

get_prices ~29

Read historical prices for a run form. Needs only version and data.

NameTypeReqDescription
runobjectyes–

No output schema declared.

No examples provided.

list_data ~28

List available price data, fields, dates, limits, and whether reports can be retained for publishing.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_strategies ~41

List published website strategies, their URLs, and their current keys. Use a current key as expectedKey only when the user asks to replace that saved strategy.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

report ~259

Run a backtest and show its results. Supply strategyExplanation in plain terms for the widget. In your reply, explain the rule, always show Return vs. SPY (summary.returnVsSpyPct in percentage points, or Unavailable), and give one takeaway or limit supported by the report. Choose any additional cards using stats. Use scoreSeries for a separate score panel. Use chartSeries to select named report series and set their legend labels, line or bar types, colors, and line patterns. Keep the interpretation about this historical test. To publish this exact result later, pass its reportId to save_strategy after the user asks to save it to the website.

NameTypeReqDescription
chartSeriesarray–Additional price-panel plots. Reference named engine report series. Set a legend label, line or bar type, line pattern, and optional hex color.
runobjectyes–
scoreSeriesstring–Named report series to draw in the separate score panel.
statsarray––
strategyExplanationstring–In 1 to 3 plain sentences, explain what the strategy trades, what triggers buys and sells or rebalancing, and one key assumption when relevant. Use the run rules. Leave historical results for the rep…

No output schema declared.

No examples provided.

save_strategy ~208

PUBLIC: anyone can see the saved page. Publish a completed report to the public website after the user asks to save it. Use the reportId returned by report, a public slug, and client-authored page and presentation choices. Never submit or invent result numbers. Adds it to the strategy directory without rerunning the strategy. Existing slugs require expectedKey to replace a different result. setAsHome changes the home page only when explicitly requested.

NameTypeReqDescription
expectedKeystring–Current published key, required only when replacing a different saved result at this slug.
idstringyesPublic page slug. New slugs add a page; existing slugs require expectedKey to replace.
pageobjectyes–
presentationobjectyes–
reportIdstringyesThe reportId returned by report. Do not submit prices, trades, or statistics.
setAsHomeboolean–Also select this strategy for the home page. Otherwise preserve the current home strategy.

No output schema declared.

No examples provided.

share_report ~97

PUBLIC: the report is listed in the public strategy library, and anyone can see it. Make a report public so it can be shared, and return its page URL. Needs only the reportId returned by report. The page text comes from the report itself. Sharing the same report again returns the same URL. The report widget calls this when the visitor presses its share icon.

NameTypeReqDescription
reportIdstringyesThe reportId returned by report.

No output schema declared.

No examples provided.

simulate ~28

Simulate historical fills and account balances. Needs the full run form.

NameTypeReqDescription
runobjectyes–

No output schema declared.

No examples provided.

Install

How do I install the Backtester MCP server?

Backtester is a hosted endpoint at https://backtester.daenadigital.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · backtester.daenadigital.com

# add to Claude Code
claude mcp add --transport http morshedgit-backtester 'https://backtester.daenadigital.com/mcp'
Common questions

What is the Backtester MCP server?

Backtester is an MCP server listed in the public MCP registry as io.github.morshedgit/backtester. Test a plain-words trading rule on historical prices and compare the trades with SPY. Not advice. This page covers its hosted endpoint (https://backtester.daenadigital.com/mcp).

Is the Backtester MCP server safe to use?

Backtester scores 62 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 Backtester MCP server expose?

Backtester exposes 9 tools: list_data, get_prices, build_series, build_signal, simulate, and 4 more. Their descriptions and schemas cost roughly 756 tokens of context every time the server is loaded.

Does the Backtester MCP server require authentication?

No. We connected to Backtester without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Backtester MCP server still maintained?

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

What did VerifyMCP test on the Backtester MCP server?

VerifyMCP ran 14 checks on Backtester, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.