# Backtester (remote · backtester.daenadigital.com)

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

- Trust score: 62/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `backtester.daenadigital.com`: 62/100 (this document), [markdown](https://verifymcp.io/servers/morshedgit-backtester/backtester.md), [page](https://verifymcp.io/servers/morshedgit-backtester/backtester)

## Channel facts

- Endpoint: `https://backtester.daenadigital.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (save_strategy).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 38/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 771 tokens (~70/item across 11 items; 9 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## 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.

### Claude

```bash
claude mcp add --transport http morshedgit-backtester 'https://backtester.daenadigital.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "morshedgit-backtester": {
      "url": "https://backtester.daenadigital.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "morshedgit-backtester": {
      "type": "http",
      "url": "https://backtester.daenadigital.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.morshedgit-backtester]
url = "https://backtester.daenadigital.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "morshedgit-backtester": {
      "type": "remote",
      "url": "https://backtester.daenadigital.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add morshedgit-backtester --url 'https://backtester.daenadigital.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  morshedgit-backtester:
    url: "https://backtester.daenadigital.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "morshedgit-backtester": {
      "Transport": "http",
      "Url": "https://backtester.daenadigital.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add morshedgit-backtester -t streamable-http -u 'https://backtester.daenadigital.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "morshedgit-backtester": {
      "type": "http",
      "url": "https://backtester.daenadigital.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 62, +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.

### 2026-11-18 (score 61, +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.

### 2026-11-15 (score 60, +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.

### 2026-11-13 (score 59, +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.

### 2026-11-11 (score 58, +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.

### 2026-11-09 (score 57, +1)

- [security] 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
- [functional improvement] Stability: unverified → 0.03
- [functional] Destructive annotations: 100 → pass
- [cosmetic] 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

### 2026-11-08 (score 56)

First indexed and scored.

## MCP tools (9)

### `list_data` (~28 tokens)

List available data

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

### `get_prices` (~29 tokens)

Get historical prices

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

Input parameters:

- `run` (object, required)

### `build_series` (~32 tokens)

Build data series

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

Input parameters:

- `run` (object, required)

### `build_signal` (~34 tokens)

Build trading signals

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

Input parameters:

- `run` (object, required)

### `simulate` (~28 tokens)

Simulate past trades

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

Input parameters:

- `run` (object, required)

### `report` (~259 tokens)

Run a backtest report

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.

Input parameters:

- `chartSeries` (array): Additional price-panel plots. Reference named engine report series. Set a legend label, line or bar type, line pattern, and optional hex color.
- `run` (object, required)
- `scoreSeries` (string): Named report series to draw in the separate score panel.
- `stats` (array)
- `strategyExplanation` (string): 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…

### `share_report` (~97 tokens)

Share a report publicly

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.

Input parameters:

- `reportId` (string, required): The reportId returned by report.

### `list_strategies` (~41 tokens)

List saved strategies

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.

### `save_strategy` (~208 tokens)

Publish a report to the public website

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.

Input parameters:

- `expectedKey` (string): Current published key, required only when replacing a different saved result at this slug.
- `id` (string, required): Public page slug. New slugs add a page; existing slugs require expectedKey to replace.
- `page` (object, required)
- `presentation` (object, required)
- `reportId` (string, required): The reportId returned by report. Do not submit prices, trades, or statistics.
- `setAsHome` (boolean): Also select this strategy for the home page. Otherwise preserve the current home strategy.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/morshedgit-backtester/backtester#diagnostics

## Score history

- 2026-11-21: 62
- 2026-11-20: 62
- 2026-11-19: 61
- 2026-11-18: 61
- 2026-11-17: 60
- 2026-11-16: 60
- 2026-11-15: 60
- 2026-11-14: 59
- 2026-11-13: 59
- 2026-11-12: 58
- 2026-11-11: 58
- 2026-11-10: 57
- 2026-11-09: 57
- 2026-11-08: 56

## 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.

## Links

- Remote endpoint: https://backtester.daenadigital.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/morshedgit-backtester/backtester.xml
- Changelog JSON feed: https://verifymcp.io/servers/morshedgit-backtester/backtester/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/morshedgit-backtester/backtester.json
- HTML version of this page: https://verifymcp.io/servers/morshedgit-backtester/backtester
