No user-submitted related servers found.
Scored across 11 tools
Most tools target distinct resources (balance, profile, accounts, movements, payment cards, beneficiaries), but test_connection overlaps with get_default_account_balance by also retrieving the balance, and the three create_*_beneficiary tools are very similar in function though differentiated by beneficiary type. Agents may struggle to pick between these without careful reading.
Tools generally follow a verb_noun pattern in snake_case (get_profile_data, list_deposit_accounts), but there is inconsistency with compound nouns: 'list_paymentcards' and 'create_paymentcard' lack the expected underscore between 'payment' and 'card', unlike 'get_default_account_balance' and 'list_deposit_accounts'. This is a minor deviation from an otherwise predictable pattern.
With 11 tools, the set is well-sized for a payment server covering balance, profile, accounts, movements, payment cards, and beneficiaries. Each tool addresses a distinct need without excessive granularity or bloat.
The read side is solid (profile, balance, accounts, movements, cards, beneficiaries) and creation is supported for payment cards and all beneficiary types. However, there are no update/delete operations for cards or beneficiaries, nor any transfer/payment initiation tools, leaving clear gaps in the expected lifecycle for a payment platform.