Skip to main content
Glama
FIO Bank MCP Server

FIO Bank MCP Server

by zjor

Related Servers

Alternatives to FIO Bank MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables users to read Czech Fio banka account details, booked transaction history and balances, download official statements, and prepare exact CZK domestic payment batches for manual approval in Fio.
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Exposes SimpleFIN bank data (accounts and transactions) as tools for Claude Code, enabling users to connect to bank accounts, list balances, and fetch transactions.
      4
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables secure interaction with Plaid's Transactions API to sync, search, and analyze financial transactions from linked bank accounts using natural language queries.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables Claude to interact with a Folio business bank account for managing accounts, transactions, receipts, bookkeeping, and payments as drafts.
      14
      25 npm
      6
      MIT
    • A
      license
      B
      quality
      C
      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
      B
      quality
      F
      maintenance
      Query bank accounts, credit cards, and transactions via Sophtron's financial data API. Works with Claude Desktop and any MCP-compatible client.
      10
      1
      Apache 2.0

    TDQS

    A4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool exposed, there is no possibility of the agent selecting the wrong tool. Its purpose (fetching account transactions over a date range) is stated unambiguously.

    Naming Consistency5/5

    The single name fio_get_transactions follows a clean namespace_verb_noun convention that would extend predictably. There is no competing convention to clash with.

    Tool Count2/5

    One tool is far too thin for a bank API surface, which naturally spans accounts, statements, and payment operations. The server exposes a single read endpoint, so the count is an extreme mismatch for the apparent domain.

    Completeness2/5

    The surface covers only transaction retrieval; there is no way to list accounts, fetch a formal statement, or initiate/verify payments. Agents needing anything beyond a read of transactions will hit a dead end.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues