MT5 build 6230: MCP returns zero tick fields and inconsistent UTC offset
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Hello MetaQuotes team and MQL5 community,
I need clarification about the native MT5 MCP interface in terminal build 6230.
Saved observations for XAUUSD_ on October 19, 2026 show the following:
• At 15:07:43 Kuwait time (UTC+3), successful, synchronized native MQL calls returned tick_size=0.001 and tick_value/profit/loss=0.10000000000000001, with LastError=0.
• A later get_marketwatch_symbols response, captured by 15:20:45 Kuwait time, returned tick_size=0.00000000 and tick_value=0.00000000. Quotes had changed, and update_time was 15:20:39.
• get_time_information returned utc_time=12:20:45Z, local_time=15:20:45, and local_utc_offset_minutes=0.
These observations were not simultaneous. The zero values were present in the received response before local JSON parsing, and no root cause is assumed.
Could you please clarify:
What sources, units, calculation rules, refresh/cache behavior, and zero/error defaults are used for the MCP tick fields, including symbols using CFD_LEVERAGE?
What are the clock sources, offset sign convention, DST semantics, and historical time/time_ms serialization rules?
Are there any known issues affecting these fields in build 6230? If so, please identify the affected/fixed builds and relevant documentation.
Is there a supported way to inspect the existing connection’s serverInfo.name/version, protocolVersion, and any separately versioned MetaQuotes transport component without reconnecting, changing permissions, or exposing credentials or account data?
Please provide documentation or an existing sanitized trace if available. The native diagnostic has already been completed; this request is for clarification rather than another diagnostic run.
Thank you.