Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Read-only FalkorDB tools for cross-bank AML investigations: rings, money paths, echo-proof claims.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://bankweave-api.onrender.com/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"bankweave": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/lsudoko/bankweave-mcp:3.0.0"
]
}
}
}Run this in your terminal
claude mcp add --transport http bankweave https://bankweave-api.onrender.com/mcpclaude mcp add bankweave -- docker run -i --rm ghcr.io/lsudoko/bankweave-mcp:3.0.0Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"bankweave": {
"url": "https://bankweave-api.onrender.com/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"bankweave": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/lsudoko/bankweave-mcp:3.0.0"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"bankweave": {
"type": "http",
"url": "https://bankweave-api.onrender.com/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"bankweave": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/lsudoko/bankweave-mcp:3.0.0"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://bankweave-api.onrender.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
The server did not answer when we last checked, so we could not read its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account LSUDOKO, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Did not respond within 6 seconds when we checked
Did not respond within 6 seconds when we checked
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 2 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (3.0.1) reached the registry 20 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Happo
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Review Happo's visual and accessibility diffs: inspect comparisons, accept or reject, report flakes.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Many banks, one ring, every claim proven.
BankWeave is a team of AI agents that investigates money-laundering alerts across several banks, with FalkorDB as its shared brain. It clears innocent alerts fast, exposes laundering rings that no single bank can see, and backs every conclusion with a graph path you can click through. It also knows how many *independent* reasons it has for each belief, notices when one of them dies, and refuses to file a report it can't prove.
io.github.LSUDOKO/bankweave (v3.0.0, streamable HTTP)claude mcp add --transport http bankweave https://bankweave-api.onrender.com/mcp, or as a stdio package: claude mcp add bankweave -- docker run -i --rm ghcr.io/lsudoko/bankweave-mcp (17 read-only FalkorDB tools, each returning the Cypher it ran; docs/MCP.md)video/build.py --longdocs/BLOG.mdRunning now on real data. The production instance on FalkorDB Cloud holds IBM's labelled AML transactions for 6 banks: 3,024 accounts, 24,990 transfers, 36 graphs (6 bank graphs, the consortium graph with 10,178 nodes and 37,448 edges, 27 case graphs, agent memory and the typology knowledge base). The agents have triaged 1,208 alerts: 1,113 cleared with a stated reason and 95 escalated into cases, each case with claims, evidence, the Cypher behind every piece of evidence, a provenance-gated report and a signed Merkle seal.
BankWeave is an independent project built for FalkorDB Graph Hacks. It is not a FalkorDB product and is unrelated to FalkorDB's QueryWeaver or Weights & Biases Weave.
case_ graph, where claims are linked to evidence and the query that produced it.| Area | What you can do | Where |
|---|---|---|
| Console | A sidebar listing all fourteen pages with live counts, Ctrl K search over pages and cases, and one card system across every page: stat cards from live queries, status chips, rounded charts | every page |
| Dashboard | Open cases, alerts decided, independent claims, actions awaiting a human; claim support for the latest cases; the next approval; the agent team; an alert-triage gauge; FalkorDB Cloud latency, graphs and memory | /command |
| Graph explorer | A FalkorDB-browser-style page: pick a graph, write Cypher (GRAPH.RO_QUERY, writes rejected by the engine), see an Obsidian-style force graph with labels, hover neighbourhoods and a property panel. Twelve presets, each a FalkorDB feature on our data: cross-bank ring, algo.pageRank, algo.labelPropagation, algo.wcc, algo.SPpaths, Double Metaphone full-text, HNSW vector KNN, shared identity, the agents' alert-to-claim chain, a SAR's provenance, the typology KB, learned procedures | /explorer |
| 3D explainer | Scroll through eight scenes on a three.js stage: six bank slices and per-graph ACL, hashed ids stitching the consortium, algo.wcc clearing an alert, the ring one bank sees 37.5% of, PageRank hub and algo.SPpaths, six paths collapsing to four origins, a KYC cascade, a Merkle root signed by a hardware key. Every number comes from the API; each scene shows the Cypher it ran | /explainer |
| Hosted MCP | claude mcp add --transport http bankweave https://bankweave-api.onrender.com/mcp: 17 read-only tools (cases, echo-proof claims, money paths, rings, hubs, components, vector and phonetic search, triage, typologies, guarded Cypher), 3 prompts, 2 resources | /mcp, docs/MCP.md |
| Landing | Centred hero over glossy blue bubbles with word-by-word type, the live console rising out of it, a "what's new" bento, the evaluation shown as highlighted screenshots of the live page, the real-tool recordings and the FalkorDB Browser proof | / |
| Real tools, recorded | The ESP32 sketch running in Wokwi posts a real card tap to the live API, and EMVLab decodes the field 55 it printed | Hardware Lab, below |
| Landing | Dashboard |
|---|---|
| Graph explorer: cross-bank ring on the consortium graph | 3D explainer: the ring as one bank sees it |
|---|---|
Graph explorer: algo.pageRank hubs (hover focuses one community) | 3D explainer: six bank slices, each sees only its own graph |
|---|---|
| Alert queue | Case workspace |
|---|---|
| Approvals | Hardware Lab |
|---|---|
The same data the agents use, opened in FalkorDB's own browser (browser.falkordb.com, connected to our FalkorDB Cloud instance: FalkorDB v4.22, 36 graphs, about 81 MB). Every query below is read-only and was typed into the browser; the timings are the engine's own RT readout. The connection bar with the instance hostname is cropped out.
| Query | What it proves |
|---|---|
| Cross-bank ring: the case spanning the most banks, its accounts, banks and transfers (12 nodes, 166 edges, 1.85 ms) | one Cypher query sees the whole ring that no single bank graph contains |
CALL algo.pageRank('Account','TRANSFERS') top 12 (3.55 ms) | the hub detection the Investigator calls is native GraphBLAS, not Python |
(:Account)-[:CARD_TXN]->(:Terminal) (5 nodes, 29 edges, 0.41 ms) | the POS/ATM taps, including the one sent from the Wokwi ESP32, are real edges in the consortium graph; the Terminal node carries POS-MUM-…, Mumbai, GPS 19.076, 72.8777 |
(:SAR)-[:CONTAINS]->(:Sentence)-[:CITES]->(:Claim)-[:SUPPORTED_BY]->(:Evidence) in case_C-70431130 (0.61 ms) | every report sentence cites a claim, and every claim rests on evidence: the provenance gate is a graph pattern |
db.idx.vector.queryNodes('Account','behavior_vec',10, …) (0.36 ms) | HNSW vector search finds behaviour twins at five different banks |
Accounts at different banks sharing a Device or IP (291 nodes, 220 edges, 2.79 ms) | the identity links the consortium uses to join bank slices |
| Cross-bank ring | algo.pageRank |
|---|---|
| Card taps into terminals (the Wokwi tap included) | The Mumbai POS node and its properties |
|---|---|
| SAR → sentence → claim → evidence | HNSW vector KNN |
|---|---|
| Shared devices and IPs across banks | FalkorDB Cloud console: the instance (Free tier, ap-south-1, v4.22.0, healthy) |
|---|---|
Hosted MCP, called live (no install, plain HTTP):
$ curl -s -X POST https://bankweave-api.onrender.com/mcp -H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' 17 tools: engine_overview, list_graphs, graph_schema, list_cases, get_case, explain_claim, account_network, trace_money_path, find_rings, top_hubs, connected_components, similar_accounts, search_customers, list_alerts, triage_alert, typology_guidance, run_readonly_cypher
$ ... "method":"tools/call","params":{"name":"top_hubs","arguments":{}} {"graph": "consortium", "result": [{"account": "e8ccd1faa8d3a4ba", "bank": "001", "score": 0.0027...}, ...
The top account matches row 1 of the PageRank query in the FalkorDB Browser above.
| Area | What you can do | Where |
|---|
| Command Center | Live alerts, open cases, independently supported claims, evidence awaiting review, FalkorDB healt
Only the beginning is shown; read the rest in the repo