No user-submitted related servers found.
Scored across 14 tools
Tools are separated by resource (accounts vs transactions vs identity) and action, with the main overlaps being the pending-transaction pair (acct_get_pending_transactions per account vs txn_get_pending_transactions across all) and txn_get_transactions vs txn_search_transactions. Descriptions explicitly disambiguate these cases (e.g. 'prefer get_transactions when filtering by account or amount'), so misselection is unlikely but possible. acct_get_account, acct_get_account_balance and acct_list_accounts are clearly distinguished by scope and cost.
A single predictable pattern is used throughout: a short domain prefix (acct_/txn_/id_) followed by verb_noun (list_accounts, get_account, get_transactions, search_transactions, report_transaction_issue). Singular/plural distinctions (get_transaction vs get_transactions) are used meaningfully, and no naming style is mixed.
14 tools is well within the ideal range for a banking data aggregation API, and each tool earns its place: accounts, settled transactions, pending transactions, identity, refresh, and support/verification actions. The refresh pair (all vs one account) and the get/balance split are justified by differing cost and rate-limit behavior.
The surface covers the full read lifecycle for accounts and transactions (list, get, balance, pending, batch, search) plus identity, name verification, data refresh, and issue reporting. Minor gaps remain: there is no way to enumerate connected institutions/connections or consent state, and no pagination/offset control beyond the internal 20-page cap. These are workable around, but an agent cannot fully audit its data sources.