EA Trade Tester by TrueTest
REMOTE · TRUETEST.UK
FREE first read, no sign-up: test an EA, trading bot, indicator or MT4/MT5 report for luck and costs
Available components
Last scanned (16 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1327 tokens (~331/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
- Server version: 1.0.0 → 1.0.2 functional
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
- Schema quality: 374 → 331 ▲ functional
- New tool “get_record_check” functional
- “check_trading_record” reworded the description of “record_text” cosmetic
- Tool “check_trading_record” changed its title: Check a trading record (MT5 report, statement or CSV) → Check a trading record (MT4/MT5 report, statement or CSV) cosmetic
- 11 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- “test_strategy_code” reworded the description of “ai_draft” cosmetic
- 10 Nov 26 73
First indexed and scored.
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://truetest.uk/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=truetest.uk | CN=YE1,O=Let's Encrypt,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 61fd59b0a7c47b1cd23c48fececd5050e1c |
| SANs: truetest.uk | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of truetest.uk. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| uk. | DS published | 43876 | 8 | Verified |
| truetest.uk. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; font-src 'self'; img-src 'self' data:; connect-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self' https://checkout.stripe.com; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://truetest.uk/mcp | Verified | 200 | |
| http (plaintext) | http://truetest.uk/mcp | HTTPS enforced | 308 | https://truetest.uk/mcp |
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 →
check_trading_record Check a trading record (MT4/MT5 report, statement or CSV) ~345
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | – | The file's name, e.g. ReportTester.html or trades.csv (helps read the format) |
| is_forward | boolean | – | True if every trade in the record was taken after the strategy was fixed (a forward or live record) |
| name | string | – | Optional name of the strategy or EA |
| record_text | string | yes | Text of an MT4 or MT5 Strategy Tester report (HTML), an MT4/MT5 account statement (HTML), a cTrader, NinjaTrader, TradingView ('List of trades') or Myfxbook CSV export, or any CSV of closed trades (c… |
| versions_tried | integer | – | How many versions, settings or EAs were tried before this one, as stated by the user (it raises the luck bar) |
| Name | Type | Req | Description |
|---|---|---|---|
| evidence_scope | – | – | what the verdict shows and what it does not show |
| first | string | yes | – |
| good_points | – | – | what the record does well; it follows the verdict and its reason |
| hidden_risk_found | boolean | yes | – |
| last | string | yes | – |
| losing_years | integer | yes | – |
| luck_bar | number | yes | – |
| luck_counter | – | – | – |
| more | string | yes | – |
| next_step | – | – | – |
| note | string | yes | – |
| read | – | – | what was read from the record (trades, net, dates, currency, rows left out) |
| reason | string | yes | – |
| summary | string | yes | – |
| t_day_clustered | – | – | left out when the record has no spread of results to measure |
| trade_days | integer | yes | – |
| trades | integer | yes | – |
| verdict | string | yes | – |
| versions_tried | integer | yes | – |
| worst_day | – | – | info only: the largest daily loss, for scale (never a verdict input) |
No examples provided.
get_lab_status Get a Strategy Lab's status and result ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lab | string | yes | The private lab link from test_strategy_code or from a TrueTest email (https://truetest.uk/lab/...), or its 32-character code; 'demo' for the public sample lab |
| Name | Type | Req | Description |
|---|---|---|---|
| cost_estimate | – | – | present when the costs of some tested symbols are an estimate not yet checked against live prices: which ones |
| evidence_scope | – | – | once tested: what the result shows and does not show |
| forward_watch | – | – | – |
| good_points | – | – | once tested: what the rebuilt strategy does well; it follows the verdict |
| kept_at_least_until | – | – | a customer lab: the UTC date (yyyy-mm-dd) until which it is kept at least, under the current policy |
| kept_note | – | – | how long the lab is kept and what moves that date on |
| lab_url | string | yes | – |
| luck_counter | – | – | – |
| meaning | string | yes | – |
| note | string | yes | – |
| queue_length | – | – | queued or running: labs in the queue |
| reason | – | – | – |
| rebuild | – | – | present when the rebuild is not exact |
| rough_wait_minutes | – | – | queued or running: a rough wait |
| sample | – | – | present only for the public sample lab |
| status | string | yes | – |
| summary | string | yes | – |
| verdict | – | – | – |
| versions_tested | integer | yes | – |
| worst_day | – | – | info only: the largest daily loss, for scale |
No examples provided.
get_record_check Read a website result with its assistant code ~160
Reads the result of a trading record the user checked on the TrueTest website, by the assistant code shown with that result. Use it when the record is too big for check_trading_record (over about 700 KB): the user uploads the file at https://truetest.uk/strategy and gives the code. It returns the verdict and numbers the website showed; it changes nothing, cannot buy anything, and never returns the trades, the file name or the strategy's name.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The assistant code shown with a record-check result on https://truetest.uk/strategy, e.g. 1A2B-3C4D-5E6F-7A8B (dashes and spaces are ignored) |
| Name | Type | Req | Description |
|---|---|---|---|
| evidence_scope | – | – | what the verdict shows and what it does not show |
| first | string | yes | – |
| good_points | – | – | what the record does well; it follows the verdict and its reason |
| hidden_risk_found | boolean | yes | – |
| last | string | yes | – |
| losing_years | integer | yes | – |
| luck_bar | number | yes | – |
| luck_counter | – | – | – |
| more | string | yes | – |
| next_step | – | – | – |
| note | string | yes | – |
| read | – | – | what was read from the record (trades, net, dates, currency, rows left out) |
| reason | string | yes | – |
| summary | string | yes | – |
| t_day_clustered | – | – | left out when the record has no spread of results to measure |
| trade_days | integer | yes | – |
| trades | integer | yes | – |
| verdict | string | yes | – |
| versions_tried | integer | yes | – |
| worst_day | – | – | info only: the largest daily loss, for scale (never a verdict input) |
No examples provided.
test_strategy_code Test trading-strategy code (EA, indicator, Python bot, written rules) ~603
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).
| Name | Type | Req | Description |
|---|---|---|---|
| ai_draft | boolean | – | True only if the user agreed that our AI service may read the code text to draft the rule card. It is run by an outside AI provider, on servers in a country the UK has not approved for data protectio… |
| code | string | – | One file's text, if you are not using files |
| string | – | The user's email address, only if the user wants the full backtest: it identifies the user's tests for the luck bar and the 3-free-labs-a-day limit. TrueTest sends no email to it for a request made t… | |
| filename | string | – | That one file's name with its extension, e.g. MyEA.mq5. Give it whenever you have it; without it the language is guessed from the text. |
| files | – | – | All the strategy's files together, e.g. the .mq5 plus its .mqh includes and .set settings; at most 20 files and about 1 MB in total through this connector (larger: upload on https://truetest.uk/strat… |
| name | string | – | Optional name of the strategy |
| symbols | string | – | Optional symbols to test, e.g. EURUSD, GBPUSD, XAUUSD |
| timeframe | string | – | Optional timeframe, e.g. M15 or H1 |
| Name | Type | Req | Description |
|---|---|---|---|
| compiled | – | – | free first read: true if a compiled file was sent |
| files | – | – | free first read: the files read |
| findings | array | yes | – |
| lab_url | – | – | with an email: the private Strategy Lab link |
| language | – | – | free first read: the language read |
| next_step | – | – | compiled files only: what to send instead |
| note | string | yes | – |
| read_as_from_text | – | – | true when a file had no name with a known extension, so its language was guessed from its text (the summary says which) |
| reader_note | – | – | the code reader is busy: what that means for this upload |
| reference | – | – | with an email: the submission reference |
| rule_card | – | – | with an email: who writes the plain-English rule card |
| stored | – | – | free first read: always false (nothing is stored) |
| summary | string | yes | – |
No examples provided.
How do I install the EA Trade Tester by TrueTest MCP server?
EA Trade Tester by TrueTest is a hosted endpoint at https://truetest.uk/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 · truetest.uk
claude mcp add --transport http uk-truetest-ea-tester 'https://truetest.uk/mcp'
What is the EA Trade Tester by TrueTest MCP server?
EA Trade Tester by TrueTest is an MCP server listed in the public MCP registry as uk.truetest/ea-tester. FREE first read, no sign-up: test an EA, trading bot, indicator or MT4/MT5 report for luck and costs. This page covers its hosted endpoint (https://truetest.uk/mcp).
Is the EA Trade Tester by TrueTest MCP server safe to use?
EA Trade Tester by TrueTest scores 79 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 EA Trade Tester by TrueTest MCP server expose?
EA Trade Tester by TrueTest exposes 4 tools: check_trading_record, get_record_check, test_strategy_code, get_lab_status. Their descriptions and schemas cost roughly 1,247 tokens of context every time the server is loaded.
Does the EA Trade Tester by TrueTest MCP server require authentication?
No. We connected to EA Trade Tester by TrueTest without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the EA Trade Tester by TrueTest MCP server still maintained?
EA Trade Tester by TrueTest 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 EA Trade Tester by TrueTest MCP server?
VerifyMCP ran 13 checks on EA Trade Tester by TrueTest, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.