Skip to main content
Glama
collinsb1

Mercury Enhanced MCP

by collinsb1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Mercury Enhanced MCP

No user-submitted related servers found.

    Related Servers

    • 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.
      8 npm
      MIT

    • Mercury MCP

      dragonkhoi
      A
      license
      Not graded
      quality
      D
      maintenance
      Simple MCP server that interfaces with the Mercury API, allowing you to talk to your Mercury banking data from any MCP client like Cursor or Claude Desktop.
      4
      MIT

    • Mercury Multiorg MCP

      dkaleganov
      A
      license
      A
      quality
      A
      maintenance
      An unofficial, read-only MCP server for Mercury business banking. It holds one read-only API token per organization, so a single AI session can work across several Mercury organizations; Mercury's own connector binds one organization per connection.
      24
      72 PyPI
      MIT

    • akahu-mcp

      adrianparker
      A
      license
      A
      quality
      B
      maintenance
      An MCP server exposing the Akahu banking API as tools to list accounts, get balances, and fetch transactions.
      3
      AGPL 3.0
    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

    A3.6/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have distinct purposes, but list_transactions and list_account_transactions overlap significantly: both retrieve transactions, with list_transactions supporting accountId filtering that can achieve the same result as list_account_transactions. This could cause misselection when an agent wants transactions for a single account.

    Naming Consistency4/5

    Names follow a consistent verb_noun pattern (e.g., get_, list_). Minor inconsistency: get_accounts exists alongside get_account, which is acceptable, but 'get_accounts' is a list operation while 'list_account_transactions' also lists, and some tools use 'get_' where 'list_' might be expected (e.g., get_recipients vs list_recipients would be more consistent).

    Tool Count5/5

    15 tools is well-suited for a financial API covering accounts, transactions, recipients, treasury, and cards. Each tool appears to serve a distinct resource or operation without excessive redundancy.

    Completeness4/5

    The tool set covers key read operations across accounts, transactions, recipients, and treasury, including statements and cards. However, it lacks any write operations (e.g., create recipient, initiate payment), which may be intentional but leaves the surface incomplete for a full payment API.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources