fetch-transactionsLABSCO SUMMARY
Credentials from the environment only — a deliberate design choice, and the right one.
If bank passwords arrived as tool arguments they would end up in conversation history and in whatever logs the client keeps; reading them from the process environment keeps them out of both. That is a genuine mitigation, not a guarantee: this drives real logins to real bank accounts, and the author's own security section stops short of endorsing it. Start with a read-only use and a machine you control.
What it is
An MCP server over the israeli-bank-scrapers library, covering the major Israeli banks and credit card issuers. It lists which institutions are supported and exactly which environment variables each one needs, then fetches transactions over a date range you choose, with a separate step for institutions that require two-factor authentication.
What you get
- Transactions fetched from a supported bank over a date range —
fetch-transactions - Two-factor authentication handled as its own step for the institutions that require it —
two-factor-auth - A resource listing every supported bank and credit card company with the environment-variable names it needs —
banks://list - Credentials read from the environment rather than passed as tool arguments, so they never enter the LLM conversation history
- Coverage of Bank Hapoalim, Leumi, Discount, Mercantile, Mizrahi, Otsar Hahayal, Union Bank, Beinleumi, Massad, Yahav, Beyhad Bishvilha, Behatsdaa, OneZero (experimental), and the card issuers Visa Cal, Max, Isracard and Amex
Requirements
Your online banking credentials, supplied only through the environment. Each institution uses <BANK_ID>_<FIELD> variables — Bank Leumi needs LEUMI_USERNAME and LEUMI_PASSWORD, Hapoalim needs HAPOALIM_USERCODE and HAPOALIM_PASSWORD — and the banks://list resource reports the exact names per institution. Build from a clone with npm install and npm run build, then register build/server.js with node and put the variables in the client's env block. The package is israeli-bank-mcp 1.0.0. The author's own security note is a shrug rather than a reassurance — read it before deciding this belongs on a machine with your real banking credentials.
Setup effort
Build from source — git clone https://github.com/mottibec/israeli-bank-mcp.git
USE CASES
01
Pulling a month of transactions for reconciliation
Fetch the date range from the bank and hand the assistant structured transactions instead of a downloaded CSV.
02
Working out what a bank expects before you configure it
Read the supported-institutions resource for the exact environment-variable names that bank needs.
03
Getting past a login that demands a second factor
Complete the 2FA step for institutions that require it, then run the transaction fetch.
2 tools
Listed in project docs. Your client may show a different list.
two-factor-authBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
Login credentials for the bank or card company you use, as <BANK_ID>_<FIELD> environment variables — e.g. LEUMI_USERNAME and LEUMI_PASSWORD for Leumi, or HAPOALIM_USERCODE and HAPOALIM_PASSWORD for Hapoalim
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/mottibec/israeli-bank-mcp.git
cd israeli-bank-mcp
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"israeli-bank-mcp": {
"command": "node",
"args": [
"<YOUR_PATH_TO_ISRAELI_BANK_MCP>/build/server.js"
],
"env": {
"LEUMI_USERNAME": "<YOUR_LEUMI_USERNAME>",
"LEUMI_PASSWORD": "<YOUR_LEUMI_PASSWORD>"
}
}
}
}Set only the variables for your own bank: the block shows Leumi (LEUMI_USERNAME, LEUMI_PASSWORD); Hapoalim uses HAPOALIM_USERCODE and HAPOALIM_PASSWORD, and the banks://list resource names the variables for every other institution.
