sparebank1-mcp
Related Servers
Alternatives to sparebank1-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables users to view personal bank accounts, balances, and transaction history through a local stdio MCP connection. It uses the non-public mobile banking API with locally stored session credentials and no payment or generic HTTP tools.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants and scripts to read, analyze and safely write self-hosted personal finance books, covering accounts, transactions, categories, tags, monthly and category reports, net worth, cash flow, recurring payments, installment plans and bulk imports. Writes are safeguarded with dry runs, delete confirmation, and an optional read-only mode, while amounts are returned exactly as both minor units and decimal strings with totals kept per currency.MIT
- AlicenseNot gradedqualityDmaintenanceA read-only MCP server that securely connects Swedish/Nordic bank accounts to AI assistants, keeping all financial data local and encrypted.22 npmMIT
- AlicenseBqualityAmaintenancePrivacy-first MCP server for the Starling Bank (UK) public API. Covers all 87 operations: balances, transactions, spaces and savings goals, cards, direct debits, payees, payments and standing orders, plus local spending and subscription analysis. Read-only by default; local stdio only with no telemetry; token stored in the macOS Keychain; human confirmation before any money moves.547 npm1MIT
- AlicenseAqualityBmaintenanceEnables local management of Trade Republic accounts, including portfolio, cash, orders, documents, and market data, with dry-run order previews and safety guardrails.22MIT
- AlicenseNot gradedqualityCmaintenanceEnables an AI assistant to query Plaid-synced bank data stored locally in SQLite — balances, transactions, spending, cash flow, recurring charges, and liabilities — plus bounded read-only SQL and local CSV/JSON exports, all over local stdio with no hosted service or listening port.PolyForm Noncommercial 1.0.0
TDQS
Scored across 11 tools
Most tools have distinct resource/action targets, especially around auth, accounts, transactions, and export. There is some potential overlap among list_accounts vs get_account_balance, get_account vs get_account_details, and list_transactions vs export_transactions, but the descriptions generally clarify the boundaries.
All tools use the sb1_ prefix and snake_case, with a predictable verb_noun pattern for most operations. The main minor deviation is sb1_auth_status, which is noun-based rather than verb-based, but it remains readable and consistent overall.
Eleven tools are well scoped for a banking integration focused on authentication, accounts, balances, and transactions. Each tool appears to earn its place without excessive surface area.
The read-oriented lifecycle is well covered: authentication checks, account listing/details/keys/balances, transaction listing/details, and CSV export. Gaps include no child-ID discovery, no credit-card or pension support in some account endpoints, and no payment or transfer operations, though the latter may be intentionally out of scope.