n26-mcp
Related Servers
Alternatives to n26-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables read-only access to personal bank accounts via the TrueLayer API, allowing querying of accounts, balances, transactions, and generating financial analytics such as spending by category, subscriptions, and monthly summaries.91MIT
- AlicenseNot gradedqualityCmaintenanceEnables read-only access to personal European bank accounts through Enable Banking, allowing MCP clients to list accounts, retrieve balances, search and summarize transactions, and estimate spending with bounded, privacy-preserving tools.MIT
- AlicenseNot gradedqualityCmaintenanceEnables read-only access to a single company's bank accounts via Enable Banking (PSD2 account information), so users can list registered accounts, read balances and account details, and retrieve transactions for a period with filtering and totals. Account ownership is enforced by a reviewed registry and per-company instance pinning, with consent lifecycle tools available when explicitly enabled.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables secure, read-only access to personal European bank accounts through Enable Banking and Cloudflare Workers, allowing MCP clients to list accounts, retrieve balances, search transactions, and summarize cash flow.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables reading C6 Bank account balances, statements, credit card bills, and investments via Open Finance Brasil. It is read-only and regulated by the Central Bank of Brazil.MIT
- AlicenseAqualityAmaintenanceEnables read-only access to Banco General accounts, cards, and pension data through MCP, allowing balance checks, transaction searches, and spending summaries without moving funds.1425 npm1MIT
TDQS
Scored across 5 tools
Each tool maps to a distinct read-only resource: accounts, balances, transactions, recurring-charge detection, and consent expiry. The only mild overlap is between get_transactions and recurring_charges, since the latter is derived from transaction data, but the descriptions explicitly steer agents (use recurring_charges for summaries rather than raising the transaction limit).
Three tools follow a clean verb_noun pattern (list_accounts, get_balances, get_transactions), while recurring_charges and consent_status are noun-phrase names describing derived resources. The deviation is small and every name is self-explanatory, so predictability remains high.
Five tools is well-scoped for a read-only open-banking surface, and each one covers a genuinely different question (which accounts, what balance, what moved, what recurs, is the consent still valid). There is no filler or redundant tool.
The read-only lifecycle is well covered: discovery, balances, paged/filterable transactions, recurring-charge analysis, and consent health including expiry warning. Minor gaps exist (no account-holder details, no dedicated spending-summary tool — it is only referenced as an external resource), but nothing blocks core agent workflows, and payment operations are intentionally out of scope.