Skip to main content
Glama
Sign In
starling-bank-mcp

starling-bank-mcp

by domdomegg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to starling-bank-mcp

No user-submitted related servers found.

    Related Servers

    • financy

      open-finance-ai
      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.
      124 npm
      6
      Apache 2.0

    • Mercury MCP Server

      Fyko
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Mercury Banking API that enables listing accounts and retrieving transactions via natural language.
      6 npm
      MIT

    • FreeAgent MCP Server

      StupidCodeFactory
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the FreeAgent accounting API, enabling LLMs to securely access and manage accounting data including contacts, invoices, bills, bank transactions, and more.
      5 npm
      1
      MIT
    • moolre-mcp

      moolre-mcpofficial

      moolrehq
      F
      license
      B
      quality
      D
      maintenance
      MCP server that exposes Moolre's API as 24 tools for AI agents, enabling account management, transfers, payments, SMS, and WhatsApp operations.
      24
      -
    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

    B3.2/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, and the entity_action naming makes intent clear. The main ambiguity is between transactions_list and the feed_item_* family, which both concern transactions, though descriptions clarify that a feed item is a transaction. savings_goal_deposit vs withdraw and payment_create vs payee_create are clearly distinguishable.

    Naming Consistency4/5

    Nearly all tools follow a consistent noun_verb pattern (accounts_list, payment_create, card_lock_update, savings_goal_delete). The only deviations are inconsistent pluralization of the entity prefix (accounts_list vs account_balance_get, savings_goals_list vs savings_goal_create), which is a minor blemish rather than a convention break.

    Tool Count4/5

    24 tools is on the heavier side but justified by the breadth of the banking domain (accounts, feed items, payees, payments, cards, direct debits, standing orders, savings goals). Each tool maps to a real operation, with little redundancy, though the set sits at the upper end of what stays manageable.

    Completeness4/5

    Coverage is strong: savings goals have full CRUD plus deposit/withdraw, feed items support read/update/attachment workflows, and read-only surfaces exist for accounts, cards, direct debits, and standing orders. Gaps remain around payments (create only, no list/cancel) and standing orders/direct debits (list only), but these are minor and workable.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources