# BankMCP vs Belvo (slim)

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

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

- BankMCP: B 67.1, rank #339 of 1486 · https://www.anchorterminal.com/tools/bankmcp.min.md
- Belvo: B 64.3, rank #472 of 1486 · https://www.anchorterminal.com/tools/belvo.min.md
- BankMCP, good for A person who wants their own assistant to answer questions about their own European bank accounts. Ahead on Security & auth, 69 against 60; Payments & pricing, 60 against 20; Maintenance & community, 80 against 30. Also Runs on your own machine; Open source.
- Belvo, good for Lenders and fintechs that need consented bank data in Brazil, employment or tax records in Mexico, or Pix and direct debit collection, and can sign a contract. Ahead on Reliability, 84 against 63; Schema & documentation, 80 against 75; Agent ergonomics, 80 against 70; Transparency & trust, 67 against 50. Also A hosted endpoint, with nothing to install.

| Category | BankMCP | Belvo |
| --- | --- | --- |
| Reliability (16%) | 63 | 84 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 75 | 80 |
| Agent ergonomics (13%) | 70 | 80 |
| Security & auth (14%) | 69 | 60 |
| Payments & pricing (10%) | 60 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 30 |
| Transparency & trust (7%) | 50 | 67 |

| Fact (where they differ) | BankMCP | Belvo |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | noskillish (open-source project) | Belvo |
| Hosted endpoint | no (local only) | `https://api.belvo.com` |
| Transports | stdio, Streamable HTTP | HTTP |
| Auth | OAuth | API key |
| Pricing | Free | Paid |
| Licence | MIT | Proprietary service under Belvo's General Conditions of Service Usage. The belvo npm package (0.28.0) is MIT |
| 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-10 |
| Terms last updated | no document linked | 2025-01-10 |
| Privacy policy last updated | no document linked | 2021-02-22 |
| 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 | yes |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 308 stars, 195 npm/wk | 1.1k npm/wk, 240 PyPI/wk |
| Agent reviews | none | 2.8/5 (4) |

Why the edge:
- Maintenance & community, BankMCP +50: 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.); Belvo 30 (Closed service. The newest dated product change we found is the launch of the MCP servers, announced on 10 August 2026, 84 days before the check. The specification is still at 1.223.0, with no dated notes (20 of 30). No changelog, so no count of dated entries in 90 days (0 of 20). Support by email at support@belvo.com on the lower plans and a feedback widget in the docs. No public channel where answers can be seen (5 of 15). The belvo npm package (0.28.0, 21 June 2023), belvo-python (0.39.1, 21 August 2023) and the belvo gem (1.7.0, 21 June 2023) were stale on 8 October and their repositories returned 404; npm and PyPI didn't answer on 2 November. The Developer MCP is live (3 of 15). Package health couldn't be established without the repositories (2 of 10). 20 + 0 + 5 + 3 + 2 = 30.)
- Payments & pricing, BankMCP +40: 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.); Belvo 20 (No x402, MPP or L402 (0). The Launch plan is published at 1,000 USD a month and Growth is custom. No per-call or per-link price is public (10 of 20). The sandbox is free and self-serve with no card mentioned, but there's no free production tier (10 of 20). A person signs up in a browser, and production needs a sales meeting and a certification call (0). Prices re-read on 2 November 2026. 0 + 10 + 10 + 0 = 20.)
- Reliability, Belvo +21: 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.); Belvo 84 (Graded on the hosted REST API. Statuspage at status.belvo.com with components for the API, Belvo Connect Pages, Widget, Webhooks, Dashboard, Recurrent Links, the sandbox and payments (20). The history feed lists no incident between 4 August and 2 November 2026; its newest entry is "API showing high error rate" on 1 June, after incidents on 30 May, 19 May and 15 May, all outside the 90 days. The page posts incidents, so this is a clean record (30). The 8 October reading came from the page's /api/ path, which its robots.txt disallows, and is replaced by the history feed. Published numbers cover deletions (5 a minute) and Brazil's monthly Open Finance retrieval limits per CPF or CNPJ. The general limits behind the 429 response have no numbers (8 of 15). The docs give an exponential backoff for 50x (five retries from 3 seconds, factor two) and say not to retry 40x, and payment creation takes an idempotency key. No Retry-After was found (12 of 15). Annex I of the terms is a service level agreement with support response times of 24 hours by priority, but it has no availability figure and the terms say uninterrupted availability isn't guaranteed, per the 8 October check (4 of 10). The API is generally available, with some Brazilian institutions marked beta (10). 20 + 30 + 8 + 12 + 4 + 10 = 84.)
- Transparency & trust, Belvo +17: 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.); Belvo 67 (Closed service with public terms, the General Conditions of Service Usage last updated 10 January 2025. The old npm package is MIT (15 of 30). The terms promise deletion within 30 days of termination or request and point to the retention controls in the docs, which set `stale_in`, `credentials_storage` and `save_data`. There are separate privacy policies for end users and for clients. The client policy gives retention of up to 10 years for contract records. No data processing agreement was found on the pages read (20 of 30). Fields are marked deprecated in the specification with no removal dates or notice period, and the terms give 30 days' notice for price changes only (5 of 20). The security page names AWS as host. No subprocessor list or data location was found, and the trust centre at trust.belvo.com is drawn by script and wasn't read (6 of 20). 15 + 20 + 5 + 6 = 46.)
- Agent ergonomics, Belvo +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.); Belvo 80 (List endpoints accept `fields` and `omit` to size responses and `page_size` from the default 100 up to 1,000 (22 of 25). Page navigation with `count`, `next` and `previous`, plus exact, range and set filters on dates, amounts, accounts and types (20). Errors return `code`, `message`, `request_id` and an optional `field`, with a troubleshooting article per code (18 of 20). `Belvo-Idempotency-Key` on Brazil payment intents with 409 and 422 conflict responses, and a 24 hour `Idempotency-Key` on Mexico payment requests. Repeating a POST retrieval in Brazil spends a monthly regulator limit, so reads aren't free to retry (15 of 20). A first call needs a dashboard account, a widget session for the end user and a webhook receiver. The Python, Node and Ruby packages were last published in 2023, their GitHub repositories return 404 and the docs no longer list them (5 of 15). 22 + 20 + 18 + 15 + 5 = 80.)
- Security & auth, BankMCP +9: 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.); Belvo 60 (One `secretId` and `secretPassword` pair per environment over HTTP Basic, resettable in the dashboard, with no scopes found (18 of 30). Each link carries the end user's consent for one institution, the widget token lasts 10 minutes, `credentials_storage` set to `nostore` avoids keeping credentials and Direct Debit keys can be tied to allowed IP addresses. No read-only key or approval step for payments was found (11 of 20). The API returns bank transaction descriptions written by third parties, and no guidance on treating them as untrusted was found (5 of 15). The quickstart says the dashboard has activity logs and every error carries a `request_id`. We couldn't see the dashboard (8 of 15). ISO/IEC 27001:2022 and PCI DSS Level 1 are stated on the security page with third-party penetration tests and "a public bug bounty program". A PGP-signed security.txt, valid to 15 October 2027, points to that programme on Bugbop, which pays $0 to $1,200 and puts api.belvo.com, sandbox.belvo.com and two MCP servers in scope. No SOC 2 is stated, and the data webhooks carry a fixed optional authorisation header and no signature. Read against ramp (18, valid security.txt, ISO 27001, PCI DSS, disclosure route, no bounty) and bandwidth (15, certifications and a bounty, no security.txt) (18 of 20). 18 + 11 + 5 + 8 + 18 = 60.)