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.

CogniRepo

PYPI · COGNIREPO

FAISS, call graph, AST, BM25 — 34 MCP tools for AI agents. 50-80% token reduction. Offline.

Available components

pypi · cognirepo 45
+1 this week 45 Trust /100

Last scanned (5 hours ago)

Scores higher than 45% of PyPI servers

Category Code Search and Documentation

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 Security82
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects mcp 1.27.0, a direct dependency. A fixed version is available. 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 81 of 83 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to ashlesh-t/cognirepo). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 25 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package installed, but its server did not start, 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.

  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 1 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 −14
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: unverified → pass ▲ functional
  • 29 Oct 26 +5
    • CVE-2026-116685 affects this package: high ▼ security
    • CVE-2026-116686 affects this package: high ▼ security
    • CVE-2026-116684 affects this package: high ▼ security
    • Known CVEs: unverified → fail ▼ security
    • Security disclosure: pass → unverified ▼ functional
    • Dependency health: unverified → partial ▲ functional
  • 28 Oct 26 +9
    • Known CVEs: fail → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Dependency health: partial → unverified ▼ functional
  • 27 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 26 Oct 26 +45
    • CVE-2026-59951 affects this package: high ▼ security
    • CVE-2026-59950 affects this package: high ▼ security
    • CVE-2026-52869 affects this package: high ▼ security
    • CVE-2026-52870 affects this package: high ▼ security
    • CVE-2026-112398 no longer affects this package ▲ security
    • CVE-2026-96639 no longer affects this package ▲ security
    • CVE-2026-112393 no longer affects this package ▲ security
    • CVE-2026-112900 no longer affects this package ▲ security
    • CVE-2026-112403 no longer affects this package ▲ security
    • Known CVEs: CVE check failed: a known high-severity CVE affects mcp 1.27.0, a direct dependency. A fixed version is available. security
    • Score status: failed → scored ▲ functional
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 5 Nov 2026 · Analysed pypi/cognirepo@1.1.1

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 ashlesh-t/cognirepo
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/ashlesh-t/cognirepo/.github/workflows/publish.yml@refs/tags/v1.1.1
Rekor log index 1818474111
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:d8d0a123d940fc167e5e4768154edc64ee00826dcb8188772498f53ce802a49b

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 10 findings
ID CVE Severity Vector Fix available
GHSA-5h93-6whr-6q8j CVE-2026-116685 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-84m7-p3x7-pcfv CVE-2026-59951 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-hvrp-rf83-w775 CVE-2026-52870 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L yes
GHSA-jpw9-pfvf-9f58 CVE-2026-52869 high CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L yes
GHSA-rwrf-2pqf-9j8j CVE-2026-116686 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H yes
GHSA-vj7q-gjh5-988w CVE-2026-59950 high yes
GHSA-w4fh-qvv9-3v23 CVE-2026-116684 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
PYSEC-2026-3481 CVE-2026-52870 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L yes
PYSEC-2026-3482 CVE-2026-52869 high CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L yes
PYSEC-2026-3483 CVE-2026-59950 none yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 81 packages
Packages resolved 81
Stale 8
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 CogniRepo MCP server?

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

pypi · cognirepo

# add to Claude Code
claude mcp add ashlesh-t-cognirepo -- uvx cognirepo
Common questions

What is the CogniRepo MCP server?

CogniRepo is an MCP server listed in the public MCP registry as io.github.ashlesh-t/cognirepo. FAISS, call graph, AST, BM25, 34 MCP tools for AI agents. 50-80% token reduction. Offline. This page covers its PyPI package (cognirepo).

Is the CogniRepo MCP server safe to use?

CogniRepo scores 45 out of 100 on VerifyMCP. We recorded 10 known advisories against it as of 5 November 2026. Its build provenance is signed and verified. 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.

Is the CogniRepo MCP server still maintained?

CogniRepo is still listed as active in the MCP registry. We last reached this channel on 5 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 CogniRepo MCP server under?

CogniRepo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.