Skip to content
anlyon.devby Anlyon

EA Trade Tester by TrueTest MCP server

uk.truetest/ea-testertruetest.ukstreamable-httpv1.0.2Scanned

FREE first read, no sign-up: test an EA, trading bot, indicator or MT4/MT5 report for luck and costs

3 tools: 2 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. anlyon.dev only lists and labels, and these labels are the same either way.

Compare with similar serversMarkdownJSONReport this listing

What the EA Trade Tester by TrueTest MCP server can do

The EA Trade Tester by TrueTest MCP server is published by truetest.uk, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: check_trading_record and test_strategy_code), but cannot delete data. 1 tool only reads.

1 tool reads private data (test_strategy_code).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since anlyon.dev first saw them.

Last scanned Nov 12, 2026, version 1.0.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 2Claude Code: ask
  • check_trading_recordJudges whether a finished trading record's results look real or like luck: reads the trades, applies a luck test that allows for the number of versions tried, checks costs, losing …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Judges whether a finished trading record's results look real or like luck: reads the trades, applies a luck test that allows for the number of versions tried, checks costs, losing years and grid/martingale signs, and returns a verdict (REAL / PROMISING / LIKELY_LUCK / NO_EVIDENCE / FAIL / HIDDEN_RISK / TOO_FEW) with its reason. Use it for a record of trades already taken or backtested; for strategy code or written rules use test_strategy_code. Nothing is stored: the record is read as data, never run, and discarded after the answer.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Check a trading record (MT5 report, statement or CSV)
  • test_strategy_codeReads trading-strategy code - an MT5/MT4 Expert Advisor or indicator (.mq5/.mq4/.mqh/.set), a Python trading bot (.py), a TradingView Pine Script (.pine), a cTrader cBot or NinjaTr…Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.

    What it can reach

    • private-dataThe description's first sentence says "read" and "file": it reads files.
    • private-dataThe input names a file (input.files), and the tool reads: it reads files.
    Description, as the server wrote it
    Reads trading-strategy code - an MT5/MT4 Expert Advisor or indicator (.mq5/.mq4/.mqh/.set), a Python trading bot (.py), a TradingView Pine Script (.pine), a cTrader cBot or NinjaTrader strategy in C# (.cs) or rules written in plain words (.txt) - and reports code faults: wrong server clock, modules never called, settings never used, missing include files, unchecked orders, martingale or grid sizing. Without an email it returns this free first read only and stores nothing. With the user's email it also opens a private Strategy Lab and returns its link: TrueTest rebuilds the strategy as plain-English rules, the user checks them on the lab page, then TrueTest backtests its own rebuilt copy on up to 16 years of prices with real costs, runs a luck check and keeps a forward watch. It never runs the uploaded code as given and never places trades. For a finished trade record use check_trading_record; compiled .ex5/.ex4 files cannot be read (test their Strategy Tester report instead). Files are kept up to 90 days; the lab 12 months after the user's last visit (https://truetest.uk/security).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Test trading-strategy code (EA, indicator, Python bot, written rules)
Only reads 1Show 1 read-only tool
  • get_lab_statusReturns where a Strategy Lab stands - waiting for the rule card, waiting for the user's check, queued, running, done or watching forward - with the place in the queue, a rough wait…No findings

    Why it is in this group

    • The name "get_lab_status" says "get": a word for reading.
    Description, as the server wrote it
    Returns where a Strategy Lab stands - waiting for the rule card, waiting for the user's check, queued, running, done or watching forward - with the place in the queue, a rough wait, and once tested the verdict and its reason. Use it when the user asks how their test is going. It changes nothing in the lab; a look counts as a visit, which keeps the lab for 12 more months.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Get a Strategy Lab's status and result

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 11, 2026, 09:20 UTC, unchanged since Nov 11, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://truetest.uk/mcp: tools/list returned 3 tools to an anonymous client, including check_trading_record (write), test_strategy_code (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. Tools1 changed.~1 changedView diff
All changes to this server

Install

Pinned to version 1.0.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http ea-tester https://truetest.uk/mcp
claude mcp add --transport http ea-tester https://truetest.uk/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ea-tester__get_lab_status"
    ],
    "ask": [
      "mcp__ea-tester__check_trading_record",
      "mcp__ea-tester__test_strategy_code"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ea-tester. Review it before you use it.

Capability tags behind 1 rule
  • mcp__ea-tester__test_strategy_code private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/uk.truetest/ea-tester/verify?hash=7ce9bd36ec0ced58ab66aee3d62b92796165ffaf62bba87ab43f011a8bb4ecba" | jq -e '.changed == false'

Pinned hash 7ce9bd36ec0c, from Nov 12, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/uk.truetest/ea-tester/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for uk.truetest/ea-tester
[![anlyon.dev](https://anlyon.dev/badge/uk.truetest/ea-tester.svg)](https://anlyon.dev/servers/uk.truetest/ea-tester)

Source: MCP Registry · repository. Synced Nov 12, 2026, 19:18 UTC.

EA Trade Tester by TrueTest MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the EA Trade Tester by TrueTest MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the EA Trade Tester by TrueTest MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the EA Trade Tester by TrueTest MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the EA Trade Tester by TrueTest MCP server have?

3 tools: 2 write, 1 read. check_trading_record, test_strategy_code and get_lab_status.

Does the EA Trade Tester by TrueTest MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the EA Trade Tester by TrueTest MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the EA Trade Tester by TrueTest MCP server changed its tools?

Yes, 2 times since anlyon.dev started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.