io.github.LSUDOKO/bankweave

Est-ce que io.github.LSUDOKO/bankweave est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.LSUDOKO/bankweave » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 17 outils

• account_network≈ 224 tokens

  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) and its bounded 1-2 hop neighbourhood with the banks it spans. A bank alone only sees its own side of these links. FalkorDB features: GRAPH.RO_QUERY, bounded undirected expansion.

  Paramètres, retour & exemple (2)

  Paramètres

  • depth · integer · optionnel
  • account_id · string · requis

  Exemple d'appel

  {"name": "account_network", "arguments": {"account_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• connected_components≈ 166 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • graph · string · optionnel
  • limit · integer · optionnel

  Exemple d'appel

  {"name": "connected_components", "arguments": {"graph": "texte", "limit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• engine_overview≈ 139 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "engine_overview", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• explain_claim≈ 248 tokens

  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 multiplicity and weight, which origin kinds were never explored, and the derived-claim / evidence chain with the Cypher each evidence item ran. Pure read: the score is recomputed in memory, nothing is written. FalkorDB features: GRAPH.RO_QUERY, variable-length DERIVED_FROM traversal.

  Paramètres, retour & exemple (2)

  Paramètres

  • case_id · string · requis
  • claim_id · string · requis

  Exemple d'appel

  {"name": "explain_claim", "arguments": {"case_id": "texte", "claim_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_rings≈ 244 tokens

  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 account. FalkorDB features: algo.labelPropagation.

  Paramètres, retour & exemple (5)

  Paramètres

  • graph · string · optionnel
  • limit · integer · optionnel
  • max_size · integer · optionnel
  • min_size · integer · optionnel
  • account_id · ? · optionnel

  Exemple d'appel

  {"name": "find_rings", "arguments": {"graph": "texte", "limit": 1, "max_size": 1, "min_size": 1, "account_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_case≈ 208 tokens

  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 claims that justify them, and SAR status. case_id like 'C-44c08392'. FalkorDB features: one graph per case, GRAPH.RO_QUERY.

  Paramètres, retour & exemple (2)

  Paramètres

  • case_id · string · requis
  • max_evidence · integer · optionnel

  Exemple d'appel

  {"name": "get_case", "arguments": {"case_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• graph_schema≈ 149 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • graph · string · optionnel

  Exemple d'appel

  {"name": "graph_schema", "arguments": {"graph": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_alerts≈ 180 tokens

  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_QUERY.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
  • status · ? · optionnel

  Exemple d'appel

  {"name": "list_alerts", "arguments": {"limit": 1, "status": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_cases≈ 139 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • limit · integer · optionnel

  Exemple d'appel

  {"name": "list_cases", "arguments": {"limit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_graphs≈ 128 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_graphs", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• run_readonly_cypher≈ 228 tokens

  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 rows, 10 s timeout. graph: 'consortium', 'bank_<id>', 'case_<id>' or 'typology_kb' (see graph_schema for labels and properties).

  Paramètres, retour & exemple (3)

  Paramètres

  • graph · string · optionnel
  • limit · integer · optionnel
  • cypher · string · requis

  Exemple d'appel

  {"name": "run_readonly_cypher", "arguments": {"cypher": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_customers≈ 170 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • k · integer · optionnel
  • name · string · requis
  • label · string · optionnel

  Exemple d'appel

  {"name": "search_customers", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• similar_accounts≈ 179 tokens

  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.queryNodes.

  Paramètres, retour & exemple (2)

  Paramètres

  • k · integer · optionnel
  • account_id · string · requis

  Exemple d'appel

  {"name": "similar_accounts", "arguments": {"account_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• top_hubs≈ 134 tokens

  Accounts where money pools: PageRank over TRANSFERS, highest first, with bank ids. graph: 'consortium', 'bank_<id>' or 'case_<id>'. FalkorDB features: algo.pageRank.

  Paramètres, retour & exemple (2)

  Paramètres

  • graph · string · optionnel
  • top_k · integer · optionnel

  Exemple d'appel

  {"name": "top_hubs", "arguments": {"graph": "texte", "top_k": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• trace_money_path≈ 242 tokens

  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. No path = no claim. FalkorDB features: algo.SPpaths.

  Paramètres, retour & exemple (5)

  Paramètres

  • dst · string · requis
  • src · string · requis
  • case_id · ? · optionnel
  • max_len · integer · optionnel
  • path_count · integer · optionnel

  Exemple d'appel

  {"name": "trace_money_path", "arguments": {"dst": "texte", "src": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• triage_alert≈ 200 tokens

  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 connected component size (islands smaller than the configured threshold clear instantly) and its motif score components. FalkorDB features: algo.wcc, GRAPH.RO_QUERY.

  Paramètres, retour & exemple (1)

  Paramètres

  • alert_id · string · requis

  Exemple d'appel

  {"name": "triage_alert", "arguments": {"alert_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• typology_guidance≈ 153 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • question · string · requis

  Exemple d'appel

  {"name": "typology_guidance", "arguments": {"question": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://bankweave-api.onrender.com/mcp