SkillFoxx

Tochka Bank MCP: accounts and payments for signing

tochka-bank-mcp

An MCP server for Tochka Bank's live business API: accounts, statements, and drafting rouble payments that a human signs via SMS in online banking

  • 2 ★ on the repository
  • Last commit
  • MIT
MCP server

Broad access

Why this level

  • Drafts real payments by bank details, though sending requires a human's signature
  • Reads balances, statements and company details, sensitive banking data
All reasons and checks
Russian stack

theyahia/tochka-bank-mcpAuthor:theYahia

Install

Services

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/tochka-bank-mcp

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Drafts real payments by bank details, though sending requires a human's signature
  • Reads balances, statements and company details, sensitive banking data

This is third-party code. Review the repository files before installing.

What it does

The server gives seven tools over Tochka's live API (enter.tochka.com/uapi): listing business accounts, account balances, transactions for a period (asynchronous, with status polling), client codes, company details, drafting an outgoing rouble payment, and its status. The server itself sends no money: create_payment builds a payment through the "for signing" flow, showing a preview with no send until the confirm flag is explicitly passed, after which a person signs the payment in Tochka's online banking via SMS. The tool has an amount limit via an environment variable and an optional recipient account whitelist. Authorization uses a hybrid OAuth 2.0 flow: a one-time auth command opens a browser to confirm rights, after which the server refreshes access and refresh tokens itself.

Who it is for. For companies with a Tochka Bank account who want account and statement access from an agent, and payment drafting with no risk of sending money without a human's confirmation.

Good fit when

  • You want to check an account balance and statement from a chat with an agent
  • You want to draft a payment by recipient details, but a human must sign it
  • You want a recipient whitelist and an amount limit to bound what the agent can even draft

Not a fit when

  • You need a list of external counterparties as a separate entity: Tochka does not expose them that way, you derive them from get_statement transactions
  • You need single-tenant JWT authentication: the server currently implements only the OAuth flow, JWT is not supported

Example request

Draft a payment of 75,000.50 roubles to OOO Romashka, account 40702810000000005678, BIC 044525225, for web development services, show the preview first

MCP

Transport
stdio
Authentication
OAuth

Environment variables

TOCHKA_CLIENT_ID required
OAuth client id from the Tochka developer dashboard
TOCHKA_CLIENT_SECRET required, secret
OAuth client secret
TOCHKA_MAX_PAYMENT_RUB
Maximum payment amount for create_payment, defaults to 100000
TOCHKA_ALLOWED_RECIPIENTS
Comma-separated whitelist of recipient accounts
TOCHKA_REFRESH_TOKEN secret
A pre-issued refresh token for headless deployments, skipping the auth step

Limitations

Requires a one-time auth command that opens a browser before first use; headless deployments need a pre-issued TOCHKA_REFRESH_TOKEN. External counterparties cannot be fetched as a separate list. Works against the live API, with a sandbox available via a separate base URL. The access token lives about a day, the refresh token about a month.

How to disable. Remove the tochka-bank server from claude_desktop_config.json and delete the token file ~/.config/tochka-bank-mcp/tokens.json.

FAQ

Can the agent send money itself?

No, create_payment only drafts a payment for signing; sending and signing happen in Tochka's online banking via SMS by a human.

Can I limit who and how much the agent can draft payments for?

Yes, TOCHKA_MAX_PAYMENT_RUB sets an amount limit, and TOCHKA_ALLOWED_RECIPIENTS restricts recipient accounts.

Discussion

No questions or reviews yet.

All Tochka Bank tools

Tochka Bank MCP server

MCP-сервер Точка Банка

Official

Tochka Bank's official MCP: an agent checks accounts and balances, builds statements and drafts payments that you sign in online banking

MCP serverBroad access

Tochka Bank MCP server

mcp-server-tochka-bank

Russian stack

A Tochka Bank MCP server for business owners: balance, invoices, payments with a signing link, closing documents and payment tracking

MCP serverBroad access
Russian stack

Self-hosted financial context for a business: cash position across Tochka and MoySklad, statement-to-ledger reconciliation and cash-gap forecasting

MCP serverExtended access
Russian stack

An MCP server for the Sberbank Business API: accounts, balance, statements, payment orders and counterparties for an AI agent

MCP serverBroad access1
Russian stack

Unofficial MCP server and skills for a personal T-Bank account: accounts, transfers, bill pay, tickets and groceries

MCP serverBroad access56
Russian stack

An MCP server for the Alfa-Bank Business Alfa API: accounts, statements, payments and rates, flagged as an unverified demo until a bank agreement is signed

MCP serverBroad access2

README in short

The README opens with a warning that the server can draft real payments but never sends them itself, explains the hybrid OAuth flow with a one-time auth command and a headless option via a pre-issued refresh token, an environment variable table with the amount limit and recipient whitelist, a seven-tool table flagged by operation type, and a security section on masking INNs and account numbers in logs and errors.

README badge

Report a problem