Darwin RAG
PYPI · DARWIN-RAG
Local-first RAG engine with MCP server for AI agent integration.
Available components
Last scanned (17 hours ago)
Scores higher than 0% of PyPI servers
Category AI and Machine Learning
Recent critical change
CVE-2026-49468 affects this package (4 Aug 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security74
- No malware found by supply-chain analysis.Pass
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- Dependency health was assessed across the 177 of 180 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 71 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →
Checks we ran (9)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
Checks we could not complete (5)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
- Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 0
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 0
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 0
- Malware scan: unverified → pass ▲ security
- 25 Oct 26 0
- Malware scan: pass → unverified ▼ security
- 24 Oct 26 0
- Malware scan: unverified → pass ▲ security
- 22 Oct 26 −28
- Known CVEs: unverified → fail ▼ critical
- Score status: scored → failed ▼ critical
- Malware scan: pass → unverified ▼ security
- Dependency health: unverified → partial ▲ functional
- 21 Oct 26 +28
- Known CVEs: fail → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Dependency health: partial → unverified ▼ functional
- Score status: failed → scored ▲ functional
- 19 Oct 26 0
- Malware scan: pass → unverified ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Analysed pypi/darwin-rag@0.2.18
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 46 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-2fqr-mr3j-6wp8 | CVE-2026-54279 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-2g87-pp6c-29x5 | high | yes | ||
| GHSA-494j-54xm-rwp3 | CVE-2026-111063 | medium | yes | |
| GHSA-4fvr-rgm6-gqmc | CVE-2026-54273 | medium | yes | |
| GHSA-4m7w-qmgq-4wj5 | CVE-2026-54275 | low | yes | |
| GHSA-5wr8-gcqf-gqf3 | CVE-2026-111064 | high | yes | |
| GHSA-63hw-fmq6-xxg2 | CVE-2026-54277 | medium | yes | |
| GHSA-6cjc-53gc-5rqm | CVE-2026-111065 | medium | yes | |
| GHSA-9x8q-7h8h-wcw9 | CVE-2026-54280 | low | yes | |
| GHSA-9xw5-w5jj-pvcg | CVE-2026-111066 | high | yes | |
| GHSA-cq5v-8q36-5273 | CVE-2026-69244 | high | yes | |
| GHSA-f9xw-jh8m-3mwq | CVE-2026-111748 | medium | yes | |
| GHSA-g3cq-j2xw-wf74 | CVE-2026-54278 | medium | yes | |
| GHSA-gx76-c99x-2c96 | CVE-2026-111749 | low | yes | |
| GHSA-hg6j-4rv6-33pg | CVE-2026-47265 | medium | yes | |
| GHSA-hpj7-wq8m-9hgp | CVE-2026-54276 | medium | yes | |
| GHSA-jg22-mg44-37j8 | CVE-2026-34993 | medium | CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:H/A:L | yes |
| GHSA-m6qw-4cw2-hm4m | CVE-2026-50269 | low | yes | |
| GHSA-mfx4-hv73-q22v | CVE-2026-69243 | medium | yes | |
| GHSA-mq44-7p77-q5h7 | CVE-2026-59881 | medium | yes | |
| GHSA-pqxq-w44r-73xw | CVE-2026-111750 | medium | yes | |
| GHSA-xcgm-r5h9-7989 | CVE-2026-54274 | medium | yes | |
| PYSEC-2026-2104 | CVE-2026-34993 | high | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H | yes |
| PYSEC-2026-2105 | CVE-2026-47265 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| PYSEC-2026-2106 | CVE-2026-50269 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| PYSEC-2026-2107 | CVE-2026-54273 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| PYSEC-2026-2108 | CVE-2026-54274 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| PYSEC-2026-2109 | CVE-2026-54276 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N | yes |
| PYSEC-2026-2110 | CVE-2026-54277 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| PYSEC-2026-2111 | CVE-2026-54278 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| PYSEC-2026-2112 | CVE-2026-54279 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| PYSEC-2026-2113 | CVE-2026-54280 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| PYSEC-2026-237 | CVE-2026-54275 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| PYSEC-2026-3545 | CVE-2026-69244 | none | yes | |
| PYSEC-2026-3546 | CVE-2026-69243 | none | yes | |
| PYSEC-2026-3547 | CVE-2026-59881 | none | yes | |
| GHSA-3cv6-jpf6-8222 | CVE-2026-84377 | medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-4jcj-7x88-m979 | CVE-2026-12773 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L | yes |
| GHSA-4xpc-pv4p-pm3w | CVE-2026-49468 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-7488-6r32-c95q | CVE-2026-59822 | high | yes | |
| GHSA-g5ff-637f-6q2m | high | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N | yes | |
| GHSA-hhww-mrg2-969h | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N | yes | |
| PYSEC-2026-3479 | CVE-2026-59822 | none | yes | |
| PYSEC-2026-388 | CVE-2026-49468 | none | yes | |
| PYSEC-2026-4066 | CVE-2026-84377 | medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N | yes |
| PYSEC-2026-4067 | CVE-2026-12773 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 177 packages
| Packages resolved | 177 |
|---|---|
| Stale | 23 |
| No linked repository | 1 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the Darwin RAG MCP server?
Darwin RAG runs locally as a PyPI package, launched with uvx darwin-rag mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · darwin-rag
claude mcp add brightdotdev-darwin-rag -- uvx darwin-rag mcp
What is the Darwin RAG MCP server?
Darwin RAG is an MCP server listed in the public MCP registry as io.github.Brightdotdev/darwin-rag. Local-first RAG engine with MCP server for AI agent integration. This page covers its PyPI package (darwin-rag).
Is the Darwin RAG MCP server still maintained?
Darwin RAG is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Darwin RAG MCP server under?
Darwin RAG declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.