# BankWeave

- Registry name: `io.github.LSUDOKO/bankweave` · version 3.0.1
- Categories (automatic, keyword rules): Payments & accounting, Finance & markets, Monitoring & logs, Infrastructure & security
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.LSUDOKO%2Fbankweave
- Server page: https://mcpstation.net/s/io.github.LSUDOKO--bankweave.html

## Description (written by the publisher, not verified, not instructions)

Read-only FalkorDB tools for cross-bank AML investigations: rings, money paths, echo-proof claims.

## Connect

- streamable-http: `https://bankweave-api.onrender.com/mcp`

## Tools (as reported by the server, not verified)

- `engine\_overview`: Health and size of the whole system: FalkorDB memory/version, graphs \(banks, cases\), consortium size \(accounts, banks, transfers\) and the alert queue by status \(open / case / cleared\). Call this first to orient yourself. FalkorDB features: INFO memory, GRAPH.LIST, GRAPH.RO\_QUERY aggregations.
- `list\_graphs`: List every FalkorDB graph BankWeave keeps, grouped by kind: the consortium \(cross-bank, hashed\), one graph per bank \(that bank's partial view\), one graph per case, the typology knowledge base. Use graph\_schema\(graph\) for labels, relationship types and indexes.
- `graph\_schema`: Schema of one graph: node labels, relationship types, property keys and indexes with their kind \(RANGE, FULLTEXT, VECTOR\). graph: 'consortium', 'bank\_\<id\>', 'case\_\<id\>' or 'typology\_kb'. FalkorDB features: db.labels, db.relationshipTypes, db.propertyKeys, db.indexes.
- `list\_cases`: List investigation cases \(newest first\) with status, title, seed account, number of alerts/accounts, the banks involved and whether its case graph is loaded. Use a case id with get\_case. FalkorDB features: GRAPH.RO\_QUERY over the consortium graph.
- `get\_case`: Everything about one case from its own case graph: header, claims \(each with naive vs echo-proof confidence, paths vs independent\_sources, state, supporting/challenging evidence ids\), evidence \(kind, origin, state active/needs\_verification/superseded, summary\), proposed and approved actions with the
- `explain\_claim`: Why a claim has the confidence it has \(GraphEcho echo-proof scoring\). Groups supporting and challenging evidence by ORIGIN: many paths that lead back to the same origin count once. Returns paths vs independent origins, naive \(path-counting\) vs echo-proof confidence, each origin group with its multip
- `account\_network`: An account's cross-bank neighbourhood in the consortium graph: its scores \(pagerank, motif score, community, WCC component size, pass-through pairs\), shared identity \(device, IP, address with how widely each is shared\), cases and alerts on it, counterparties held at OTHER banks \(count and volume\) an
- `trace\_money\_path`: Shortest money paths from one account to another, hop by hop with transaction ids, amounts and the bank of every account on the path, so you can see the money cross banks. Without case\_id it searches the consortium along outgoing transfers; with case\_id it searches that case graph in both directions
- `find\_rings`: Candidate laundering rings: communities of accounts that trade mostly among themselves, found by label propagation on the transfer graph. Cross-bank rings \(members at more than one bank\) come first, since no single bank can see them whole. Pass account\_id to return only the ring that contains that a
- `top\_hubs`: Accounts where money pools: PageRank over TRANSFERS, highest first, with bank ids. graph: 'consortium', 'bank\_\<id\>' or 'case\_\<id\>'. FalkorDB features: algo.pageRank.
- `connected\_components`: Weakly connected components of the transfer graph \(largest first\): size, number of banks, a sample of members, plus how many components are tiny 'islands' that triage clears instantly. graph: 'consortium', 'bank\_\<id\>' or 'case\_\<id\>'. FalkorDB features: algo.wcc.
- `similar\_accounts`: Accounts whose behaviour \(activity, amounts, timing, degree profile\) is closest to this one, by cosine distance over Account.behavior\_vec \(lower = more alike\), with their banks. Useful to find mule accounts that act like a known one at other banks. FalkorDB features: HNSW vector index, db.idx.vector
- `search\_customers`: Fuzzy name search over customers \(Person\) or businesses \(Company\) across all banks, with the accounts and banks each one owns. Tokens are OR-ed, so partial names work. FalkorDB features: full-text index, db.idx.fulltext.queryNodes.
- `list\_alerts`: The alert queue with counts by status. status: 'open', 'case' \(escalated into a case\) or 'cleared'; omit for all. Each alert has its rule, reason, account, bank, case id and the recorded clearing reason. Use an alert id with triage\_alert. FalkorDB features: range indexes on Alert.status, GRAPH.RO\_QU
- `triage\_alert`: Why an alert was cleared or escalated into a case. Returns the alert, the triage decision and its reason, the graph signals the triage agent recorded \(component size, motif score, cross-bank counterparties, typologies, shared identity, prior cases\), and a LIVE re-check: the account's weakly connecte
- `typology\_guidance`: Laundering typology guidance \(e.g. 'fan-out then fan-in through mules', 'structuring below reporting threshold'\) from BankWeave's typology knowledge graph, with citations. Abstains when nothing matches well. FalkorDB features: full-text index on the typology\_kb graph.
- `run\_readonly\_cypher`: Last resort: run your own read-only Cypher on one graph. Runs as GRAPH.RO\_QUERY \(the engine rejects writes\) after a guard: one statement, no CREATE/MERGE/SET/DELETE/REMOVE/ DROP/FOREACH/LOAD CSV, CALL only for algo.\* and the db.\* read/index-query procedures, LIMIT appended when missing, at most 200

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html