Is BankWeave MCP server safe?
Probably. Read the findings first.
Use with care. Some checks failed or could not be verified.
What to know before installing
- highRemote endpoint did not respond — HTTP 503
How BankWeave compares
Against every graded Finance MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 58/100
- higher than 16% of 1,761 Finance servers
- Uptime
- 7%
- of our recent checks; the typical remote Finance server answers 100%
Public scan report
scanner v0.1.10 · 2026-10-27 · same rubric, same numbers if you re-run it
1 high
- –Code scanpackage could not be scannedn/a
- Live reliabilityremote unreachable: HTTP 5030/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 9 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- highRemote endpoint did not respond
reliability.unreachableHTTP 503
Overall 58/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Other servers that do what BankWeave does
- RCSB PDBMCP server to search, inspect, and cross-reference RCSB Protein Data Bank structuresnot reviewedGrowingA
BankMCP™Read-only MCP server for your own bank accounts via Enable Banking. Self-hosted, one user.not reviewedEstablishedA- Agent402.Tools: pay-per-call web toolsAgentic Finance: 500+ agent tools, multi-chain USDC over x402 or MPP, or free via proof-of-worknot reviewedEstablishedA