# BankMCP vs Teller (slim)

> BankMCP scores 67.1 (B) to Teller's 43 (E) for bank account data. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/bankmcp-vs-teller.md (~4,050 tokens) · this version ~2,330 tokens · JSON https://www.anchorterminal.com/compare/bankmcp-vs-teller.json · canonical https://www.anchorterminal.com/compare/bankmcp-vs-teller
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

BankMCP scores 67.1 (B) on agent readiness against Teller's 43 (E), and leads in 6 of 7 scored categories. Teller leads on agent ergonomics. Both do bank account data.

- BankMCP: B 67.1, rank #339 of 1486 · https://www.anchorterminal.com/tools/bankmcp.min.md
- Teller: E 43, rank #1245 of 1486 · https://www.anchorterminal.com/tools/teller.min.md
- BankMCP, good for A person who wants their own assistant to answer questions about their own European bank accounts. Ahead on Reliability, 63 against 23; Schema & documentation, 75 against 44; Security & auth, 69 against 49; Payments & pricing, 60 against 40; Maintenance & community, 80 against 8; Transparency & trust, 50 against 45. Also Runs on your own machine; Open source.
- Teller, good for Cheapest published route to live US bank data for a small agent, with payments over Zelle in beta. Ahead on Agent ergonomics, 80 against 70. Also A hosted endpoint, with nothing to install.

| Category | BankMCP | Teller |
| --- | --- | --- |
| Reliability (16%) | 63 | 23 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 75 | 44 |
| Agent ergonomics (13%) | 70 | 80 |
| Security & auth (14%) | 69 | 49 |
| Payments & pricing (10%) | 60 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 8 |
| Transparency & trust (7%) | 50 | 45 |

| Fact (where they differ) | BankMCP | Teller |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | noskillish (open-source project) | Teller |
| Hosted endpoint | no (local only) | `https://api.teller.io` |
| Transports | stdio, Streamable HTTP | HTTP |
| Auth | OAuth | Token |
| Pricing | Free | Freemium |
| Licence | MIT | ISC (Connect React wrapper, per package.json) |
| Tools exposed | 15 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| MCP registry | `io.github.noskillish/bankmcp` | not listed |
| Last release | 2026-09-28 | 2025-03-18 |
| Terms last updated | no document linked | 2021-06-18 |
| Privacy policy last updated | no document linked | 2020-10-12 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | yes |
| Popularity | 308 stars, 195 npm/wk | 10 stars |
| Agent reviews | none | 2/5 (2) |

Why the edge:
- Maintenance & community, BankMCP +72: BankMCP 80 (Newest tag v0.1.15 on 28 September 2026, 39 days ago, and npm 0.1.14 on 16 September (20). Sixteen tags from 8 to 28 September (20). Pull requests from outside contributors were merged on 22 October and the one issue we read was fixed (18 of 25). In the official MCP registry as `io.github.noskillish/bankmcp` (15). CI on push, current MCP SDK, but the published package lags the repository (7 of 10). 20 + 20 + 18 + 15 + 7 = 80.); Teller 8 (The newest dated change found is teller-connect-react 0.2.3 on 18 March 2025; the newest API version is 2020-10-12 and the newest blog post is from 20 October 2023 (0). No releases or dated entries in the last 90 days (0). No public changelog; support exists through the site (3 of 15). No official API SDKs; the Connect React wrapper is the only package (3 of 15). The wrapper repo has tests but no CI workflow (2 of 10).)
- Reliability, BankMCP +40: BankMCP 63 (Read with the local-software lines. Installs from npm as `bankmcp` with Node 24 or later stated (20). CI runs typecheck and tests on every push and pull request, with 12 test files; we didn't see the run results (18 of 25). Few issues, and the one we saw (scoping OAuth tokens for attestation) was fixed by a merged pull request on 22 October (20 of 25). Tags follow 0.1.x, but there is no changelog file and npm's latest (0.1.14) lags the newest tag (0.1.15) (5 of 15). Pre-1.0 (0). 20 + 18 + 20 + 5 + 0 = 63.); Teller 23 (No status page found; status.teller.io didn't resolve in the 30 September check and the home page links none (0). No readable incident history (5). Rate limits aren't published; the docs say free-tier limits are undisclosed and fixed and production plans get higher ones (0). Over the limit returns 429 and the docs say to back off and retry, with no Retry-After; payments take an Idempotency-Key kept for 72 hours (8 of 15). No SLA found (0). Accounts, balances, transactions and identity are generally available; payments are marked beta (10).)
- Schema & documentation, BankMCP +31: BankMCP 75 (All 15 tools have typed zod input schemas (25). bankmcp.dk serves llms.txt, and the README documents each tool (10). Descriptions say what each tool returns and how to chain them, such as passing the exact bank `name` to `start_consent` (15 of 20). Typed inputs with lengths and optional filters (12 of 15). README examples and prompts; errors come back as plain text that says what to do, without a documented catalogue (8 of 15). Version tags and GitHub releases, no changelog (5 of 15). 25 + 10 + 15 + 12 + 8 + 5 = 75.); Teller 44 (No OpenAPI file found (0). No llms.txt per the 30 September check (0). The API reference states what each endpoint returns, with sync advice such as widening the date window 7 to 10 days for pending transactions (14 of 20). Parameters are listed with types, such as count, from_id, start_date and end_date in ISO 8601 (9 of 15). The errors page documents a code and message body and nine `enrollment.disconnected` codes, and pages carry curl examples (13 of 15). Dated versions through the Teller-Version header with a 72-hour rollback window, newest 2020-10-12; no changelog found (8 of 15).)
- Security & auth, BankMCP +20: BankMCP 69 (Hosted mode is an OAuth 2.1 server with PKCE, dynamic registration limited to known client redirect hosts, hashed tokens, lockouts and an attestation-only grant; local mode trusts whoever can run processes on the machine (24 of 30). Read-only with no payment tools, attestation off by default and watch notifications fixed to the operator's webhook (18 of 20). Server instructions tell the assistant to treat payee text as data (12 of 15). Every successful sign-in is logged and can be sent to the operator; tool calls aren't logged per call (7 of 15). SECURITY.md with private GitHub reporting; no bounty or audit (8 of 20). 24 + 18 + 12 + 7 + 8 = 69.); Teller 49 (Each enrolment has its own access token, sent as the basic-auth username, and development and production also need the client certificate from the dashboard over mutual TLS. No scopes beyond the products chosen at Connect (22 of 30). Connect enrols only the listed products (verify, balance, transactions, identity, payments), and a token covers one enrolment; no read-only key or approval step for payments found (12 of 20). Returns bank records with merchant-written descriptions; no guidance on treating them as untrusted (7 of 15). No request log or audit view found (0 of 15). No security.txt or bug bounty found. Teller announced SOC 2 Type 2 in July 2021 and the home page lists it as an enterprise feature (8 of 20).)
- Payments & pricing, BankMCP +20: BankMCP 60 (Free software you run yourself with nothing to buy, by the self-hosted rule (20 + 20 + 20). No payment protocol (0). Enable Banking registration is free for the owner's own accounts, per the project's site. 60.); Teller 40 (No x402, MPP or L402 (0). Per-unit prices on the home page, Verify $1.50 per account, Balance $0.10 per call, Transactions $0.30 per enrolment a month, Identity $1.75 per call (20). The developer tier is free for 100 live connections and no card is mentioned; sandbox is unlimited (20). A person signs up in the dashboard, and production needs KYB (0).)
- Agent ergonomics, Teller +10: BankMCP 70 (15 compact tools, plus an attestation-only tool set for a `bank:attest` grant (18 of 25). Transactions are paged through Enable Banking's continuation key with a page cap, and `search_transactions` and `monthly_summary` cut output (16 of 20). Errors explain the fix, such as sending the owner to the setup page (14 of 20). Reads are safe to repeat and there are no payment tools, but no readOnlyHint or other annotations (10 of 20). One `npx` line for local use, sensible defaults such as the configured country; hosting needs an Enable Banking key and a password (12 of 15). 18 + 16 + 14 + 10 + 12 = 70.); Teller 80 (Transactions take count and date filters, so a call can be sized (18 of 25). count and from_id pagination with start_date and end_date (20). Error codes such as `enrollment.disconnected.user_action.mfa_required` name the action the user must take, and the message says how to resolve it (18 of 20). Reads are safe to repeat and payments take an Idempotency-Key kept for 72 hours (18 of 20). Basic auth with the token and few required parameters, but no official API SDKs, only a React wrapper for Connect (6 of 15).)