Skip to main content
Glama
theYahia

is-bankasi-mcp

by theYahia

Related Servers

Alternatives to is-bankasi-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      A
      quality
      D
      maintenance
      MCP server for MAIB e-commerce payments (Moldova). Supports payments, refunds, recurring billing, one-click payments, and transaction status via OAuth 2.0.
      8
      13 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
      -
    • F
      license
      C
      quality
      B
      maintenance
      A standalone MCP server wrapping Mastercard Open Finance US (Finicity) APIs for open banking operations, enabling financial data access and payment services.
      62
      -
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Bank of Georgia iPay payment gateway, enabling payment orders, refunds, recurring payments, and pre-authorization via OAuth 2.0 + JWT.
      8
      16 npm
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Remote MCP server for Deutsche Bank BizBank/SME API, enabling secure OAuth with PKCE and tools for account and transaction management.
      -

    TDQS

    B3.4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: accounts, balances, transactions, exchange rates, transfers, and cards are clearly separated. There is no overlap between getting account transactions versus card transactions, and transfer initiation/status checking are unambiguous.

    Naming Consistency4/5

    Seven of eight tools follow the 'get_' verb-noun pattern, making the set highly predictable. 'initiate_transfer' deviates by using an action verb rather than 'get_', which is a minor inconsistency but does not cause confusion.

    Tool Count5/5

    With 8 tools, the server is well-scoped for a banking API covering accounts, transactions, cards, exchange rates, and transfers. Each tool serves a distinct purpose, and the number feels appropriate without being overwhelming or sparse.

    Completeness4/5

    The toolset covers core banking workflows: listing accounts, checking balances, viewing transactions, managing transfers, and accessing card data. Minor gaps exist, such as lacking a dedicated transfer history or card details endpoint, but agents can work around these using existing tools.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing