sber-unofficial-mcp
MCP server that exposes the unofficial SberBank Online SDK to AI agents (Claude, Codex, Cursor): browserless auth, product/operation reads, and self-transfers gated by explicit human approval. Secrets never cross the agent boundary; integration is direct client ↔ SberBank, with no third-party services.
pip install sber-unofficial-mcp # pulls in sber-unofficial-sdk
sber-unofficial-mcp login # one-time interactive login
Then connect the sber-unofficial-mcp command to your agent. The core SDK is a
separate package, sber-unofficial-sdk,
usable on its own.
By default the server is read-only — the tools that change the account are not
registered at all. Pass --allow-writes to enable card rename and self-transfers.
To try it without a bank account, run sber-unofficial-mcp --demo for a synthetic
portfolio that contacts nothing.
Full documentation: https://github.com/ex3lite/sber-mcp
mcp-name: io.github.ex3lite/sber-mcp
Metadata
Release files for sber-unofficial-mcp 0.6.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sber_unofficial_mcp-0.6.4.tar.gz | 29.7 kB | With provenance | Details for sber_unofficial_mcp-0.6.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sber_unofficial_mcp-0.6.4-py3-none-any.whl | Python 3 | none | any | Details for sber_unofficial_mcp-0.6.4-py3-none-any.whl |
Total release size: 59.2 kB
Release files / sber_unofficial_mcp-0.6.4.tar.gz
| Download URL | sber_unofficial_mcp-0.6.4.tar.gz |
|---|---|
| Size | 29.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
31eede4329aa2cf9a09a913f53ce7a3fb6fbb05c73f6f261b85e70958846b8d1
|
|
BLAKE2b-256 checksum How to use checksums |
9321404ad3d28838a0eec74848103b9b45b3dfb53e55ab94c08d85be41e579ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 5, 2026.
Transparency logRelease files / sber_unofficial_mcp-0.6.4-py3-none-any.whl
| Download URL | sber_unofficial_mcp-0.6.4-py3-none-any.whl |
|---|---|
| Size | 29.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a10d9ad5bd7f182c795068b0d7f166d58e779ee64a7e5f5ebb199ac40b8996bd
|
|
BLAKE2b-256 checksum How to use checksums |
044be713fe5518834e453da19062fbb4eff1bf0b0b2df493945ae37520fa5db5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 5, 2026.
Transparency logSecurity for sber-unofficial-mcp 0.6.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for sber_unofficial_mcp-0.6.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 5, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.