Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.VBlackJack/cortex

PYPI · CORTEX-LOCAL-RAG

Local multi-client RAG server over the Model Context Protocol.

Available components

−38 this week 0 Trust /100

Last scanned (22 hours ago)

Scores higher than 0% of PyPI servers

Category Search and Retrieval

Recent critical change

CVE-2026-112398 affects this package (24 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 123 of 125 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to VBlackJack/Cortex). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 13 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: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need 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 the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Changelog

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 −38
    • Known CVEs: unverified → fail ▼ critical
    • Score status: scored → failed ▼ critical
    • Dependency health: unverified → partial ▲ functional
  • 28 Oct 26 +38
    • Known CVEs: fail → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Dependency health: partial → unverified ▼ functional
    • Score status: failed → scored ▲ functional
  • 27 Oct 26 0
    • Malware scan: pass → unverified ▼ security
  • 26 Oct 26 −38
    • Known CVEs: unverified → fail ▼ critical
    • Score status: scored → failed ▼ critical
    • Dependency health: unverified → partial ▲ functional
  • 25 Oct 26 +38
    • Known CVEs: fail → unverified ▼ security
    • Dependency health: partial → unverified ▼ functional
    • Score status: failed → scored ▲ functional
  • 24 Oct 26 0
    • CVE-2026-112398 affects this package: none ▼ critical
Diagnostics

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 4 Nov 2026 · Analysed pypi/cortex-local-rag@2026.1021.3

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo VBlackJack/Cortex
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/VBlackJack/Cortex/.github/workflows/release.yml@refs/tags/v2026.1021.03
Rekor log index 3357200376
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:f8a1aa3fa7a1785c24950b1b3388012c858e7155176fcee924e7c176be9d4ecf

Background: How many MCP packages publish verified provenance →

Vulnerabilities 76 findings
ID CVE Severity Vector Fix available
GHSA-2wm9-hf6c-p5cr CVE-2026-45830 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H no
GHSA-36p7-vc44-83pf CVE-2026-45833 critical no
GHSA-f4j7-r4q5-qw2c CVE-2026-45829 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H no
GHSA-xph7-9rjv-w5fr CVE-2026-45831 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H no
PYSEC-2026-311 CVE-2026-45829 none no
PYSEC-2026-3813 CVE-2026-45830 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H no
PYSEC-2026-3814 CVE-2026-45833 none no
PYSEC-2026-3815 CVE-2026-45831 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H no
GHSA-567q-5qvw-pf92 CVE-2026-112907 low CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L yes
GHSA-69hj-f68j-2879 CVE-2026-112909 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N yes
GHSA-8mx5-7m5m-r77g CVE-2026-112910 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L yes
GHSA-9vhv-jxww-xfm5 CVE-2026-112913 low CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L yes
GHSA-cwqr-hh33-gh44 CVE-2026-112915 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H yes
GHSA-fq56-3cx3-fjxp CVE-2026-112935 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N yes
GHSA-j8f7-rjxc-mr56 CVE-2026-112936 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L yes
GHSA-rfpc-qcw5-3pc4 CVE-2026-112939 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N yes
GHSA-v4x8-3wr5-3wq8 CVE-2026-112940 high CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H yes
GHSA-22hg-r758-rrw9 CVE-2026-112390 high yes
GHSA-24rc-8hj2-v98c CVE-2026-96638 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H yes
GHSA-254f-3936-288h CVE-2026-112391 medium yes
GHSA-27h8-gf7j-v5hc CVE-2026-112392 high yes
GHSA-332p-7hrc-92wf CVE-2026-112393 critical yes
GHSA-3j72-p6qg-6xp7 CVE-2026-96642 high yes
GHSA-4558-3h8r-v8xp CVE-2026-112394 medium yes
GHSA-462x-pgg6-55fp CVE-2026-112395 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L yes
GHSA-4rm8-3hmm-39fg CVE-2026-96641 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H yes
GHSA-4rr5-89j8-mwwm CVE-2026-112396 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-58r4-6rv3-gfh8 CVE-2026-112397 high yes
GHSA-5x8w-8jj5-q52h CVE-2026-112398 critical yes
GHSA-5xm2-6676-qcp9 CVE-2026-112399 high yes
GHSA-654x-cwwv-5j9c CVE-2026-114501 medium yes
GHSA-65qm-jvmh-6pqg CVE-2026-112400 high yes
GHSA-74r2-7ff9-mjj2 CVE-2026-112401 medium yes
GHSA-78g4-xqwv-q3g8 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-7mwm-ghpf-9vrm CVE-2026-112402 high yes
GHSA-8g5g-8vmr-9782 CVE-2026-112403 critical yes
GHSA-9v9v-9qvf-h2hj CVE-2026-96644 high yes
GHSA-c6hw-5grf-ff96 CVE-2026-112404 high yes
GHSA-cp9v-662q-vvx9 CVE-2026-112405 high yes
GHSA-f2g6-542v-9j58 CVE-2026-112406 high yes
GHSA-fc9g-5qg7-mf45 CVE-2026-112891 medium yes
GHSA-g4qv-2jxx-769h CVE-2026-96643 high yes
GHSA-g7cr-3p24-7wf7 CVE-2026-96778 high yes
GHSA-g842-9rc4-69pw CVE-2026-96637 high yes
GHSA-gg2r-wvfm-q9rx CVE-2026-112892 high yes
GHSA-j4m9-6w36-pw47 CVE-2026-112893 high yes
GHSA-jg86-v3jv-hrpm CVE-2026-112894 high yes
GHSA-mrfp-p49p-3hf2 CVE-2026-96640 high yes
GHSA-p4wg-p73j-c528 CVE-2026-112895 high yes
GHSA-p8hx-v2p6-rp84 CVE-2026-96636 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H yes

Showing 50 of 76 vulnerabilities.

Background: What a vulnerability scan can and cannot prove →

Dependencies 123 packages
Packages resolved 123
Stale 13
No linked repository 2
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools

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.

Install

How do I install the io.github.VBlackJack/cortex MCP server?

io.github.VBlackJack/cortex runs locally as a PyPI package, launched with uvx cortex-local-rag. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · cortex-local-rag

# add to Claude Code
claude mcp add vblackjack-cortex -- uvx cortex-local-rag
Common questions

What is the io.github.VBlackJack/cortex MCP server?

io.github.VBlackJack/cortex is an MCP server listed in the public MCP registry as io.github.VBlackJack/cortex. Local multi-client RAG server over the Model Context Protocol. This page covers its PyPI package (cortex-local-rag).

Is the io.github.VBlackJack/cortex MCP server still maintained?

io.github.VBlackJack/cortex is still listed as active in the MCP registry. We last reached this channel on 4 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 io.github.VBlackJack/cortex MCP server under?

io.github.VBlackJack/cortex declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.