theYahia/sber-mcp (theYahia/sber-mcp) is an MCP server listed on the M8ven Trust Index. It scores 56 out of 100, grade D. It declares 8 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
56/100

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

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

theYahia

Source: 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. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// 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.
// tools this server exposes8 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

get_accounts

Список счетов клиента в Сбербанке.

get_balance

Баланс по счёту.

get_statement

Выписка по счёту за период (список транзакций). Поддерживает пагинацию.

summarize_transactions

Сводка по выписке: количество, суммы поступлений/списаний, чистый итог за период.

create_payment
get_payment_status

Статус платежа по ID.

list_counterparties

Список сохранённых контрагентов (получателей платежей).

get_company_info

Сведения об организации-клиенте (реквизиты, ИНН, список счетов).

// 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 →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretSBER_ACCESS_TOKENSBER_TOKEN один из Прямой Bearer-токен API (синоним )
configSBER_BASE_URLнет API-хост (дефолт https://fintech.sberbank.ru:9443)
configSBER_CA_PATHSBER_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_SECRETSBER_CLIENT_ID + один из OAuth client_credentials
configSBER_KEY_PATHSBER_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_PASSPHRASESBER_PFX_PATH / нет mTLS: путь к .p12/.pfx и пароль
configSBER_PFX_PATH/ SBER_PFX_PASSPHRASE нет mTLS: путь к .p12/.pfx и пароль
configSBER_TIMEOUT_MSнет Таймаут запроса в мс (дефолт 30000)
🔐 secretSBER_TOKEN"": "ваш-bearer-токен"
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

All four hints declared on every tool

8/8 tools missing one or more hints — get_accounts (missing: destructiveHint, idempotentHint, openWorldHint); get_balance (missing: destructiveHint, idempotentHint, openWorldHint); get_statement (missing: destructiveHint, idempotentHint, openWorldHint), +5 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

Only 0/8 tool handlers declare input schemas (0%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 0/8 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

5/8 tools referenced in tests (63%)

Write tests that reference each tool by name so every tool has at least one test.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.12.0 (high), @modelcontextprotocol/sdk@1.12.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// 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 Verified](https://m8ven.ai/badge/mcp/theyahia/sber-mcp?variant=verified)](https://m8ven.ai/mcp/theyahia/sber-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 0d18002923aa3deea08365aabaecf7a5a3848af7
code hash: d6289f2d5615eb8d1429ba8260e1f5a39269208b381a9103ab18901214944e02
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client