Context Vault

io.github.RajdeepDas43Published by GitHub account RajdeepDas43v0.7.0Updated Oct 24, 2026

Governed memory for AI agents (Paramind AI): conflict-checked writes, time-travel reads, ACL, audit.

VerifiedSTDIODesktop onlyKnowledge & Memory

Overview

AI-generated overview

Context Vault is a local MCP server providing governed memory for AI agents, with conflict-checked writes, time-travel reads, access control and audit.

What you can do
  • Store and manage persistent memory for an AI agent, with writes checked for conflicts before they are accepted.
  • Read memory as it existed at an earlier point in time (time-travel reads).
  • Apply access control (ACL) to memory entries.
  • Keep an audit trail of memory activity.
  • No individual tools are listed in the registry entry, so exact operations are not documented.
When to use it
Worth considering when an assistant needs durable, auditable memory that multiple agents or users share and where conflicting or unauthorized writes must be controlled. Less useful for simple single-session note keeping.
Requirements
Runs as a local process over stdio, installed from the PyPI package context-vault-ai, so a Python environment is needed. Desktop-only; no remote or web execution. No authentication, environment variables or headers are declared.
Before you install
The server stores and governs agent memory, so anything written to it persists and is subject to its ACL and audit rules; review what data you allow an agent to store. No credentials are declared, but the registry entry lists no tools, so verify write, delete and access-control behavior before relying on it.

Installation

In SourceWeft

  1. Open Context Vault in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.7.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.