Skip to main content
Glama
mottibec

Israeli Bank MCP

by mottibec

Related Servers

Alternatives to Israeli Bank MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Self-hosted MCP server that securely connects your bank accounts via Enable Banking, offering read-only access to balances and transactions for AI assistants.
      12
      121 npm
      271
      MIT
    • A
      license
      B
      quality
      F
      maintenance
      A Model Context Protocol server that provides programmatic access to Firefly III personal finance management. It enables AI assistants to manage accounts, transactions, budgets, and more through natural language.
      5
      8
      AGPL 3.0
    • F
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that exposes the Up Banking API to LLM clients, providing 19 tools and 2 resources for accounts, transactions, categories, tags, attachments, and webhooks.
      19
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that allows AI assistants to interact with Lunch Money accounts, enabling management of transactions, categories, budgets, and other financial data through natural language commands.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that provides AI assistants like Claude with secure, read-only access to MoneyWiz financial data for natural language queries and financial analytics.
      13
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for the Pluggy Open Finance Brazil API, enabling connection to bank accounts and management of financial data including transactions, accounts, investments, and payment intents through natural language.
      21 npm
      MIT

    TDQS

    D1.6/5.0

    Scored across 2 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness1/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive