Skip to main content
Glama
zjor

FIO Bank MCP Server

by zjor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to FIO Bank MCP Server

No user-submitted related servers found.

    Related Servers

    • simplefin

      RommelTVAG
      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
      -

    • Plaid Transactions MCP Server

      laramarcodes
      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.
      -

    • folio-mcp

      henrikkvamme
      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
      3 npm
      6
      MIT

    • open-banking-mcp

      pimvanoerle
      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
      MIT

    • sophtron-mcp

      312-dev
      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

    • ClearFi Finance MCP Server

      vaughngit
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to the ClearFi personal finance API for searching transactions, tracking bills, analyzing spending, and managing accounts.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    Resources