Skip to main content
Glama
adrianparker

akahu-mcp

by adrianparker

Related Servers

Alternatives to akahu-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      D
      maintenance
      An MCP server that exposes Akahu (New Zealand open-banking) data to LLM agents, allowing them to list bank accounts, inspect investment holdings, and pull transactions for analysis.
      3
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that syncs New Zealand bank accounts from Akahu into a local SQLite cache, offering tools for transaction search, spending summaries, cashflow, recurring charges, and more for natural language money queries.
      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
      Not graded
      quality
      B
      maintenance
      MCP server that exposes banking data (connections, accounts, balances, transactions) and agent skills, allowing AI agents to query and refresh financial data via stdio.
      36 npm
      6
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Mercury Banking API that enables listing accounts and retrieving transactions via natural language.
      5 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides read-only access to your BECU accounts via browser automation, enabling querying of account balances and transaction history conversationally.
      MIT

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: listing accounts, fetching a single account's balance, and fetching a single account's transactions. No overlap or ambiguity between them.

    Naming Consistency4/5

    Tool names follow a mostly consistent snake_case pattern with verb-noun structure, but two use the 'bank_get_' prefix while 'list_accounts' deviates slightly. The inconsistency is minor and does not hinder understanding.

    Tool Count5/5

    Three tools is an appropriate size for a banking read-only integration, covering the essential operations without unnecessary bulk. Each tool earns its place.

    Completeness4/5

    The tool set covers the core read-only banking needs: account listing with balances and transaction retrieval. Minor gaps exist (e.g., no direct account details endpoint, no cross-account transaction aggregation), but these are not critical for the apparent purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive