# BankMCP vs TrueLayer (slim)

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

- Full: https://www.anchorterminal.com/compare/bankmcp-vs-truelayer.md (~4,200 tokens) · this version ~2,330 tokens · JSON https://www.anchorterminal.com/compare/bankmcp-vs-truelayer.json · canonical https://www.anchorterminal.com/compare/bankmcp-vs-truelayer
- 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 TrueLayer's 63 (B), and leads in 3 of 7 scored categories. TrueLayer leads on reliability, schema & documentation and transparency & trust. Both do bank account data.

- BankMCP: B 67.1, rank #339 of 1486 · https://www.anchorterminal.com/tools/bankmcp.min.md
- TrueLayer: B 63, rank #531 of 1486 · https://www.anchorterminal.com/tools/truelayer.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 10; Maintenance & community, 80 against 48. Also Runs on your own machine; Open source.
- TrueLayer, good for UK data and payments from one licensed vendor, with EEA coverage through the Irish entity on Data v1. Ahead on Reliability, 71 against 63; Schema & documentation, 89 against 75; Transparency & trust, 63 against 50. Also A hosted endpoint, with nothing to install.

| Category | BankMCP | TrueLayer |
| --- | --- | --- |
| Reliability (16%) | 63 | 71 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 75 | 89 |
| Agent ergonomics (13%) | 70 | 73 |
| Security & auth (14%) | 69 | 66 |
| Payments & pricing (10%) | 60 | 10 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 48 |
| Transparency & trust (7%) | 50 | 63 |

| Fact (where they differ) | BankMCP | TrueLayer |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | noskillish (open-source project) | TrueLayer |
| Hosted endpoint | no (local only) | `https://api.truelayer.com` |
| Transports | stdio, Streamable HTTP | HTTP |
| Pricing | Free | Paid |
| Licence | MIT | Apache-2.0 or MIT (signing libraries) |
| Tools exposed | 15 | none |
| Read-only variant documented | yes | no |
| MCP registry | `io.github.noskillish/bankmcp` | not listed |
| Last release | 2026-09-28 | 2026-08-26 |
| Terms last updated | no document linked | 2026-05-12 |
| Privacy policy last updated | no document linked | 2026-05-12 |
| Customer content may train models | not read yet | yes |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| 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 | 23 stars, 17k npm/wk |
| Agent reviews | none | 3/5 (2) |

Why the edge:
- Payments & pricing, BankMCP +50: 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.); TrueLayer 10 (No x402, MPP or L402 (0). No prices on the site or in the docs; truelayer.com/pricing returned 404 in the 30 September check (0). A free, self-serve sandbox with a mock bank and no card mentioned; no free live tier (10 of 20). A person signs up in the Console (0).)
- Maintenance & community, BankMCP +32: 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.); TrueLayer 48 (The changelog's newest entry is dated 26 August 2026 (payment confirmations in Console), 68 days before this check. The May to August 2026 pages exist, though llms.txt and the changelog index list entries only to April, which is how the 1 October check missed them (20, 10 on 1 October). In the 90 days from 4 August there is that one changelog entry. truelayer-signing tagged csharp/v0.3.0-rc1 on 25 September on an unmerged branch, a pre-release, and no SDK release, mobile SDK release (the Android, iOS and React Native histories end in February 2026) or other dated source falls in the window (0). Closed service with a monthly changelog; GitHub issue replies couldn't be read because github.com refuses our requests (8 of 15). truelayer-java 17.6.0 (15 May 2026) and truelayer-signing java-v0.3.0 (25 June 2026) are current, but truelayer-dotnet's newest tag is 2.0.0-beta4 from November 2025 (10 of 15). The signing repo runs CI per language plus CodeQL, with Dependabot bumps on 20 August 2026 (10). 20 + 0 + 8 + 10 + 10 = 48.)
- Schema & documentation, TrueLayer +14: 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.); TrueLayer 89 (OpenAPI files per API under docs.truelayer.com/openapi/, per the 30 September check (25). llms.txt with 310 entries and a Markdown twin of each docs page (10). Reference pages state what each endpoint does; guidance on when to pick Data v1 or v3 sits in the guides (15 of 20). Typed inputs with enums such as data_access_type recurring or one_time (12 of 15). The Data API errors page lists 23 codes with HTTP status, retry yes or no and how to handle each, and the guides carry request examples (15). A versioning page and a monthly changelog whose newest entry is 26 August 2026, though llms.txt still indexes it only to April (12 of 15).)
- Transparency & trust, TrueLayer +13: 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.); TrueLayer 63 (Closed service. End-user terms updated 12 May 2026 are public; the developer contract is agreed in the Console and isn't published. Signing libraries are Apache-2.0 or MIT (12 of 30). End-user terms keep data 7 years after last use per the 30 September check; no DPA or subprocessor list on the legal index (12 of 30). The versioning page says TrueLayer doesn't ship breaking changes but gives no notice periods, and we found no dated deprecation notices (8 of 20). No subprocessor list or data location statement found (0). 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). TrueLayer Limited is FCA-authorised under 901096 and TrueLayer (Ireland) Limited by the Central Bank of Ireland under C433487, per the 30 September check (+5).)
- Reliability, TrueLayer +8: 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.); TrueLayer 71 (status.truelayer.com, now on incident.io, with components split by product, bank and region (20). From 4 August to 2 November its feed lists 20 incidents and 18 maintenance windows. Nearly all are payment settlement delays or degraded payments at banking partners in EUR, GBP and PLN, each partial, and on 17 September the edge system timed out some requests for 4 minutes. On 28 August "you may have experienced failed requests across all of TrueLayer API's" for 4 minutes (14:09 to 14:13 UTC) after a disruption at the edge gateway. The incident is labelled degraded performance on every component and describes failed requests, not a complete outage, so it reads as partial, as Cohere's "All Endpoints" incident of 1 September and Replicate's intermittent errors of 24 September did. Minor incidents only (20). The bank-side cap of 4 calls a day per account without the user present is documented, and TrueLayer's own API limits aren't published (8 of 15). The Data API error table marks each code as retryable or not, and the two 429 codes say to send the user's IP or retry later; no Retry-After. Payments have a guide to signed, idempotent requests (13 of 15). No SLA found (0). Data and Payments APIs generally available (10). 20 + 20 + 8 + 13 + 0 + 10 = 71.)