XTester does not open a separate MCP network listener.
"Local stdio" describes only the client-to-host transport and does not guarantee an entirely local or offline AI workflow. The MCP client or provider may transmit and store tool names and schemas, arguments, results, strategy excerpts, paths, logs and market-data excerpts.
Review your AI client's retention and telemetry settings; do not send credentials or private strategy source; minimise output; use a local model/client when data must not leave the device.
A claim that "data never leaves the device" is not allowed without end-to-end verification of the specific client, provider and configuration.
Consent and actions
The user explicitly confirms install and launch of the application.
A read-only connection check runs first.
Before mutating actions the agent confirms the workspace/project identity.
Remote writes and updates are described as requiring confirmation; the site does not assert runtime enforcement without testing a specific client/host.
XTester telemetry is optional (opt-in) and is enabled only with the user's consent in the application. Do not send credentials, strategy source or sensitive data in telemetry/support reports.
Conversion: source, rights and verification
Only source is accepted (a file, a folder or pasted code). Compiled .ex4, .ex5, .dll are not accepted and not decompiled.
Import requires an explicit rights confirmation (confirm_rights): the user confirms they have the right to use and port the supplied code. This records the user's responsibility; it is not a legal ownership check by XTester.
The result is verified, not declared identical. When a reference report exists (for example a CSV or a TradingView List of trades) a diff-test runs with a permitted per-bar tolerance, and the port gets one of the honest statuses: confirmed · conditionally confirmed · needs work · not confirmed. Without a reference report the status is "not confirmed". The word "equivalent" and any promise of identity with the original's results are not used.
A successful compile does not confirm the strategy's behavioural correctness.
Source is imported and stored locally. Data the external AI agent receives over MCP is processed per that client's and its LLM provider's settings; with a compatible local client and a local model, processing can run on the user's computer. Some functions — market-data download, GitHub, updates, a cloud LLM provider — may reach the network.
Conversion is not tied to live trading — the live path is a separate phase with its own confirmations.
