FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository icyberdeveloper/tbank-mcp;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
T-Bank MCP
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
**T-Bank (Т-Банк) MCP** — mobile banking API server for Claude Code, Codex, ChatGPT, and other MCP-capable agents.
The buttons register the tbank-mcp command — run pip install tbank-mcp first.
Features
- **90 tools**: accounts, cards, documents, operations, grocery ordering, cinema and
concert tickets, train and flight booking, hotel search, orders, transfers
(including payment by bank requisites, from a scanned invoice QR), messenger,
investments
- **A skill for every vertical**, entered through the tbank router skill: grocery
order, tickets, travel, transfer, bill pay, cards & documents, messenger, budget
analysis, invest advisor, login
- **Pinned CA trust**: system store + the Russian Trusted Root CA (Минцифры), which no
OS ships and every *.t-bank-app.ru host needs — that is most of the hosts this
MCP talks to. Shipped in tbank_mcp/ca/roots/, pinned by SHA-256. Leaf/intermediate rotation
needs no action; a root rotation is a PEM drop into tbank_mcp/ca/roots/ (or TBANK_EXTRA_CA).
The verify bundle is (re)generated from that material into
~/.local/share/tbank-mcp/bundle.pem; TBANK_CA_BUNDLE relocates it — it is a
write target, not a curated input, so extra roots go in via TBANK_EXTRA_CA.
Certificates are never learned from the network — see the header of tbank_mcp/tls.py.
- **Grocery checkout**: search → cart → order → pay (proven end-to-end)
- **Secure login**: password/PIN stay OUT of the LLM context (local CLI or env var)
Quick Install
As a Claude Code plugin (server + every skill in one step)
There is no store to be admitted to — a marketplace is just a git repo with a
.claude-plugin/marketplace.json, and anyone can host one.
The venv and the Python dependencies are created on the server's first start by
bin/tbank-mcp: a plugin manifest cannot run install steps (install is not a
field in the schema), so the launcher does it once and every later start goes
straight to the server. Only the grocery checkout needs a browser, and 150 MB is
not something to download behind your back — install it yourself if you want that
flow:
From PyPI
The tbank-mcp console script starts the stdio server; the pinned CA roots, the
flows reference and the skills all ship inside the wheel, so it runs from anywhere.
tbank-mcp-login is the same login CLI as the repo's login_cli.py — both write
the session to the same file the server reads. tbank-mcp-skills installs the
skills for Claude Code (default ~/.claude/skills, --target for elsewhere) and,
unlike a plain cp, first removes stale copies under retired names — re-run it
after upgrades. The grocery checkout browser stays opt-in here too:
python -m playwright install chromium.
Manually (clone, no plugin)
🔒 Login — the password never reaches the agent
The password and the PIN are secrets, and they are **not put into the model's
context**. Logging in is done by a local script, or through an environment variable.
Option 1 (recommended): the local CLI
The script asks for the password itself, via getpass, so it is never echoed to the
terminal and never passes through the agent. Its prompts are in Russian, as shown:
Or with the password in the environment, for CI and scripts:
Then **start Claude Code**. The agent picks up the saved session and works without
the password, which never enters the LLM context.
Option 2: through the agent (convenient, but the LLM sees the password)
If you are content to hand the password to the agent:
⚠️ **Note:** the password ends up in the model's context and in call logs. For an
account you care about, use Option 1.
Both options need the SMS code typed in either way, so there is no unattended
login. TBANK_PASSWORD (and TBANK_PIN) are read **only** by the login CLI
(tbank-mcp-login / login_cli.py) — the
env example above — and never by the MCP server or the LLM. TBANK_PHONE is not
read anywhere: the phone is always a command-line argument.
> **Работа с MyT (рабочий календарь и парковка) переехала** в отдельный MCP:
> tbank-myt. Другой аккаунт, другая
> сессия, свой login_cli.py — здесь их больше нет.
Other agents (Codex, ChatGPT, Hermes, OpenClaw)
With a pip install tbank-mcp the whole entry shrinks to "command": "tbank-mcp" —