Tochka Bank (PyPI) MCP Server
mcp-server-tochka-bank
PyPI
v0.6.2
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 5 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 0
Tools 42
Each tool and what it can reach — statically extracted from the published source.
tochka_download_closing_documentingests untrusted inputtochka_download_invoiceingests untrusted inputgoods_listno sensitive capabilitygoods_removeno sensitive capabilitytochka_account_detailno sensitive capabilitytochka_acquiring_paymentno sensitive capabilitytochka_acquiring_payment_captureno sensitive capabilitytochka_acquiring_payment_createno sensitive capabilitytochka_acquiring_payment_refundno sensitive capabilitytochka_acquiring_payment_with_receiptno sensitive capability
Show 32 more tools ↓
tochka_acquiring_paymentsno sensitive capabilitytochka_acquiring_registryno sensitive capabilitytochka_acquiring_retailersno sensitive capabilitytochka_all_balancesno sensitive capabilitytochka_balanceno sensitive capabilitytochka_card_transactionsno sensitive capabilitytochka_check_invoicesno sensitive capabilitytochka_consentno sensitive capabilitytochka_consent_childrenno sensitive capabilitytochka_consent_createno sensitive capabilitytochka_consentsno sensitive capabilitytochka_customerno sensitive capabilitytochka_customersno sensitive capabilitytochka_delete_closing_documentno sensitive capabilitytochka_delete_invoiceno sensitive capabilitytochka_incomingno sensitive capabilitytochka_invoiceno sensitive capabilitytochka_paymentno sensitive capabilitytochka_payments_for_signno sensitive capabilitytochka_pending_invoicesno sensitive capabilitytochka_searchno sensitive capabilitytochka_send_closing_document_emailno sensitive capabilitytochka_send_invoice_emailno sensitive capabilitytochka_statements_listno sensitive capabilitytochka_subscription_chargeno sensitive capabilitytochka_subscription_createno sensitive capabilitytochka_subscription_statusno sensitive capabilitytochka_subscription_status_setno sensitive capabilitytochka_subscription_with_receiptno sensitive capabilitytochka_subscriptionsno sensitive capabilitytochka_untrack_invoiceno sensitive capabilitytochka_updno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (42 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.6.2 latest |
A 95/100 | 0 | 1.9.0 | 2026-07-23 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan mcp-server-tochka-bank --online --registry pypiOther implementations of Tochka Bank 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Finance & Commerce
Security scan results for the 1money MCP server.
Security scan results for the Actual MCP server.
Security scan results for the Actual Budget MCP server.
Security scan results for the Adyen MCP server.
Security scan results for the Aelf Node Skill MCP server.
Security scan results for the Agent Skills MCP server.