Skip to main content
Glama
tkom04

Open Banking MCP Server

by tkom04

Related Servers

Alternatives to Open Banking MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Enables read-only access to personal bank accounts via the TrueLayer API, allowing querying of accounts, balances, transactions, and generating financial analytics such as spending by category, subscriptions, and monthly summaries.
      9
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables Claude to read UK bank account data—balances, transactions, cards, standing orders, direct debits, and identity—through TrueLayer's Data API, with local caching and optional live refreshes. It is read-only by design, requiring consent and never moving money.
      12
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to a single company's bank accounts via Enable Banking (PSD2 account information), so users can list registered accounts, read balances and account details, and retrieve transactions for a period with filtering and totals. Account ownership is enforced by a reviewed registry and per-company instance pinning, with consent lifecycle tools available when explicitly enabled.
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to interact with Up Bank accounts and transactions, including reading balances, summarizing spending, and categorizing or tagging transactions.
      -
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables interaction with Monzo bank accounts for balance checking, transaction management, pot operations, and reconciliation through natural language.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Qonto's Business API for banking operations. Supports all API key-accessible endpoints for managing business banking transactions and account information.
      3
      MIT

    TDQS

    C2.8/5.0

    Scored across 9 tools

    Disambiguation2/5

    exchange_code and complete_code_exchange overlap almost entirely (one is a legacy alias), and get_accounts/list_accounts plus get_transactions/list_transactions have similar names but differ in real vs. dummy behavior, creating confusion. An agent could easily select the wrong tool without careful description inspection.

    Naming Consistency3/5

    The pattern is mostly verb_noun, but the use of both get_ and list_ prefixes for closely related actions, along with exchange_code versus complete_code_exchange, shows inconsistent verb choice. The 'legacy alias' note further muddies the name convention.

    Tool Count5/5

    With 9 tools, the server is well-scoped for Open Banking operations covering auth, accounts, transactions, consents, and export. Each tool has a place, and the count is neither too small nor excessive.

    Completeness4/5

    The surface covers the core lifecycle: OAuth authorization, code exchange, account listing, transaction retrieval, CSV export, and consent listing. Notable gaps include consent revocation and token refresh, which are minor but would round out the workflow.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive