# BankMCP vs Powens (slim)

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

- Full: https://www.anchorterminal.com/compare/bankmcp-vs-powens.md (~4,500 tokens) · this version ~2,630 tokens · JSON https://www.anchorterminal.com/compare/bankmcp-vs-powens.json · canonical https://www.anchorterminal.com/compare/bankmcp-vs-powens
- 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 Powens's 42.8 (E), and leads in 6 of 7 scored categories. Powens leads on transparency & trust. Both do bank account data.

- BankMCP: B 67.1, rank #339 of 1486 · https://www.anchorterminal.com/tools/bankmcp.min.md
- Powens: E 42.8, rank #1253 of 1486 · https://www.anchorterminal.com/tools/powens.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 27; Schema & documentation, 75 against 48; Agent ergonomics, 70 against 57; Security & auth, 69 against 60; Payments & pricing, 60 against 10; Maintenance & community, 80 against 33. Also Runs on your own machine; Open source.
- Powens, good for A European product, strongest in France, that needs account and transaction data plus wealth, loan and document data under Powens' own licence. Ahead on Transparency & trust, 65 against 50. Also A hosted endpoint, with nothing to install.

| Category | BankMCP | Powens |
| --- | --- | --- |
| Reliability (16%) | 63 | 27 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 75 | 48 |
| Agent ergonomics (13%) | 70 | 57 |
| Security & auth (14%) | 69 | 60 |
| Payments & pricing (10%) | 60 | 10 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 33 |
| Transparency & trust (7%) | 50 | 65 |

| Fact (where they differ) | BankMCP | Powens |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | noskillish (open-source project) | Powens SAS |
| Hosted endpoint | no (local only) | `https://{domain}.biapi.pro/2.0` |
| Transports | stdio, Streamable HTTP | HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Free | Paid |
| Licence | MIT | Proprietary service under Powens' General Terms and Conditions of Sale. The Powens Connect iOS SDK on GitHub is LGPL-3.0 |
| Tools exposed | 15 | none |
| MCP registry | `io.github.noskillish/bankmcp` | not listed |
| Last release | 2026-09-28 | none |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | no document linked | no date given |
| 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 | 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 | none |
| Agent reviews | none | 2.3/5 (4) |

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.); Powens 10 (No x402, MPP or L402 (0). No public prices. Fees are set in a purchase order by volume of users (0). A free, self-serve console account with a sandbox domain and a test connector, no card mentioned. No free live tier (10 of 20). A person signs up in the console (0).)
- Maintenance & community, BankMCP +47: 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.); Powens 33 (The public changelog is a Notion page drawn by script and was not read, so recency is taken from the docs sitemap. The newest reference page change is dated 15 September 2026, 24 days before the check, scored 20 of 30 because docs metadata is weaker evidence than a release note. Docs pages changed on two dates in the last 90 days, 31 August and 15 September, and dated changelog entries could not be counted (0 of 20). Closed service with a linked changelog, a support desk on Jira and support hours of 9.30am to 7pm on working days in the conditions of sale (8 of 15). The iOS SDK is at 1.0.0-beta with its last commit on 1 October 2024, Android is marked coming soon, and no server-side SDK was found (3 of 15). The SDK repository holds a binary framework with no CI workflow (2 of 10).)
- Reliability, BankMCP +36: 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.); Powens 27 (Graded with the hosted lines. No status page is linked from the home page, the product pages or the docs read. status.powens.com was a guess that our network could not reach, so this is scored absent and listed as unchecked (0 of 20). No readable incident history (5 of 30). The fair usage policy publishes sandbox limits of 30 calls a minute and 86,400 a day. Production limits are not published (10 of 15). The policy says rate limiting exists and asks for webhooks before polling. No 429 status, Retry-After, backoff guidance or idempotency key was found, and the response code table has no 429 (2 of 15). The conditions of sale carry no uptime figure. The site states 99.9 per cent historical API availability and a committed 95 per cent connection success rate as claims, not as a published SLA (0). Version 2.0 is the current API with no beta label (10).)
- Schema & documentation, BankMCP +27: 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.); Powens 48 (No OpenAPI file or other machine-readable contract was found. The reference is hand-written GitBook tables (0 of 25). Both docs spaces publish llms.txt and a Markdown twin of every page (10). Each resource page opens with what the resource is, and endpoints say which token they need and how soft-deleted items behave. Several endpoints have no description beyond the title (12 of 20). Parameters and objects are in tables with types, required marks and value lists for states and scopes. Configuration and client `config` are free key-value objects (9 of 15). Guides carry curl requests and JSON responses. The reference pages read have few examples, and the errors page lists five common codes and warns that others may appear (9 of 15). The version is in the path (2.0). The changelog is a Notion page that is drawn by script and was not read (8 of 15).)
- Transparency & trust, Powens +15: 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.); Powens 65 (Closed service with public General Terms and Conditions of Sale under French law. The page has no version or date. The iOS SDK is LGPL-3.0 (15 of 30). The conditions of sale include a data protection annex, say collected data is destroyed at most 30 days after the contract ends, and the privacy policy gives retention periods by purpose. Neither page is dated, and the end-user terms say no data leaves the EU while the privacy policy lists business tools with transfers outside it (22 of 30). Obsolete and deprecated items are marked in the docs with no dates, and the conditions of sale say backward compatibility is assured but may be limited, with no notice period (5 of 20). The conditions of sale name Sewan and AWS, OVH and Gemalto in France and Unnax and CRIF in Spain and Italy, and commit to servers in the EU (17 of 20). Regulatory standing counts here as an addition to the checklist, as for the other bank data listings. Powens SAS is a payment institution registered with the ACPR under CIB 16948 (+5).)
- Agent ergonomics, BankMCP +13: 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.); Powens 57 (Lists take `limit` up to 1,000 and `expand` pulls linked resources into one response. No field selection was found (17 of 25). `limit` and `offset` on most lists, opaque cursor links in `_links` on transactions, and `min_date`, `max_date`, `last_update`, value and wording filters (18 of 20). One error format with `code`, `description`, an optional bank message and `request_id`, and advice to branch on the code. The documented code list is short (13 of 20). No idempotency key was found, including on `POST /payments`. Reads are safe to repeat (4 of 20). A first data call needs a console domain, a client application, a user token, a temporary code and a browser consent. `limit` is required on transactions. The only SDK found is an iOS beta from 2024 (5 of 15).)