Lossless Context MCP server
Agent context flight recorder: restore after compaction, fan-out packs, signed git-bound receipts.
4 stars95 downloads/wk
Reviews
Write oneNobody has reviewed Lossless Context yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Lossless Context tools (11)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
context_blameForensics: what did the agent see of this file, and when? Every content version the
context_receiptIssue an HMAC-SHA256-signed context receipt: every file/view the model was shown via
context_statsWhere did this session’s file-read tokens go? Totals, per-repo breakdown, heaviest
coordination_statusThe air-traffic radar for concurrent agents on this machine: which agent processes
export_packBuild a fan-out context pack: the stable, hot files (ranked across sessions from the
outlineReturn a cheap structural outline of a file: declaration lines (functions, classes,
read_fileRead a text file through the context ledger. The FIRST read of a file/view (or the
read_filesRead a working set of text files in one call, each through the same lossless ledger as
restore_contextRe-emit the working set after a compaction (or /clear) destroyed it. Serves CURRENT
verify_context_receiptVerify a context receipt + signature pair against the local receipt key (timing-safe,
working_setWhat has this session been working on? A heat-ranked table of the files the flight
Public scan report
scanner v0.1.10 · 2026-11-04 · same rubric, same numbers if you re-run it
- Code scan23 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 60 days ago12/15
- Maintainer identityregistry namespace matches repository owner6/10
How Lossless Context compares
Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 70% of 1,119 Developer tools servers
- Tools
- 11
- the typical Developer tools server has 7
- Tools that change things
- 0%
- typical: 5%. Fewer write tools means less an agent can break
- GitHub stars
- 4
- more than 77% of 855 Developer tools servers
- Downloads a week
- 95
- more than 58% of 436 Developer tools servers with a package
What its tools let an agent do: 11 read
Install Lossless Context in Claude Code, Cursor or VS Code
Runs npx -y lossless-context-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add lossless-context-mcp -- npx -y lossless-context-mcp
What the publisher says
From the Lossless Context repository's README, as published. We do not edit it. Read it on GitHub
lossless-context-mcp
The flight recorder for your agent's context. A persistent, hook-fed ledger of every file version your coding agent was shown — so a compaction can't destroy the working set, a subagent fleet doesn't pay for the same files N times, and you can prove afterward exactly what the model saw.
┌──────────────────────┐
ledger reads ──────▶│ │──▶ RESTORE working set survives /compact
(read_file, MCP) │ flight recorder │──▶ PACKS one cache-cached prefix for a fan-out fleet
transcript sweeps ─▶│ (content-addressed │──▶ RECEIPTS signed, git-bound "what did it see"
(native Read/Edit) │ archive on disk) │──▶ METERING where the read tokens went, in dollars
└──────────────────────┘See it
Compaction destroys your agent's working set. Not anymore — sweep at PreCompact, manifest injected after, blind edit blocked, working set restored, edit allowed:
Two agents, one file — air traffic control. The second agent is stopped mid-clobber, with the culprit named:
Every line in these recordings is genuine output from the shipped code — the demos are generated by docs/demo/make-demo.mjs, which drives the real hooks and server and renders what they actually said. Re-run it yourself.
1. Restore: compaction can't destroy your working set anymore
When Claude Code compacts, roughly two-thirds of a typical context is tool output — mostly file contents — and compaction discards it permanently. The model then flails: re-reading files it half-remembers, or worse, guessing at contents it no longer has (#27242 is the ask, at 80 👍).
The flight recorder closes the loop automatically:
the session touched (native Read/Edit/Write included, not just MCP reads), then writes a ranked working-set manifest. Fast enough to sit on the compaction path — one real 14 MB transcript swept in 361 ms; measure yours: node bench/sweep-bench.mjs .
- PreCompact — the sweep hook parses the session transcript and archives every file
fresh context: "your working set was these 12 files (edited ones first); restore any of them instead of guessing."
- SessionStart(compact) — the inject hook puts a compact manifest back into the
budget-capped, annotating any file that changed since the model last saw it.
- restorecontext** — re-emits the working set from current disk state,
Cross-session memory tools (claude-mem and friends) summarize what happened for the next session. This is the complementary, mid-session layer: file-version-exact recovery of what you were just working on.
2. Blind-edit guard: the recorder as an active safety net
The recorder knows exactly which file versions the model has actually seen this context epoch. A PreToolUse hook uses that to stop the two ugliest edit failures before the write lands:
context was compacted/reset, working from a summary's memory of the content. (The harness's own read-before-edit tracking is not documented to survive compaction, and newer models are allowed to edit unread files at all.) Denied, with a one-line reason the model sees: read it (or restorecontext), then retry.* Self-healing — costs exactly one extra read.
- Post-compaction guess-edits — the model edits a file it hasn't read since its
agent, you, a formatter). Content-hash compared, not mtime-guessed. Denied with the same re-read instruction.
- Stale-base edits — the file changed on disk since the model read it (another
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Lossless Context: common questions
- Is Lossless Context MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the Lossless Context safety report
- How do I install Lossless Context?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Lossless Context need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Lossless Context maintained?
- The last commit was 60 days ago (2026-09-05). The latest release is v2.0.0.
- What can I use instead of Lossless Context?
- Servers from other publishers that do the same job: Repowise MCP server, Git MCP server and Gitwand MCP server.
- How does Lossless Context compare with other Developer tools MCP servers?
- safety score 85/100 (higher than 70% of 1,119 Developer tools servers); tools 11 (the typical Developer tools server has 7); tools that change things 0% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Lossless Context
Same job from other publishers: the closest match first, then the best rated.
RepowiseCodebase intelligence for AI coding agents — graph, git history, docs, decisions, code health.not reviewedEstablishedB- GitComprehensive Git MCP server enabling native git tools including clone, commit, worktree, & more.not reviewedEstablishedA
- GitwandAuto-resolves Git merge conflicts so agents only touch the complex hunks.not reviewedEstablishedA
- PalinodeInspectable, correctable project memory in git-versioned Markdown for AI agents.not reviewedEstablishedC
ContentrainGit content governance, 23 deterministic MCP tools. Hosted: docs.contentrain.io/developer/mcp-cloudnot reviewedEstablishedC