Skip to main content
Glama
noskillish

BankMCP

by noskillish

Related Servers

Alternatives to BankMCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server that securely connects Swedish/Nordic bank accounts to AI assistants, keeping all financial data local and encrypted.
      19 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that exposes Enable Banking API tools for interacting with bank accounts through Open Banking. It enables users to authenticate sessions, list accounts, and fetch transaction history or balances via a secure self-hosted server.
      2
      -
    • A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server for the open-banking.io PSD2 API that lets AI agents query personal bank balances and transactions via natural language, with zero-knowledge encryption ensuring all sensitive data is decrypted in-process and never exposed to third parties.
      4
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Self-hosted MCP server enabling Claude to query bank accounts, balances, and transactions through Plaid with OAuth and TLS.
      -
    • A
      license
      B
      quality
      B
      maintenance
      A read-only MCP server that exposes Turkish open banking data (accounts, balances, transactions, cash flow, and cards) to AI agents via the ÖHVPS 2.0.0 standard.
      5
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      A read-only MCP server that connects AI clients to your own bank, credit card, loan, and brokerage data through Plaid or Teller, letting you query accounts, balances, transactions, holdings, liabilities, identity, income, and run debt avalanche/snowball payoff analysis. Credentials and access tokens stay locally in a chmod-600 SQLite file, with outbound calls limited to the provider's API.
      24
      1
      MIT

    TDQS

    A3.9/5.0

    Scored across 12 tools

    Disambiguation4/5

    Tools are mostly distinct: account queries (get_balances, get_transactions), consent lifecycle (start_consent, consent_status, disconnect_bank), account listing/labeling, and watch management (create_watch, list_watches, delete_watch, check_watches). Minor overlap between list_accounts and get_balances (both return booked balances) and between check_watches and create_watch's notification behavior, but descriptions clarify the differences.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern: get_balances, get_transactions, list_banks, list_accounts, list_watches, start_consent, delete_watch, disconnect_bank. Minor deviations: create_watch vs. delete_watch/list_watches (could be add_watch for consistency), and consent_status/check_watches/set_account_label are noun-ish or verb_noun but not perfectly parallel. Overall predictable.

    Tool Count5/5

    12 tools is well-scoped for a banking aggregation server. Each tool covers a distinct part of the workflow: bank discovery, consent management, account access, labeling, transaction history, and watch rules. No redundant or filler tools.

    Completeness4/5

    The surface covers the core banking aggregation lifecycle: connect banks, list accounts, read balances/transactions, label accounts, and manage watches. Minor gaps: no tool to update a watch or refresh a consent, and no explicit way to fetch a single transaction or account detail beyond balances, but agents can work around these with existing tools.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive