BankWeave MCP Server

by lsudoko Your server? Claim it

not responding

BankWeave is listed as active in the registry but did not answer our last check. It exposes 17 tools. Last commit 18 Oct 2026.

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

Uptime history 21 days of history · worst day 0%

21 days agonow

0.0%

Uptime 24h

0 of 91 checks

Tools

read from the server

20000 ms

Response time

average over 24h

Stars

last commit 18 Oct 2026

What the code does

We read the source, 7 d ago · tools taken from the live server · rules 995398eba69f

Evidence

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

Claims read-only, but the code runs commands video/build.py:53

    out = subprocess.check_output(["ffprobe", "-v", "error", "-show_entries", "format=duration", "-of", "csv=p=0", str(p)])

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command video/build.py:53

    out = subprocess.check_output(["ffprobe", "-v", "error", "-show_entries", "format=duration", "-of", "csv=p=0", str(p)])

Page executes code built at runtime video/films/film3/index.html:218, video/films/film4/index.html:141, video/work2/page.html:5

    r.children[2].innerHTML = typed(v, t, st, 30) + caret(t, t > st && t < st + v.length / 30 + .1);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

We found things in this code

Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch BankWeave and you get told the day something new turns up.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

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

~/.codex/config.toml

[mcp_servers.bankweave]
url = "https://bankweave-api.onrender.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "bankweave": {
      "url": "https://bankweave-api.onrender.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "bankweave": {
      "type": "http",
      "url": "https://bankweave-api.onrender.com/mcp"
    }
  }
}

Available tools 17

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

account

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

alerts

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

case

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

cases

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.

connected

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.

customers

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.

engine

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.

explain

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

graph

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.

graphs

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.

readonly

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

rings

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

similar

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

top

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.

trace

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

triage

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

typology

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.

Endpoints

URL	Transport	State	Latency	Checked
https://bankweave-api.onrender.com/mcp	streamable-http	answering	20000 ms	13 min ago

Alternatives to BankWeave

same job, measured the same way

Mana Public

by mana

Read-only MCP tools for Mana public creations, tags, creator profiles, and share pages.

6 tools answering

x207

by x207-labs

Read-only tools for x207 circles on NEAR: members, epochs, clearing simulation, listings.

1 114 installs/wk 6 tools answering

Crossplane

by ravibagri5

Read-only access to a Crossplane control plane: resources, claims, packages, compositions.

local only

Synci

by synci

Read-only access to your bank, investment, and crypto accounts: balances, transactions, holdings.

answering

BigQuery Data Platform

by debilla

Read-only BigQuery tools for plain-language data questions, with a cost gate on every query

194 installs/wk local only

poolproof — checks before you commit money

by poolproof

Who launched it, what exit really costs, is the pool what it claims. Facts only, no advice.

9 tools answering

VMware Log Insight

by zw008

Read-only VMware Aria Operations for Logs (Log Insight): search + aggregation. 7 MCP tools.

420 installs/wk local only

VMware Log Insight

by vmware-skills

Read-only VMware Aria Operations for Logs (Log Insight): search + aggregation. 7 MCP tools.

local only

BankWeave — questions

Answers built from our own checks of this server.

What can BankWeave do?

It exposes 17 tools, read directly from the server on our last check. Among them: account_network, connected_components, engine_overview, explain_claim, find_rings, get_case and 11 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is BankWeave working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 20000 ms. The bar chart above shows every period we have measured.

The registry lists BankWeave as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect BankWeave?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does BankWeave need an API key?

No. BankWeave completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 17 of them are readable on this page. This is what we observed, not what the docs claim.

Is BankWeave open source?

The code is open source: it is published under the MIT licence, written in TypeScript, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at bankweave-api.onrender.com, which runs on its operator's own terms.