mcp-metatrader5-server@0.1.8
VERIFIED· not startedPublisher claims: "A Model Context Protocol (MCP) server for MetaTrader 5" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
MT5_PASSWORDConfiguration, not credentials: MT5_LOGIN, MT5_MCP_HOST, MT5_MCP_PORT, MT5_MCP_TRANSPORT, MT5_PATH, MT5_SERVER- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard. It asks for MT5_PASSWORD and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-08 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
# Load environment variables from .env file if it existsFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Load environment variables from .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Make sure the server is running: uv run mt5mcp (with MT5_MCP_TRANSPORT=http in .env)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.print(" Check your credentials in .env file")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Example: I'm always frustrated when [...]Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.MCP_SERVER_URL = "http://localhost:8000/mcp"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for mcp-metatrader5-server@0.1.8 as of 6d ago. This is the package itself, not its dependencies.