Back to MCP Trust Indexm8ven
56
/ 100
3 days ago
glama

theYahia/sber-mcp

MCP server for Sberbank business API enabling account management, balance checks, statements, payments, and counterparty operations.

→ theYahia/sber-mcp· listed on glama
Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find.

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
⚠️
Known vulnerabilities in dependencies: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
8 tools verified — handlers match their declared behaviour
7 read-only tools verified — handlers contain no write/delete/exec
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 3 credentials: SBER_ACCESS_TOKEN, SBER_CLIENT_SECRET, SBER_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies3 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.12.0GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.12.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.12.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
configPORT— 3000 npx -y @theyahia/sber-mcp --http
🔐 secretSBER_ACCESS_TOKEN— SBER_TOKEN один из Прямой Bearer-токен API (синоним )
configSBER_BASE_URL— нет API-хост (дефолт https://fintech.sberbank.ru:9443)
configSBER_CA_PATH— SBER_CERT_PATH / SBER_KEY_PATH / нет mTLS: отдельные PEM-файлы (альтернатива PFX)
configSBER_CERT_PATH— / SBER_KEY_PATH / SBER_CA_PATH нет mTLS: отдельные PEM-файлы (альтернатива PFX)
configSBER_CLIENT_ID— + SBER_CLIENT_SECRET один из OAuth client_credentials
🔐 secretSBER_CLIENT_SECRET— SBER_CLIENT_ID + один из OAuth client_credentials
configSBER_KEY_PATH— SBER_CERT_PATH / / SBER_CA_PATH нет mTLS: отдельные PEM-файлы (альтернатива PFX)
configSBER_OAUTH_SCOPE— нет Space-separated scope (дефолт GET_STATEMENT_ACCOUNT PAY_DOC_RU GET_CLIENT_ACCOUNTS)
configSBER_OAUTH_URL— нет OAuth-эндпоинт (дефолт https://api.sberbank.ru:8443/prod/tokens/v2/oauth)
configSBER_PFX_PASSPHRASE— SBER_PFX_PATH / нет mTLS: путь к .p12/.pfx и пароль
configSBER_PFX_PATH— / SBER_PFX_PASSPHRASE нет mTLS: путь к .p12/.pfx и пароль
configSBER_TIMEOUT_MS— нет Таймаут запроса в мс (дефолт 30000)
🔐 secretSBER_TOKEN— "": "ваш-bearer-токен"
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/theyahia-sber-mcp-g1zdeq)](https://m8ven.ai/mcp/theyahia-sber-mcp-g1zdeq)
commit: 0d18002923aa3deea08365aabaecf7a5a3848af7
code hash: d6289f2d5615eb8d1429ba8260e1f5a39269208b381a9103ab18901214944e02
verified: 7/28/2026, 9:04:08 AM
view raw JSON →