Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Auditable multi-agent topology generator from Drosophila MaleCNS connectome motifs.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:
https://lm203688.github.io/flybrain-connectome/Führe das in deinem Terminal aus
claude mcp add --transport http flybrain-connectome https://lm203688.github.io/flybrain-connectome/In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"flybrain-connectome": {
"url": "https://lm203688.github.io/flybrain-connectome/"
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"flybrain-connectome": {
"type": "http",
"url": "https://lm203688.github.io/flybrain-connectome/"
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
ChatGPT verbindet sich nur mit Servern im Internet:
https://lm203688.github.io/flybrain-connectome/Menünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Der Server hat bei unserer letzten Prüfung nicht geantwortet, deshalb konnten wir seine Tools nicht lesen.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 8. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto lm203688 bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Hat bei unserer Prüfung nicht innerhalb von 6 Sekunden geantwortet
Hat bei unserer Prüfung nicht innerhalb von 6 Sekunden geantwortet
Noch nicht geprüft; wir lesen die Tool-Liste, wenn wir den Endpunkt prüfen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 2 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft in der Cloud des Entwicklers. Du verbindest dich übers Internet, ohne etwas zu installieren, aber was du sendest, läuft über die Server des Entwicklers.
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (3.0.2) kam vor 14 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, MyGroceryPal
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
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.
UK supermarket prices: compare products and baskets across 13 stores, see price history, set alerts.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
v3.01.3 · 2026-10-26 · 116 functional units · 270 module profiles · 64 gates · EPE 全栈 + AIBOM 供应链披露 + 收据完整性门禁 + Gate 60/61/62/63/64/65/66 + fail-loud 纪律 + 版本单一真源 + Xu 2026 树突计算前沿对照 + Xu 2026 双层认知计算参考实现(`tools/dendritic_rule_engine.py` + `examples/07_dendritic_rule_cache_demo.ipynb`)+ E4 区室边界 + S1 外部验证 + S2 lesion cascade + S3 统计强化 + 纪律有效性量化(catch-rate 100%,W1–W7 全部关闭)+ Gate 63 research_claims 顶层统计完整性 + 作者署名规范化(P-3 / P-4 → Li Xing + ORCID)+ bioRxiv 投稿准备包 + flybrain demo 一条命令 + 5 分钟上手 + flybrain audit CLI + JOSS 投稿包 + MCP 生态提交包 + 9 篇论文 DOI 补齐 + P1-3 HTTP/MCP 契约统一(Gate 66 · HTTP DISPATCH 从 12→47 全覆盖 MCP)+ P1-1 LangGraph runnable 后端(`--runnable` 生成含 MockLLM + MemorySaver checkpointing + OTel trace 的可执行 Python 脚本)
### The 89% problem
Deloitte's 2026 agent-pilot survey found **89% of enterprise agent pilots
never reach production**. Teradata: 78% have pilots, only 14% scaled. The
failure pattern repeats across industries in three words:
"跑不稳、管不住、查不清" — unstable, ungovernable, unauditable.
flybrain-connectomeaddresses the third word. Every agent edge in a
generated topology traces back to a real neuron or synapse class in the
*Drosophila* male brain connectome, serialized as W3C PROV-JSON — the
same format EU AI Act auditors expect. Your agent swarm isn't a black box;
it's a verifiable structure with biological provenance.
[5-minute quickstart](docs/QUICKSTART_5MIN.md) — from zero to an
interactive D3 topology graph in five minutes, no data download.
Auditable Agent Topology — 可审计的 Agent 拓扑生成与溯源, grounded in
the real *Drosophila* male-brain connectome (MaleCNS v1.0 — 166,700
neurons / 124,177,617 synapses, CC-BY).
flybrain-connectome turns a real, published brain wiring diagram into task-tailored multi-agent topologies you can instantiate as agent swarms — and it can prove, for every edge, *which real neuron / synapse class it came from*. The motif provenance is serialized as W3C PROV-JSON, the same standard EU AI Act auditors expect.
*5-module × 8-agent topology (predictive_coding_v2 blueprint) — the same graph you get from flybrain demo. Try it live →*
It is a developer toolkit and research artifact, not a trained model and not a simulation of a fly. Read the honest boundaries before you quote it.
Repo status: PUBLIC since 2026-10-18. History was audited and cleaned
before publicization (see CHANGELOG v1.3.0 for the original
Tier-2 IP leak and docs/D3_REPOSITORY_PUBLICITY_DECISION_2026-10-18.md
for the 16-step publicization runbook that was executed). The Tier-1 code is
MIT-licensed and reachable at https://github.com/lm203688/flybrain-connectome.
Tier-2 raw data (MaleCNS 5.63 GB, C. elegans Witvliet 2020, Drosophila larva
edges.csv, Petkova 2025 zebrafish) is fetched via the documented data pipeline
— see §"Requirements" and the S1 external-validation script.
| ✅ This project | ❌ Not this project |
|---|---|
| A connectome query service (47 tools over HTTP + MCP) | A spiking-neuron simulator |
| A motif-extraction pipeline (real fly → derived motif doc) | A repository of the raw 5.63 GB data |
| A synthetic topology generator (bio-motifs → agent graphs) | A trained / fine-tuned model with weights |
| W3C PROV provenance on every generated artifact | A claim that the "virtual organism" is alive |
The killer offline feature: `generate` needs no data — it composes topologies from a 7 KB derived motif snapshot. The connectome data is only needed if you want to *query* the real brain.
The 116 functional units are split cleanly by how their evidence comes together. This is the number to remember when reading any downstream claim:
| Bucket | Count | Meaning |
|---|---|---|
| Anchored to real *Drosophila* male-brain cells | 37 / 116 (31.9 %) | embodiment.real_cells_anchored > 0 — each edge traces to actual MaleCNS v1.0 neurons |
| Cross-species declarations, unanchored | 79 / 116 (68.1 %) | provenance.unanchored_reason = identity_not_in_drosophila or taxon_no_malecns_data — the circuit exists in the literature for another species, not in the MaleCNS connectome |
The 68.1 % bucket is not a defect and not a hidden error. It is a comparative-neuroscience scaffold: bird song, mammalian cortical layers, fish Mauthner, cephalopod vertical lobe, Aplysia and leech CPGs, insect mushroom-body — all are wired into the library with named references and can be composed like the anchored ones, but they are not measured in a real connectome the way the 37 anchored units are. Reading the library correctly means reading those two numbers together, not the 116 by itself.
Rather than a single "this is a X" pitch, the useful things this project does break down into three tiers. Which one you actually need depends on what you are building.
Tier 1 — usable today, offline, no data download. Neuron-circuit search across 3 species × 4 axes (system / function / species / provenance); compose a virtual-organism topology from any subset of units; run the four canonical DEMOs (mammal, insect, electrosensory, swim) end-to-end. This is the *developer tool* the project actually is. flybrain search, flybrain compose, flybrain generate cover it.
Tier 2 — for people designing AI-agent scaffolds. The composed topologies trace back to real circuitry via W3C PROV-JSON, which means a downstream agent framework (LangGraph / CrewAI / AutoGen / SwarmLabs) can pick up a starting topology and audit where each wiring decision came from. This is not a general agent infra — it is a biology-prior layer you plug into one.
Tier 3 — what this project explicitly does not do. It does not beat biology at anything (Phase 3 measured negative and is not claimed). It does not replace any EM reconstruction pipeline. It does not ship a trained model or a spiking simulator. If someone reads a v1.x changelog entry that promises any of those, the honest answer is "that was aspirational; the withdrawal is documented in docs/PROJECT_REALITY_ASSESSMENT.md".
We ran the experiments. Two of the "obvious" advantages turned out to be false under controlled testing, and we say so.
| # | Moat | Evidence | Status |
|---|---|---|---|
| 1 | Traceability — every generated edge traces to a real neuron/synapse class, serialized as W3C PROV-JSON | _verify.py 70/70; prov_json top-level field (schema v1.2.1) | ✅ real |
| 2 | Structural parsimony — genetic search finds far leaner graphs than the biological prior | GA converges to 9–11 edges vs 57 locked → −84% wire cost | ✅ real |
| 3 | Structural stability — module-level fault isolation | 25 / 27 sampled topologies show modular H1 isolation (92.6%); spectral radius ρ held at 0.00–0.30% | ✅ real |
| 4 | Local decision-making — modules read out their own answers | multi-readout experiment 5 / 28 H1 (17.9%), only on simple/delay≤2 tasks | ⚠️ partial |
| Dimension | Result | Why we dropped the claim |
|---|---|---|
| Raw compute advantage | 0 / 7 topologies beat random structure | Matched-control ESN calibration; motif advantage 0/7, differences within noise |
| Energy advantage | 0 / 24 runs beat random | SNN energy proxy; median ratio 1.006 (±5%), no systematic gain |
Honesty is a feature. The reproducible experiment scripts live in integrations/swarmlabs/diagnostics/ and the reports in the repo root (SNN_ENERGY_REPORT.md, MULTI_READOUT_REPORT.md, FAULT_ISOLATION_REPORT.md).
The toolkit needs one runtime dependency (numpy, because the connectome engine imports it at module level) plus optional extras for provenance and columnar IO. No other third-party code is required. Pick either setup:
Repo status: PUBLIC since 2026-10-18. No authentication required —
the clone commands below work directly. History was audited and cleaned
before publicization (see CHANGELOG v1.3.0 for the original
Tier-2 IP leak and docs/D3_REPOSITORY_PUBLICITY_DECISION_2026-10-18.md
for the 16-step publicization runbook).
git clone https://github.com/lm203688/flybrain-connectome.git
cd flybrain-connectome python flybrain_cli.py --help
flybrain on your PATH)git clone https://github.com/lm203688/flybrain-connectome.git
cd flybrain-connectome pip install -e . flybrain info
pip install -e . is *editable*: the flybrain entry point maps back to the checkout, which is precisely what lets it find the toolkit. A plain pip install . ships only the launcher, so point it at a checkout explicitly:
pip install .
export FLYBRAIN_HOME=/path/to/flybrain-connectome flybrain info
This path is verified in CI, not just documented. The
packagejob in
.github/workflows/ci.ymlrunspip install ".[prov]", invokes the console
script, resolves the toolkit via
FLYBRAIN_HOME, generates an organism, and
asserts the artifact's invariants — so the install instructions cannot
silently rot.
Structural provenance (motif_provenance, with the snapshot sha256) is always recorded. The *standardized* W3C PROV-JSON bundle (prov_json) is serialized by the optional dataprov package:
pip install dataprov # or: pip install "flybrain-connectome[prov]" (once on PyPI)
Without it the toolkit still runs: prov_json becomes null and get_provenance_bundle answers with prov_available: false plus the reason, rather than crashing. Both arms are asserted by scripts/check_degraded_mode.py — absent must degrade, present must actually produce the bundle.
flybrain info
reports the resolved toolkit root, the motif snapshot, the data dir, API-key status, and how many tools are exposed. Run it first whenever something looks wrong — it turns "ImportError" into a named, fixable problem.
MaleCNS v1.0 is CC-BY, ~5.63 GB, and deliberately not in this repo:
export FLYBRAIN_DATA_DIR=/path/to/your/male_cns
generate and the bundled motif snapshot need no data at all.
Every
flybrainbelow also works aspython flybrain_cli.py
(setup A), so you can try the project without installing anything.
###
Nur der Anfang wird gezeigt; den Rest findest du im Repo