MetaTrader 5 MCP Server

The materials state that no keys or environment variables are required, and there is no explicit request for API tokens or other sensitive secrets. However, trading-related actions may implicitly rely on a locally logged-in MetaTrader 5 session, with no documented isolation or permission boundaries.

The description explicitly mentions interaction via HTTP/ngrok, indicating network communication capability. Although no fixed remote endpoint is listed in the metadata, ngrok may expose a local service externally, creating outbound data flow and remote access surface; the documentation does not specify target endpoints or transport protections.

The system flags this tool as executes-code, indicating that it runs a local service or related code on the host. This is a common MCP capability, but the materials do not describe execution boundaries, accessible system capabilities, or how it interacts with MetaTrader 5 processes.

Its stated functions include market data access and trade management, implying access to trading-terminal data such as quotes, positions, or orders, and possibly the ability to place trades. The available materials do not define the exact read/write scope, log locations, or whether access is restricted to a specific account or terminal instance.

A positive factor is the presence of a public source repository, which is more auditable than closed source. However, it comes only from a third-party registry, has no declared license, no README, zero stars, and unknown maintenance status, which weakens trust and ongoing security assurance; avoid using it in real trading environments before reviewing the source and dependencies.