Skip to content

BankWeave MCP server

io.github.LSUDOKO/bankweaveLSUDOKOstreamable-httpv3.0.1Scanned

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

17 tools: 10 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 10 write, 7 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

10 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the BankWeave MCP server can do

The BankWeave MCP server is published by the GitHub account LSUDOKO. It has 17 tools. It can create or change data (10 tools: engine_overview, graph_schema, account_network, trace_money_path and 6 more), but cannot delete data. 7 tools only read.

1 tool reads private data (list_graphs).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Last scanned Oct 21, 2026, version 3.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

17 tools

Changes things 10Claude Code: ask
  • account_networkAn 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, a…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • connected_componentsWeakly 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 instan…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • engine_overviewHealth 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 / clear…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • graph_schemaSchema of one graph: node labels, relationship types, property keys and indexes with their kind (RANGE, FULLTEXT, VECTOR).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • run_readonly_cypherLast resort: run your own read-only Cypher on one graph.1 finding

    Why it is in this group

    • The name "run_readonly_cypher" says "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "run_readonly_cypher" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_readonly_cypher" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • similar_accountsAccounts 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • top_hubsAccounts where money pools: PageRank over TRANSFERS, highest first, with bank ids.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Accounts where money pools: PageRank over TRANSFERS, highest first, with bank ids. graph: 'consortium', 'bank_<id>' or 'case_<id>'. FalkorDB features: algo.pageRank.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • trace_money_pathShortest 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • triage_alertWhy an alert was cleared or escalated into a case.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • typology_guidanceLaundering typology guidance (e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
Only reads 7Show 7 read-only tools
  • explain_claimWhy a claim has the confidence it has (GraphEcho echo-proof scoring).No findings

    Why it is in this group

    • The name "explain_claim" says "explain": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • find_ringsCandidate laundering rings: communities of accounts that trade mostly among themselves, found by label propagation on the transfer graph.No findings

    Why it is in this group

    • The name "find_rings" says "find": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_caseEverything 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 id…No findings

    Why it is in this group

    • The name "get_case" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • list_alertsThe alert queue with counts by status.No findings

    Why it is in this group

    • The name "list_alerts" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • list_casesList investigation cases (newest first) with status, title, seed account, number of alerts/accounts, the banks involved and whether its case graph is loaded.No findings

    Why it is in this group

    • The name "list_cases" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • list_graphsList 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 kno…Reads private dataNo findings

    Why it is in this group

    • The name "list_graphs" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "db": it reads databases.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • search_customersFuzzy name search over customers (Person) or businesses (Company) across all banks, with the accounts and banks each one owns.No findings

    Why it is in this group

    • The name "search_customers" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 18:58 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
503
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 503.

Posture changes

  1. Nov 20, 2026
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 503
  2. Nov 6, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 503 to none
  3. Oct 29, 2026
    • HTTP status of an anonymous initialize: 200 to 503
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 10 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "run_readonly_cypher" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_readonly_cypher" says "run": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 503.View diff
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 503
  2. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 503 -> none.View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 503 to none
  3. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 503; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 10 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 503
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 10 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 3.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http bankweave https://bankweave-api.onrender.com/mcp
claude mcp add --transport http bankweave https://bankweave-api.onrender.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__bankweave__list_graphs",
      "mcp__bankweave__list_cases",
      "mcp__bankweave__get_case",
      "mcp__bankweave__explain_claim",
      "mcp__bankweave__find_rings",
      "mcp__bankweave__search_customers",
      "mcp__bankweave__list_alerts"
    ],
    "ask": [
      "mcp__bankweave__engine_overview",
      "mcp__bankweave__graph_schema",
      "mcp__bankweave__account_network",
      "mcp__bankweave__trace_money_path",
      "mcp__bankweave__top_hubs",
      "mcp__bankweave__connected_components",
      "mcp__bankweave__similar_accounts",
      "mcp__bankweave__triage_alert",
      "mcp__bankweave__typology_guidance",
      "mcp__bankweave__run_readonly_cypher"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bankweave. Review it before you use it.

Capability tags behind 1 rule
  • mcp__bankweave__list_graphs private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.LSUDOKO/bankweave/verify?hash=7d443f8460812f6481c63ced4144c048d97a637ebac974af487b03ecb13afb45" | jq -e '.changed == false'

Pinned hash 7d443f846081, from Oct 21, 2026, 19:03 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.LSUDOKO/bankweave/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.LSUDOKO/bankweave
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.LSUDOKO/bankweave.svg)](https://radar.anlyon.com/servers/io.github.LSUDOKO/bankweave)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:17 UTC.

BankWeave MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the BankWeave MCP server safe?

No scan can promise that. What its definitions show: 17 tools, 10 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the BankWeave MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the BankWeave MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the BankWeave MCP server have?

17 tools: 10 write, 7 read. engine_overview, graph_schema, account_network, trace_money_path, top_hubs, connected_components, similar_accounts, triage_alert and 9 more.

Does the BankWeave MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the BankWeave MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the BankWeave MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.