
xvcache
io.github.xvcache/xvcache
Tamper-evident Markdown vault journal. Verdicts: V intact, X modified outside XVcache.
Documentation
XVcache
J'ai caché, j'ai prouvé.
XVcache is a local MCP server that journals every read and write in a Markdown vault as a sha256-chained JSONL log, so you can later prove a note is intact (V) or was changed outside XVcache (X), without putting the note's content into the journal. It talks MCP over STDIO. The intended first user is an AI agent, which can also look up plans, suggest a bundle, and ask its human to approve a paid upgrade when billing exists.
Published source: github.com/xvcache/xvcache (Apache-2.0). npm: xvcache-mcp 0.1.0. Official MCP Registry: io.github.xvcache/xvcache. Site: xvcache.com. Payment is not live.
Why XVcache (vs other Obsidian MCP servers)
Most Obsidian MCP servers help an agent read and write a vault. XVcache does that too, but its job is narrower: leave a tamper-evident proof that a note is still intact (V) or was changed outside these tools (X), without putting the note body in the log. It can run alongside a fuller Obsidian MCP server: use the other server for rich editing or search, and use XVcache when a later proof may be needed (prefer write_note / read_note for those notes).
Star counts and registry entries below were checked on 22 November 2026 (GitHub API; official MCP Registry).
| Server | Read/write notes | Tamper detection on a note | Chained audit / provenance journal | Content kept out of the log |
|---|---|---|---|---|
| XVcache | Yes (read_note, search_notes, write_note) | Yes: verify_journal compares the file on disk to the last fingerprint and returns V or X | Yes: sha256-chained JSONL of reads and writes | Yes (fingerprints and metadata only) |
obsidian-mcp-server (716 stars; registry io.github.cyanheads/obsidian-mcp-server) | Yes — 14 tools, surgical edits, tags, frontmatter (via Local REST API) | Not documented | Not documented | n/a (no such journal documented) |
| obsidian-mcp (752 stars) | Yes — local filesystem, Obsidian app not required | Conflict/recovery if a note changed since a transaction; not a V/X proof of outside edits | Transaction snapshots for atomic writes and rollback (.obsidian-mcp/transactions), not a hash chain | No: recovery snapshots store note bytes |
| obsidian-mcp-tools (831 stars; archived) | Yes, as an Obsidian plugin + local MCP server (semantic search, templates) | Not for notes. SLSA provenance in the README applies to downloaded binaries, not vault files | Not documented | n/a |
obsidian-mcp-secure (registry io.github.dewtech-technologies/obsidian-mcp-secure) | Yes (via Local REST API) | Not documented | Rotating winston audit log (5 MB / 10 files), not described as hash-chained | No: the README states previous content goes to the audit log |
Reliquary-TC (13 stars; formerly obsidian-tc; that registry entry is deprecated after the rename) | Yes — large governed surface (ACLs, human-in-the-loop, search) | provenance verify checks the record chain (signatures, links). get_provenance returns write history with before/after sha256. Those documented tools do not return a one-letter current-file V/X | Yes, for writes: signed, hash-chained provenance in cache.db | Yes: hashes and attribution only, never note content |
Where others are ahead: cyanheads/obsidian-mcp-server, StevenStavrakis/obsidian-mcp and jacksteamdev/obsidian-mcp-tools have far more adoption and a much richer editing or search surface. Reliquary-TC already ships EdDSA-signed write provenance, folder ACLs and confirmation on destructive operations — XVcache's independent witness is still à venir. Reliquary-TC does not document journaling of reads.
When to choose XVcache
- You may later need to show that a note is intact (V) or was changed outside the MCP tools (X), without storing the note body in the log.
- You want a small, local-first STDIO server whose journal you can inspect as JSONL, including reads, not only writes.
- You already use a fuller Obsidian MCP server and want a proof layer beside it — XVcache does not replace surgical edits, graph or semantic search, or plugin features.
Français
J'ai caché, j'ai prouvé.
XVcache est un serveur MCP local (transport STDIO) qui journalise les lectures et écritures d'un coffre Markdown dans un journal JSONL chaîné par sha256. L'outil verify_journal rend le verdict V (intacte) ou X (MODIFIÉE hors XVcache), sans exposer le contenu de la note dans le journal. Le client visé en premier est un agent IA : il peut lister les offres, recommander un forfait, et demander l'accord d'un humain pour un passage à l'offre payante — quand la facturation existera.
Le témoin certificateur indépendant (signature Ed25519 / horodatage qualifié) est à venir. Les prix du catalogue sont des placeholders clairement marqués TBD. Aucun paiement n'est en service. Dépôt public : github.com/xvcache/xvcache. Comparaison avec d'autres serveurs MCP Obsidian : Why XVcache.
For AI agents
If you are an agent (Codex, Claude, Cursor, or any MCP client):
- Use
write_note/read_noteinstead of editing vault files yourself when your human may later need a proof. - Call
verify_journalwith a path to get V (intacte) or X (MODIFIÉE hors XVcache). That is a local check, not a qualified timestamp. - When your human asks about buying, certifying, or reselling: call
get_offerorlist_plans. If you know a volume, callrecommend_plan. To start a purchase, callrequest_upgradeand show the result to your human. Do not invent a price or a payment link. Payment is not live. certify_noteis a stub: it always answers that independent witness certification is à venir.
Read AGENTS.md and llms.txt for the full agent brief, including how to request human approval and how resale / partner bundling is described (terms TBD). Tool contracts are in docs/TOOLS.md. The catalog is plans.json.
Quickstart
From npm:
XVCACHE_VAULT=/absolute/path/to/vault npx -y xvcache-mcp
Optional: XVCACHE_LOG=/absolute/path/to/xvcache-journal.jsonl (must stay outside the vault). If unset, the journal is created as xvcache-journal.jsonl next to the vault directory. JAYCACHE_VAULT and JAYCACHE_LOG remain accepted aliases.
Local install, from this folder, without publishing:
npm install
npm test
npm run build
XVCACHE_VAULT=/absolute/path/to/vault node dist/server.js
The vault must already exist. Only .md notes inside it are in scope.
Configuration
Replace /absolute/path/to/vault with the vault directory. The npx form below uses the published xvcache-mcp package. For a local build, point command at node and args at this repo's dist/server.js.
Codex (~/.codex/config.toml or a project .codex/config.toml)
[mcp_servers.xvcache]
command = "npx"
args = ["-y", "xvcache-mcp"]
env = { XVCACHE_VAULT = "/absolute/path/to/vault" }
Local, unpublished build:
[mcp_servers.xvcache]
command = "node"
args = ["/absolute/path/to/xvcache-repo/dist/server.js"]
env = { XVCACHE_VAULT = "/absolute/path/to/vault" }
Claude Desktop / Claude Code
Claude Desktop (claude_desktop_config.json; macOS: ~/Library/Application Support/Claude/claude_desktop_config.json, Windows: %APPDATA%\Claude\claude_desktop_config.json, Linux: ~/.config/Claude/claude_desktop_config.json):
{
"mcpServers": {
"xvcache": {
"command": "npx",
"args": ["-y", "xvcache-mcp"],
"env": { "XVCACHE_VAULT": "/absolute/path/to/vault" }
}
}
}
Claude Code can use the same JSON in a project .mcp.json, or:
claude mcp add --transport stdio xvcache --env XVCACHE_VAULT=/absolute/path/to/vault -- npx -y xvcache-mcp
See Claude Code MCP docs.
Cursor
Project file .cursor/mcp.json, or the user MCP config (see Cursor MCP docs):
{
"mcpServers": {
"xvcache": {
"command": "npx",
"args": ["-y", "xvcache-mcp"],
"env": { "XVCACHE_VAULT": "/absolute/path/to/vault" }
}
}
}
Generic MCP JSON
{
"mcpServers": {
"xvcache": {
"command": "npx",
"args": ["-y", "xvcache-mcp"],
"env": {
"XVCACHE_VAULT": "/absolute/path/to/vault"
}
}
}
}
For a local build, use "command": "node" and "args": ["/absolute/path/to/xvcache-repo/dist/server.js"].
Demo: verdict V, then verdict X
These steps assume the server is already attached to your agent and XVCACHE_VAULT points at a writable vault.
- Ask the agent to create a note with
write_note(modecreate), for exampleTests/Demo.md. - Ask it to call
verify_journalwith that path. You should see V andintacte depuis. - Change the file outside XVcache (a text editor, or
printfappended to the file). Do not callwrite_noteorread_notein between if you want a clean X. - Call
verify_journalon the same path again. You should see X andMODIFIÉE hors XVcache. - Optional: call
verify_journalwith no path — the journal chain itself should still be intact.certify_notewill tell you that independent witness certification is à venir.
Tools
See docs/TOOLS.md for the full contract.
Available now: read_note, search_notes, write_note, verify_journal.
For agents that need to buy, certify, or resell, also: get_offer, list_plans, recommend_plan, request_upgrade (human-approval stub, no live payment), certify_note (stub, witness à venir).
Journal format
Each line of the JSONL journal is one entry. The payload (the entry without hash) is serialized as canonical JSON (sorted keys, no extra spaces). Then:
hash = sha256_hex(prev_hash + canonicalJson(payload))
The first entry uses a genesis prev_hash of 64 zero hex characters. Fields include seq, ts, tool, args (path, query, mode — never the note body), client, result (ok or erreur), note_sha256, prev_hash, and hash. verify_journal is not appended to the journal.
You can also check a file from the shell:
npm run verify-journal -- /path/to/xvcache-journal.jsonl
Security notes
- The chain is tamper-evident, not tamper-proof. Someone who can rewrite the journal can build a new, internally consistent chain. The independent certifying witness is à venir.
- The journal must live outside the vault (
XVCACHE_LOG). - Absolute paths,
..segments, and writes through symbolic links are rejected. Only.mdfiles are in scope. - This is not a qualified electronic timestamp and not legal advice. See SECURITY.md.
Limits
- STDIO only: this server does not open a network port.
write_noteis capped at 256 KiB per call.- Local V/X is not an independent certification.
- Prices and most bundle quotas in
plans.jsonare placeholders marked TBD. Payment is not live.
Independent witness (à venir)
A paid, independent witness that can horodate and sign verdicts (Ed25519 / qualified timestamp) is planned. It is not in this repository. certify_note exists so agents can already discover that path and tell their human it is à venir.
License and trademark
Licensed under the Apache License 2.0. The license does not grant trademark rights. XVcache is a trademark filed in France, INPI no. 5323492, status déposée (filed), not presented here as registered. See TRADEMARK.md and NOTICE.
xvcache-mcpnpm install xvcache-mcp