# BankWeave (remote · bankweave-api.onrender.com)

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

- Trust score: 7/100 (low)
- Change this week: −11
- Registry status: active
- Liveness: degraded
- Owner verified: no
- Last scored: 2026-11-05

> **Degraded**: one or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.

## Components

- remote · `bankweave-api.onrender.com`: 7/100 (this document), [markdown](https://verifymcp.io/servers/lsudoko-bankweave/bankweave-api.md), [page](https://verifymcp.io/servers/lsudoko-bankweave/bankweave-api)
- oci · `ghcr.io/lsudoko/bankweave-mcp`: 10/100, [markdown](https://verifymcp.io/servers/lsudoko-bankweave/ghcr-io-lsudoko-bankweave-mcp.md), [page](https://verifymcp.io/servers/lsudoko-bankweave/ghcr-io-lsudoko-bankweave-mcp)

## Channel facts

- Endpoint: `https://bankweave-api.onrender.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `3.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the BankWeave MCP server?

BankWeave is a hosted endpoint at https://bankweave-api.onrender.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http lsudoko-bankweave 'https://bankweave-api.onrender.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lsudoko-bankweave": {
      "type": "remote",
      "url": "https://bankweave-api.onrender.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lsudoko-bankweave --url 'https://bankweave-api.onrender.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lsudoko-bankweave:
    url: "https://bankweave-api.onrender.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "lsudoko-bankweave": {
      "Transport": "http",
      "Url": "https://bankweave-api.onrender.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add lsudoko-bankweave -t streamable-http -u 'https://bankweave-api.onrender.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "lsudoko-bankweave": {
      "type": "http",
      "url": "https://bankweave-api.onrender.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 7, −4)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-04 (score 11, −3)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-03 (score 14, −4)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-01 (score 18, 0)

- [security regression] Endpoint reachability: not serving MCP → unreachable
- [security regression] HSTS header: fail → unverified
- [security improvement] HTTPS: unverified → pass
- [security] Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it.

### 2026-10-26 (score 18, −53)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] HTTPS: pass → unverified
- [security regression] Stability: 0.17 → unverified
- [security regression] Transport: pass → fail
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-24 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (17)

### `engine_overview` (~79 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.

### `list_graphs` (~70 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.

### `graph_schema` (~90 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.

Input parameters:

- `graph` (string)

### `list_cases` (~72 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.

Input parameters:

- `limit` (integer)

### `get_case` (~128 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.

Input parameters:

- `case_id` (string, required)
- `max_evidence` (integer)

### `explain_claim` (~152 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.

Input parameters:

- `case_id` (string, required)
- `claim_id` (string, required)

### `account_network` (~134 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.

Input parameters:

- `account_id` (string, required)
- `depth` (integer)

### `trace_money_path` (~124 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.

Input parameters:

- `case_id`
- `dst` (string, required)
- `max_len` (integer)
- `path_count` (integer)
- `src` (string, required)

### `find_rings` (~117 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.

Input parameters:

- `account_id`
- `graph` (string)
- `limit` (integer)
- `max_size` (integer)
- `min_size` (integer)

### `top_hubs` (~70 tokens)

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

Input parameters:

- `graph` (string)
- `top_k` (integer)

### `connected_components` (~91 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.

Input parameters:

- `graph` (string)
- `limit` (integer)

### `similar_accounts` (~96 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.

Input parameters:

- `account_id` (string, required)
- `k` (integer)

### `search_customers` (~85 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.

Input parameters:

- `k` (integer)
- `label` (string)
- `name` (string, required)

### `list_alerts` (~103 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.

Input parameters:

- `limit` (integer)
- `status`

### `triage_alert` (~122 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.

Input parameters:

- `alert_id` (string, required)

### `typology_guidance` (~85 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.

Input parameters:

- `question` (string, required)

### `run_readonly_cypher` (~153 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).

Input parameters:

- `cypher` (string, required)
- `graph` (string)
- `limit` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lsudoko-bankweave/bankweave-api#diagnostics

## Score history

- 2026-11-05: 7
- 2026-11-04: 11
- 2026-11-03: 14
- 2026-11-02: 18
- 2026-11-01: 18
- 2026-10-31: 18
- 2026-10-30: 18
- 2026-10-29: 18
- 2026-10-28: 18
- 2026-10-27: 18
- 2026-10-26: 18
- 2026-10-25: 71
- 2026-10-24: 71
- 2026-10-23: 70
- 2026-10-22: 70
- 2026-10-21: 69
- 2026-10-20: 69
- 2026-10-19: 23

## Common questions

### What is the BankWeave MCP server?

BankWeave is an MCP server listed in the public MCP registry as io.github.LSUDOKO/bankweave. Read-only FalkorDB tools for cross-bank AML investigations: rings, money paths, echo-proof claims. This page covers its hosted endpoint (https://bankweave-api.onrender.com/mcp).

### Is the BankWeave MCP server safe to use?

BankWeave scores 7 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the BankWeave MCP server expose?

BankWeave exposes 17 tools: engine_overview, list_graphs, graph_schema, list_cases, get_case, and 12 more. Their descriptions and schemas cost roughly 1,771 tokens of context every time the server is loaded.

### Does the BankWeave MCP server require authentication?

Its publisher declares no required credentials for BankWeave. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the BankWeave MCP server still maintained?

BankWeave is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 31 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the BankWeave MCP server?

VerifyMCP ran 4 checks on BankWeave, covering TLS certificate, HTTPS, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about BankWeave: Authorization, HSTS header, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://bankweave-api.onrender.com/mcp
- Repository: https://github.com/LSUDOKO/BankWeave
- Website: https://bankweave.vercel.app/
- Changelog RSS feed: https://verifymcp.io/servers/lsudoko-bankweave/bankweave-api.xml
- Changelog JSON feed: https://verifymcp.io/servers/lsudoko-bankweave/bankweave-api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/lsudoko-bankweave/bankweave-api.json
- HTML version of this page: https://verifymcp.io/servers/lsudoko-bankweave/bankweave-api