Atlas / MCP servers / mottibec / Israeli Bank

Israeli BankSAFE

mcp/mottibec/israeli-bank
Verdict
SAFE
Grade
B
Trust score
89 /100
Exposed tools
2 2r · 0w · 0d
Transport
stdio
License
—
Stars
37
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

A project for managing Israeli bank accounts and transactions using the Model Context Protocol (MCP).

Features

  • 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

Getting Started

  1. Install dependencies:
npm install
  1. Build the project:
npm run build
  1. Connect to MCP Clients

Connecting to MCP Clients

The server can be connected to any MCP-compatible client. Here's how to configure it:

Example Configuration

Credentials are read from environment variables (never from tool arguments — this avoids leaking them into the LLM conversation history). Each bank requires _ 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"
}
}
}
}

Resources

  • Banks (banks://list)
  • List available banks and their required credentials

Tools

  • Fetch transactions (fetch-transactions)
  • Fetch transactions from a bank
  • 2FA (two-factor-auth)
  • 2FA authentication for banks that require that

Supported Banks

The server supports all major Israeli banks and credit card companies through the [israeli-bank-scrapers](https://github.com/eshaham/is

Read from source at commit bf723d03cc50OBSERVED · 2026-10-08
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.

claude-code
claude mcp add israeli-bank-mcp -- npx -y [email protected]
claude-desktop
{
  "mcpServers": {
    "israeli-bank-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ]
    }
  }
}
03

Exposed tools (2)

2 read · 0 write · 0 destructive.

ToolRiskDescription
fetch-transactionsread
two-factor-authread
04

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
not all pinned
Secrets in source
none-found

Findings (3)

LOWInventory / provenance · inv.no_license · CWE-1104
Why it matters. no LICENSE file and no repo licence
Fix. add a licence
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
package.json
@modelcontextprotocol/sdk, israeli-bank-scrapers, typescript, @types/node, ts-node, zod
Why it matters. 6 dependency range(s) float
Fix. pin exact versions or ship a lockfile
INFOPrompt injection · prompt.credential_read · CWE-94, CWE-1427
README.md:34
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,
Why it matters. asks the agent to read credentials

Gates applied: no_behavioural_pass, no_license.

Audited 2026-10-08 · audit v0.4.1 · source sha bf723d03cc50full audit observations/trust-audit/mcp-server/mottibec__israeli-bank.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-08bf723d03cc50SAFEB89first audit
06

Questions

What tools does Israeli Bank expose?

2 in total: 2 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is Israeli Bank safe to connect to an agent?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.

What credentials does Israeli Bank need?

No credential environment variables were found in its source, so it appears to need none.

How does Israeli Bank run?

It speaks stdio, so it runs as a local process your client starts. It is published on npm as israeli-bank-mcp at 1.0.0.

How current is this page?

The grade is for one exact copy of the source (bf723d03cc50), read on 2026-10-08. The repository is watched and re-audited when it changes.

Advertisement