whitebit-mcp@2.1.2
VERIFIED· not startedPublisher claims: "MCP server that exposes the WhiteBIT exchange API as AI tools" 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
MCP_AUTH_TOKENWHITEBIT_API_KEYWHITEBIT_SECRET_KEYConfiguration, not credentials: MCP_HOST, MCP_PORT, WHITEBIT_BASE_URL- Where it talks to
- no vendor host named in the codeAlso whitebit.com, imoney24.technology — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- 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, and read the third-party hosts first. The code names whitebit.com, imoney24.technology as well as its own vendor. The guard injects MCP_AUTH_TOKEN, WHITEBIT_API_KEY, WHITEBIT_SECRET_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
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-21 and scored it 83/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
git remote set-url origin https://x-access-token:${ROBOT_GITHUB_TOKEN}@github.com/${{ env.TARGET_REPO }}.gitFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.f"\n[mcp_servers.{MCP_SERVER_NAME}.env]\n"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.RUN chown -R appuser:appuser /appFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.result = subprocess.run(cmd, capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.--exclude='.env' \Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.subprocess.run(cmd, capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.| Auth error | Ask user for new API keys, update `.env` |Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.subprocess.run(cmd, capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.- .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Spot trading — orders and kill switchFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."""Upsert [mcp_servers.whitebit] HTTP block in Codex config.toml."""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
Not checked against OSV yet; the weekly check has not reached this version.