MetaTrader 5 connector

What it does and does not do

The connector reads balance, equity, margin, open positions and the order and deal history of the account it is attached to, and sends that data to your TCC account after pairing with a single-use code.

It does not send orders, does not modify stop or target, does not close positions and imports no DLL. There is no code path in the file that reaches a trading function — and that is verifiable in seconds, without taking our word for it.

It exists so the number does not depend on the firm: the balance and equity you see in TCC are the ones your broker's terminal reports, not the ones you typed. Account state is resent every two minutes while the chart is open, and a liveness ping every minute. Both numbers are in the code, in Include/TCCConfig.mqh, on the TCC_SYNC_SECONDS and TCC_HEARTBEAT_SECONDS lines — that is where you check them, not here.

The connector is on the free plan and costs nothing per connected account: if you follow three firms, you attach the EA to three terminals and still pay nothing for it. Elsewhere on the market, following an account anywhere near real time is either a toll or a chore — there are tools that charge a subscription per year and per account to remove the delay the free plan imposes, and tools that require a robot in the terminal plus a Windows server left running. Here what is required is your own MetaTrader, open on a chart.

How to verify it is read-only

The file is plain-text MQL5 source. Open it in MetaEditor or any text editor and search for these terms: OrderSend, OrderSendAsync, CTrade, PositionClose, PositionModify, OrderModify, #import. None of them appears in the connector code.

If any of those terms appears in a file someone handed you as the TCC connector, that file is not ours. Compare the SHA-256 before attaching anything to an account with money in it.

On Windows: certutil -hashfile TCCConnector.mq5 SHA256. On macOS or Linux: shasum -a 256 TCCConnector.mq5. The value must match the one published on this page exactly.

The full package has a published hash too, abfa0c4991ca75537b35687f4bc25c8c806f99b7723ad6e6c0b66250e43f530f, and it is reproducible: building the package again from the same source returns the same file, byte for byte. The installer checks every file's SHA-256 against the manifest before copying anything and refuses to install if a single one differs — it strengthens the check, it does not replace yours.

Pairing security

The link between terminal and your TCC account is made with a six to eight digit single-use code typed into the chart panel. The code is deliberately not an EA input: inputs are stored in preset files and leak with them.

The session token is bound to the account login and server. If either changes, the session drops on its own and pairing must be redone. Revocation is also available at any time from the TCC panel.

Since version 0.23 the token is stored on your own computer, in the terminal data folder, so that closing MetaTrader does not demand a new code every time. Its scope is read-only: whoever read that file could send telemetry for that one connection and nothing more — no trading power, no broker access, no access to your TCC account. On return, the stored login and server must match the account on the chart and the server revalidates the token; any mismatch erases the file. If you prefer the old model, turn off the Restore session input and pair again at every restart.

Installation

Download the TCCConnector-0.30.zip package: 131 KB, 16 files, all of them text — there is no executable inside. They are the Expert Advisor, the twelve include files it needs in order to compile, the installer and a manifest with the SHA-256 of each one. The .mq5 alone does not compile: the first thing it does is include the other twelve.

On Windows the short path is to extract the package and run, inside the extracted folder: powershell -ExecutionPolicy Bypass -File instalar-tcc.ps1. The installer locates the terminal data folder, checks the hashes, copies the files and calls MetaEditor to compile. It is plain-text source with a published hash as well — for the same reason the EA is.

The -ExecutionPolicy Bypass is needed because the script carries no digital signature, and that is exactly why its SHA-256 is published here. Signatures and hashes solve the same problem by different routes: a signature asks you to trust a certificate authority, a hash you check yourself, and the second is what this whole page argues for.

Outside Windows the manual path is the only path: the installer is PowerShell and assumes Windows, so on macOS and Linux — and on Windows, if you prefer — copy TCCConnector.mq5 and the Include folder into MQL5/Experts in the terminal data folder and compile in MetaEditor with F7.

Both paths stop at the same place, and that is deliberate: allow https://tgsxkgabhiqpxcunybzi.supabase.co under Tools › Options › Expert Advisors › "Allow WebRequest for listed URL". MetaTrader keeps that list encrypted precisely so that no program can authorize itself to reach the internet. No installer, ours or anyone else's, can take that step for you — if one could, the protection would not exist.

Finally, drag the EA onto any chart of the account you want to track and type the pairing code into the panel. One chart per account is enough: the connector reads the whole account, not the chart symbol.

Version history

0.23 — session restore when the terminal reopens, with fail-closed validation: login and server must match the current account and the first heartbeat confirms the token on the server.

0.20 — cursor reconciliation before any historical batch: no history starts until the server confirms how far it already received.

0.15 — on-chart panel with a pairing code field; the code stopped being an EA input so it is never stored in a preset file.

0.10 — first public read-only release: account, positions, orders and deals read and sent to TCC after pairing.