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.

cogvault

PYPI · COGVAULT

Local hybrid-search memory for AI agents over plain Markdown. Multi-tenant, offline, no LLM.

Available components

pypi · cogvault 49
0 this week 49 Trust /100

Last scanned (4 hours ago)

Scores higher than 47% of PyPI servers

Category Memory and Knowledge

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 Security98
  • No malware found by supply-chain analysis.Pass
  • Known CVEs were checked across the 49 of 51 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • Dependency health was assessed across the 49 of 51 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 NBibikov/cogvault). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 21 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.

  • 5 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 26 Oct 26 +49
    • CVE-2026-112403 no longer affects this package ▲ security
    • CVE-2026-112900 no longer affects this package ▲ security
    • CVE-2026-96639 no longer affects this package ▲ security
    • CVE-2026-112398 no longer affects this package ▲ security
    • CVE-2026-112393 no longer affects this package ▲ security
    • Known CVEs: fail → partial ▲ security
    • Score status: failed → scored ▲ functional
  • 24 Oct 26 0
    • CVE-2026-112398 affects this package: high ▼ critical
    • Security disclosure: unverified → fail ▼ functional
  • 23 Oct 26 0
    • CVE-2026-96639 affects this package: high ▼ critical
  • 22 Oct 26 0
    • CVE-2026-112393 affects this package: high ▼ critical
    • CVE-2026-112900 affects this package: high ▼ 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 5 Nov 2026 · Analysed pypi/cogvault@0.12.2

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 NBibikov/cogvault
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/NBibikov/cogvault/.github/workflows/publish.yml@refs/tags/v0.12.2
Rekor log index 3253636238
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:0ec3e29bb2451e53d889fe8d56f04b45046825abacb065d86b98468f2170facd

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

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

Dependencies 49 packages
Packages resolved 49
Stale 7
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 cogvault MCP server?

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

pypi · cogvault

# add to Claude Code
claude mcp add nbibikov-cogvault -- uvx cogvault
Common questions

What is the cogvault MCP server?

cogvault is an MCP server listed in the public MCP registry as io.github.NBibikov/cogvault. Local hybrid-search memory for AI agents over plain Markdown. Multi-tenant, offline, no LLM. This page covers its PyPI package (cogvault).

Is the cogvault MCP server safe to use?

cogvault scores 49 out of 100 on VerifyMCP. 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 cogvault MCP server still maintained?

cogvault 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 cogvault MCP server under?

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