Connection checks
A cloud page is connected: is my local trading terminal connected too?
Check where the connector runs, which account it observes and how recent its evidence is. A cloud login and a local terminal are different connections.
Check where the connector runs, which account it observes and how recent its evidence is. A cloud login and a local terminal are different connections.
A web portal can load while the customer's terminal is stopped. A local connector can be running while it observes the wrong terminal or account. Separate web access, connector access and broker-account evidence when diagnosing a connection. Describe each state with its own identity and observation time.
Name the endpoint and its machine
MetaTrader's documentation separates terminal, marketdata and MetaEditor MCP servers. The terminal endpoint can expose account and order-management tools; the remote marketdata endpoint supplies market information. MetaQuotes Python initialize connects to a MetaTrader terminal executable. These interfaces are different from simply logging into a cloud website.
A loopback address such as 127.0.0.1 refers to the machine making the connection. A cloud process cannot use its own loopback address to reach a terminal on your computer. An authorized connector or hosted terminal needs a separately verified route. Do not expose the full terminal interface on an unauthenticated public address to bridge that gap.
Check identity before interpreting a badge
- Identify the machine and terminal installation that the connector is intended to observe. Keep sensitive paths and connection details in the protected setup record.
- Read the terminal's connection state and the account's identity through the approved narrow read interface. Match server, account environment and owner; matching a broker name alone is insufficient.
- Record the observation time and distinguish current evidence from a cached result. A page refresh does not prove that the underlying terminal or account was reread.
- Check which tools and permissions are actually exposed. Account/history reads do not require granting arbitrary shell, editor or trading access.
- If the machine, terminal, account or credential changes, stop treating the old evidence as current. Complete the approved setup and review again before considering execution.
During a connector outage
Mark the observations stale and avoid inferring that the broker account is empty. A stopped connector does not itself close positions or cancel pending orders. Use an authorized account interface for inspection and follow the original-operation recovery process for uncertain requests. Do not reboot a connector as a way to recreate an unknown order.
Source check · 5 October 2026
MCP roles: https://www.metatrader5.com/en/terminal/help/mcp_and_ai/configuration and https://www.metatrader5.com/en/terminal/help/mcp_and_ai/capabilities . Terminal/account reads: https://www.mql5.com/en/docs/python_metatrader5/mt5terminalinfo_py and https://www.mql5.com/en/docs/python_metatrader5/mt5accountinfo_py . Initialization: https://www.mql5.com/en/docs/python_metatrader5/mt5initialize_py . The identity checklist is TradeTwin guidance, not an installation acceptance test.
Questions worth asking
Does the remote marketdata MCP endpoint control my account?
Its documented role is market information. Treat account and order-management access as a separate terminal connection with its own identity and permissions.
Does closing my laptop prove all positions are closed?
No. Machine availability and broker-account state are separate. Inspect account evidence through an authorized path rather than infer a financial outcome from a local outage.
Primary documentation for further reading
- MetaTrader MCP configuration
- MetaTrader MCP capabilities
- MetaQuotes Python terminal initialization
- MetaQuotes terminal information
- MetaQuotes account information
API documentation describes the provider's interface. It does not certify your account or TradeTwin connector as ready to trade.