sber-unofficial-mcp@0.6.4
VERIFIED· not startedPublisher claims: "MCP server exposing the unofficial SberBank Online SDK to AI agents" 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
SBER_MCP_CREDENTIALSSBER_PASSWORDSBER_UFS_TOKENConfiguration, not credentials: LC_ALL, LC_MESSAGES, SBER_ANTIFRAUD_DEVICEPRINT_FILE, SBER_DEVICEPRINT_FILE, SBER_LOGIN, SBER_MCP_HOME, SBER_MCP_LANG, SBER_MCP_PROFILE, SBER_UFS_SESSION- 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 SBER_MCP_CREDENTIALS, SBER_PASSWORD, SBER_UFS_TOKEN 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-16 and scored it 91/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
details={"fix": "chmod 600 <path>; must be a regular file you own"})Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.raise InsecureSessionFile(f"{path} must not be group/other accessible (chmod 700)")Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.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 sber-unofficial-mcp@0.6.4 as of 34 min ago. This is the package itself, not its dependencies.