# BankMCP vs Plaid (slim)

> Plaid and BankMCP score within a point of each other for bank account data, 67.8 and 67.1 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/bankmcp-vs-plaid.md (~4,150 tokens) · this version ~2,280 tokens · JSON https://www.anchorterminal.com/compare/bankmcp-vs-plaid.json · canonical https://www.anchorterminal.com/compare/bankmcp-vs-plaid
- 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)

Plaid and BankMCP score within a point of each other on agent readiness, 67.8 (B) and 67.1 (B). BankMCP leads on payments & pricing. Both do bank account data.

- BankMCP: B 67.1, rank #339 of 1486 · https://www.anchorterminal.com/tools/bankmcp.min.md
- Plaid: B 67.8, rank #304 of 1486 · https://www.anchorterminal.com/tools/plaid.min.md
- BankMCP, good for A person who wants their own assistant to answer questions about their own European bank accounts. Ahead on Payments & pricing, 60 against 15. Also No incidents deducted, where Plaid loses 3 points for them.
- Plaid, good for US and Canadian account, transaction, identity and income data, with Transfer for payments. Ahead on Reliability, 73 against 63; Schema & documentation, 93 against 75; Agent ergonomics, 82 against 70; Transparency & trust, 79 against 50. Also A hosted endpoint, with nothing to install.

| Category | BankMCP | Plaid |
| --- | --- | --- |
| Reliability (16%) | 63 | 73 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 75 | 93 |
| Agent ergonomics (13%) | 70 | 82 |
| Security & auth (14%) | 69 | 67 |
| Payments & pricing (10%) | 60 | 15 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 83 |
| Transparency & trust (7%) | 50 | 79 |

| Fact (where they differ) | BankMCP | Plaid |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | noskillish (open-source project) | Plaid |
| Hosted endpoint | no (local only) | `https://production.plaid.com` |
| Transports | stdio, Streamable HTTP | HTTP, stdio, Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Free | Paid |
| Licence | MIT | MIT (SDKs and MCP server) |
| Tools exposed | 15 | 4 |
| Read-only variant documented | yes | no |
| MCP registry | `io.github.noskillish/bankmcp` | not listed |
| Last release | 2026-09-28 | 2026-10-27 |
| Terms last updated | no document linked | 2025-12-01 |
| Privacy policy last updated | no document linked | 2025-12-01 |
| 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 | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 308 stars, 195 npm/wk | 586 stars, 1.3M npm/wk, 657k PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |

Why the edge:
- Payments & pricing, BankMCP +45: 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.); Plaid 15 (No x402, MPP or L402 (0). No prices without a login. The pricing page names Pay as you go, Growth and Custom and still says the first 200 calls are free, with rates shown only after a Production application (0). Sandbox is free, needs no card and doesn't expire; the Trial plan's 10 free Production Items in the US and Canada is per the 30 September check, and we didn't confirm whether it asks for a card (15 of 20). A person signs up in a browser and applies for Production (0).)
- Transparency & trust, Plaid +29: BankMCP 50 (MIT, source public (30). The README and site say what is stored (consents, account ids, watches, hashed tokens) and that balances and transactions aren't, and that data passes through Enable Banking (25 of 30). No deprecation policy for a 0.1 project (3 of 20). The README says it sends no telemetry (20). 30 + 25 + 3 + 20 = 78.); Plaid 79 (Closed service with published developer policy and end-user agreements per region; SDKs and the sandbox MCP server are MIT (15). End User Privacy Policy updated 8 December 2025 says data is kept only as long as needed, with listed exceptions and no periods; no DPA or subprocessor list on the legal index (15 of 30). Dated deprecations in the changelog, such as account subtype changes on 11 October 2026 and the Cash Flow Updates migration deadline of 20 August 2027 (20). Data from the UK and EEA is transferred to the US and stored in AWS regions; no named subprocessor list found (8 of 20). Regulatory standing counts here as an addition to the checklist (+5 for a named regulator with a register number, +3 for a named regulator alone). The privacy policy says Plaid Financial Ltd answers to the FCA and Plaid B.V. to De Nederlandsche Bank, with no firm reference numbers on the page, and the US has no AISP licence to hold (+3).)
- Schema & documentation, Plaid +18: 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.); Plaid 93 (Public OpenAPI file in plaid/plaid-openapi, at 2020-09-14_1.778.0 per the plaid-node 49.0.0 changelog (25). llms.txt with about 250 entries and a Markdown twin of each docs page (10). Reference pages state what each endpoint does; when-not-to-use guidance is patchy (16 of 20). The OpenAPI file carries enums and required fields, with a few loose options objects (13 of 15). Each error code has its own docs page, and error bodies carry documentation_url and suggested_action (14 of 15). Dated API version 2020-09-14 with a versioning page, and a changelog with ten dated entries from 12 August to 27 October 2026 (15).)
- Agent ergonomics, Plaid +12: 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.); Plaid 82 (Response size controls include the /transactions/sync cursor with count, count and offset on /transactions/get, and account_ids filters (18 of 25). Cursor and offset pagination with filters (20). Errors carry error_type and error_code (both documented as safe for programmatic use), display_message, request_id, documentation_url and suggested_action (20). Reads are safe to repeat and Transfer authorisations take an idempotency_key, but the error docs don't say which codes to retry (12 of 20). Official SDKs released together, plaid-node 49.0.0 and plaid-python 46.0.0 on 19 October 2026, and plaid-go v49.0.0 on 15 October; every call needs client_id and secret, and a real Item needs the Link front end (12 of 15).)
- Reliability, Plaid +10: 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.); Plaid 73 (status.plaid.com, now an incident.io page, with an API component and per-bank incidents and an Atom feed (20). From 3 August to 1 November 2026 the feed lists 17 incidents. Ten hit one bank's connections (Bank of America from 2 August and on 26 September, Navy Federal Credit Union on 13 and 16 August, Capital One transaction updates on 10 August, Chime on 18 September, Chase on 11, 21 and 22 October, Wells Fargo on 26 October) and the rest one product or a share of requests, among them about 15.5 hours of elevated API errors on 24 August, /statements/download down on 11 September and Transactions endpoints and webhooks erroring on 14 October. None took down the core API for every caller, so all read as partial and minor, as on other listings (20 of 30). Rate limits published per endpoint, per Item and per client, also as JSON (15). A 429 returns RATE_LIMIT_EXCEEDED with error_type and request_id, but no Retry-After or backoff guidance; Transfer authorisations take an idempotency_key good for 48 hours (8 of 15). No SLA found (0). Core API generally available (10). 73.)