moolre-mcpofficial
F
licenseB
qualityB
maintenanceMCP server that exposes Moolre's API as 24 tools for AI agents, enabling account management, transfers, payments, SMS, and WhatsApp operations.
24
-
tbank-mcp
Related Servers
Alternatives to tbank-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn 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-
- AlicenseNot gradedqualityAmaintenanceUnofficial MCP server for SberBank Online, enabling agents to read banking products and operations and perform transfers between own accounts directly via HTTP, with human confirmation for transfers. Also provides an async SDK and CLI for use without an agent.12 PyPI5MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for interacting with NexBank API v2, providing six business tools and supporting Bearer Token or OAuth authentication.1Apache 2.0
- FlicenseNot gradedqualityCmaintenanceA comprehensive banking system with MCP server capabilities and REST API, enabling account management, deposits, withdrawals, transfers, and transaction history through natural language or HTTP endpoints.-
- AlicenseNot gradedqualityFmaintenanceMCP server for T-Kassa (T-Bank/Tinkoff) payment API. Provides 16 tools for payments, refunds, recurring charges, customer management, saved cards, SBP, receipts, and T-Invest portfolio.51 npmMIT
TDQS
B3.1/5.0
Scored across 90 tools
Disambiguation3/5
The tool set uses clear domain prefixes and the descriptions often cross-reference related tools, but there are still several confusing families: list_operations vs card_operations vs operations_histogram, bank_documents vs documents, confirm_otp/confirm_pin/confirm_password/confirm_payment, and the generic get_data singleton. An agent would need to read very long descriptions carefully to avoid selecting the wrong tool.
Naming Consistency4/5
The vast majority of names are snake_case with a predictable domain prefix and a descriptive action or noun, such as grocery_search, train_book, list_accounts, transfer_sbp_resolve, and card_limits. Minor deviations like bare nouns for read-style actions (orders, trips, documents, diagnostics), plus a few noun-led names, stop it from being fully consistent but do not make the naming chaotic.
Tool Count1/5
90 tools is extreme for any single MCP server, even for a broad banking super-app. This many tools turns tool selection into a search problem rather than a decision among few clear options, and agents are more likely to overload context or miss the right tool.
Completeness3/5
Many major flows are covered end-to-end: payments, transfers, grocery ordering, train booking/payment/refund, cinema booking/payment/cancellation, and messenger conversation are implemented in detail. However, several obvious dead ends remain for a bank app: hotel booking and marketplace checkout are intentionally not supported, flight_book is effectively non-working/experimental, and inner transfer between own accounts is missing.
Maintenance
ActivityActive
ResponsivenessNo issues