banker-hub-mcp
Related Servers
Alternatives to banker-hub-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceExposes a local inference ledger over MCP stdio, letting agents query request counts, token usage, TTFT, energy consumption, local costs, cloud-equivalent costs, savings percentages, and per-model breakdowns from an OpenAI-compatible proxy's SQLite ledger. Provides four read-only tools so coding agents can answer questions about home GPU inference economics without opening a browser.41MIT
- AlicenseNot gradedqualityBmaintenanceProvides LLM clients with market intelligence tools over stdio, including market snapshots, price history, sentiment scoring, evidence search, and research briefs, with saved-run resource access.AGPL 3.0
- FlicenseNot gradedqualityCmaintenanceProvides AI agents read-only analytical access to a SQLite database over stdio, with tools for listing tables, describing schemas, and running paginated SQL queries.-
- AlicenseNot gradedqualityBmaintenanceExposes read-only local analysis tools for source auditing, web traffic review, binary reverse engineering, exploit scaffolding, OSINT, and reporting via JSON-RPC over stdio, enabling LLMs to orchestrate evidence-based security workflows without executing targets or sending network requests.1MIT
- AlicenseNot gradedqualityAmaintenanceExposes read-only tools over stdio that let an agent search the user's past Claude Code sessions by keyword and meaning, open exchanges with their neighbours, brief whole sessions, and trace everything touching a file, commit, PR or URL. The agent retrieves for itself and answers from what comes back, so it can recall what was said or decided in earlier conversations without leaving the machine.210 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants and MCP clients to access personal finance data through LunchMoney's API, covering transactions, categories, tags, recurring items, budgets, manual and Plaid accounts, crypto, and balance history. Supports full CRUD operations with token-efficient responses and stdio or remote HTTP transport.22 npm-
TDQS
Scored across 5 tools
Each tool has a clearly distinct scope: source discovery, per-source transaction listing, single-transaction fetch by id, and aggregate summary. The two source-specific listers are separated by source, and get_transaction is distinguished by singular lookup, so there is no meaningful overlap.
All tool names use a consistent snake_case verb_noun pattern: list_sources, get_binance_transactions, get_bnc_transactions, get_transaction, and get_summary. The source-specific tools follow the predictable get_<source>_transactions convention.
Five tools is well within the ideal 3-15 range and each has a clear read-only responsibility. There are no redundant or filler tools for the server's transaction-querying purpose.
The surface covers the core read workflows: discovering sources, paging transactions per source, fetching a single transaction, and computing totals. Minor gaps remain, such as a unified cross-source transaction listing and richer account/balance operations, but agents can work around these by querying per source.