The Israeli Bank MCP server lets you interact with Israeli bank accounts and credit card companies to fetch financial transactions and handle authentication.
List supported banks (banks://list resource): Retrieve all supported Israeli banks and credit card companies along with their required credentials/environment variables.
Fetch transactions (fetch-transactions tool): Retrieve transactions from any supported institution by providing a bankId (e.g., hapoalim, leumi), credentials (username, password, userCode, card6Digits, nationalID, etc.), and optional parameters like startDate, showBrowser, and combineInstallments. Credentials are managed via environment variables to prevent leakage into conversation history.
Two-Factor Authentication (two-factor-auth tool): Handle 2FA for supported banks — use action: "trigger" to send an OTP to a phoneNumber, or action: "get-token" with an otpCode to retrieve a long-term 2FA token.
Supported institutions include: Bank Hapoalim, Leumi, Discount, Mizrahi, Union Bank, Beinleumi, Massad, Yahav, Otsar Hahayal, Beyahad Bishvilha, Visa Cal, Max, Isracard, Amex, and more.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Israeli Bank MCP fetch my recent transactions from Bank Hapoalim for the last 30 days"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A project for managing Israeli bank accounts and transactions using the Model Context Protocol (MCP).
List available Israeli banks and credit card companies with their required credentials
Fetch transactions from any supported bank
Support for all major Israeli banks and credit card companies
Secure credential handling
Flexible transaction date ranges
Two-factor authentication support
Related MCP server: MoneyWiz MCP Server
Install dependencies:
npm installBuild the project:
npm run buildConnect to MCP Clients
The server can be connected to any MCP-compatible client. Here's how to configure it:
Credentials are read from environment variables (never from tool arguments — this avoids leaking them into the LLM conversation history). Each bank requires <BANK_ID>_<FIELD> env vars. For example, Bank Leumi needs LEUMI_USERNAME and LEUMI_PASSWORD; Hapoalim needs HAPOALIM_USERCODE and HAPOALIM_PASSWORD. Use the banks://list resource to see required env-var names per bank.
For clients that support configuration files (like Claude), add the following to your configuration:
{
"mcpServers": {
"israeli-bank-mcp": {
"command": "node",
"args": [
"/path/to/israeli-bank-mcp/build/server.js"
],
"env": {
"LEUMI_USERNAME": "your-username",
"LEUMI_PASSWORD": "your-password"
}
}
}
}Banks (banks://list)
List available banks and their required credentials
Fetch transactions (fetch-transactions)
Fetch transactions from a bank
2FA (two-factor-auth)
2FA authentication for banks that require that
The server supports all major Israeli banks and credit card companies through the israeli-bank-scrapers library:
Bank Hapoalim
Leumi Bank
Discount Bank
Mercantile Bank
Mizrahi Bank
Otsar Hahayal Bank
Visa Cal
Max (Formerly Leumi Card)
Isracard
Amex
Union Bank
Beinleumi
Massad
Yahav
Beyhad Bishvilha
OneZero (Experimental)
Behatsdaa
Please do not attempt this at home (I honestly don't know, it's probably not a good idea, but it's really cool)
MIT
| Name | Required | Description | Default |
|---|---|---|---|
| bankId | Yes | ||
| combineInstallments | No | ||
| credentials | Yes | ||
| showBrowser | No | ||
| startDate | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | ||
| bankId | Yes | ||
| otpCode | No | ||
| phoneNumber | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0fetch-transactionstwo-factor-authScored across 2 tools
The two tools have clearly distinct purposes: 'fetch-transactions' retrieves transaction data, while 'two-factor-auth' handles authentication. There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool.
Both tools use a consistent verb-noun pattern with hyphens (e.g., 'fetch-transactions', 'two-factor-auth'), which is predictable and readable. The minor deviation is that 'two-factor-auth' uses a compound noun without a clear verb, but overall the naming is coherent.
With only two tools, the server feels thin for a banking domain, which typically requires operations like account management, transfers, balances, or payments. This limited set may not cover essential banking workflows, indicating an under-scoped tool surface.
The tool set is severely incomplete for a banking server. It lacks basic operations such as checking account balances, initiating transfers, managing accounts, or handling payments. The two tools provided do not form a functional banking interface, leading to significant gaps that will cause agent failures.
A Model Context Protocol server for Wix AI tools
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
An MCP server that provides read access to your cloud storage providers, bank accounts and more.
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
