Skip to system research
Build A Trading SystemRules / Evidence / Replay

MQL5 Signals assessment

A scoped assessment of MQL5 Signals for Build A Trading System. Public documentation and evidence limits, not a performance score.

Original edition: 8 October 2026. Source limits appear below. Expanded edition: 13 October 2026.

Educational research design and invented arithmetic examples. No strategy returns, broker execution or production certification are supplied.

What is being assessed

Platform-mediated copying. Review the exact provider account, signal subscription and subscriber settings. Official documentation explains copying, volume conversion and synchronisation, not the merit of every seller.

System-building lens

Decide whether the service supplies data, a research environment, a signal condition or execution. Freeze the relevant settings and test your own order lifecycle. Tool capability is not a substitute for an independently evaluated economic hypothesis.

Evidence and limits

Inspect differences in broker, leverage, account currency, volume steps and reconnect behaviour. A source-account result and a subscriber result need different evidence.

Before relying on it

Save the exact product page and current terms, record what the source actually supports and list questions that remain open. No paid-account experiment, observed return, performance score or universal finding about all sellers on this platform is claimed.

Sources and scope

Copying preserves another account identity

MetaTrader's subscriber documentation describes a copying mechanism. The source account and receiving account can have different volumes, currency, broker conditions and transaction records, so the source's result cannot automatically label the receiver. A builder should retain the selected signal, receiving settings and reconnect policy before interpreting actual state. This desk has not connected a paid subscriber account or performed a live recovery test. Documentation supports a workflow description, not independent approval of every strategy or an assurance that account quantities and exits exactly replicate a leader's history.

Completed fictional restart question

An invented copy worker times out during a receiving action. The local record lacks acknowledgement, while the source instruction remains present. Resending without authoritative account reconciliation could duplicate an intended action in a generic system; the example does not allege an actual platform failure. The next source request is the receiver's order and position state under its real API contract. A static library replay over invented bars cannot test that uncertainty. Stable instruction IDs, broker IDs, partial fills, cancellation status and the effective recovery owner would be needed for a stronger operational finding.

Keep research and subscriber outcomes distinct

A complete economic study requires the eligible source and receiving populations, actual fills, costs, conversion and original risk policy. Current selected access and account eligibility need official terms. The platform name alone does not establish permitted financing, suitable quantity or an authoritative exit owner. No actual copied return, user-review count, paid tester or financial winner was supplied. The release workbench can retain these missing fields without an invented certification score. A documented copying mechanism and a verified deployed receiving route are separate findings with different sources.

Primary references and scope

Expanded source review: 13 October 2026. Documentation supports the stated mechanism, not a tested account, hypothetical fill or provider outcome.