BankWeave

Name: BankWeave
Author: LSUDOKO

MCP serverMCP

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

by LSUDOKOrepository ↗homepage ↗v3.0.1

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"bankweave","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability24/25 checks ok

when	check	result	http	latency	detail
3 min ago	mcp initialize	failed	503	207 ms	http 503
7 h ago	mcp initialize	ok	200	212 ms	server bankweave 1.0.0 · protocol 2025-06-18 · 17 tools
14 h ago	mcp initialize	ok	200	193 ms	server bankweave 1.0.0 · protocol 2025-06-18 · 17 tools
20 h ago	mcp initialize	ok	200	497 ms	server bankweave 1.0.0 · protocol 2025-06-18 · 17 tools
27 h ago	mcp initialize	ok	200	212 ms	server bankweave 1.0.0 · protocol 2025-06-18 · 17 tools
34 h ago	mcp initialize	ok	200	498 ms	server bankweave 1.0.0 · protocol 2025-06-18 · 17 tools
2 d ago	mcp initialize	ok	200	209 ms	server bankweave 1.0.0 · protocol 2025-06-18 · 17 tools
2 d ago	mcp initialize	ok	200	507 ms	server bankweave 1.0.0 · protocol 2025-06-18 · 17 tools
2 d ago	mcp initialize	ok	200	203 ms	server bankweave 1.0.0 · protocol 2025-06-18 · 17 tools
2 d ago	mcp initialize	ok	200	184 ms	server bankweave 1.0.0 · protocol 2025-06-18 · 17 tools

Tools observed via MCP handshake

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 sta
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 pe
graph_schema — Schema of one graph: node labels, relationship types, property keys and indexes with their kind (RANGE, FULLTEXT, VECTOR). graph: 'consortium', 'bank_<id>',
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
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
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
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
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 mon
find_rings — Candidate laundering rings: communities of accounts that trade mostly among themselves, found by label propagation on the transfer graph. Cross-bank rings (
top_hubs — Accounts where money pools: PageRank over TRANSFERS, highest first, with bank ids. graph: 'consortium', 'bank_<id>' or 'case_<id>'. FalkorDB features: algo.
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' t
similar_accounts — Accounts whose behaviour (activity, amounts, timing, degree profile) is closest to this one, by cosine distance over Account.behavior_vec (lower = more alik
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
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,
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 (compo
typology_guidance — Laundering typology guidance (e.g. 'fan-out then fan-in through mules', 'structuring below reporting threshold') from BankWeave's typology knowledge 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/SE

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.LSUDOKO/bankweave

first seen 7 d ago · fetched 3 d agoopen ↗

Field history (7 recent events)

7 d ago · declared · summary → "Read-only FalkorDB tools for cross-bank AML investigations: rings, money paths, echo-proof claims."
7 d ago · declared · description → "Read-only FalkorDB tools for cross-bank AML investigations: rings, money paths, echo-proof claims."
7 d ago · declared · publisherName → "LSUDOKO"
7 d ago · declared · homepageUrl → "https://bankweave.vercel.app"
7 d ago · declared · repoUrl → "https://github.com/LSUDOKO/BankWeave"
7 d ago · declared · version → "3.0.1"
7 d ago · declared · protocols → ["mcp"]

BankWeave

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from