# io.github.NORTHTEKDevs/lossless-context-mcp (npm · lossless-context-mcp)

Agent context flight recorder: restore after compaction, fan-out packs, signed git-bound receipts.

- Trust score: 75/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-23

## Components

- npm · `lossless-context-mcp`: 75/100 (this document), [markdown](https://verifymcp.io/servers/northtekdevs-lossless-context-mcp/lossless-context-mcp.md), [page](https://verifymcp.io/servers/northtekdevs-lossless-context-mcp/lossless-context-mcp)

## Channel facts

- Registry: `npm`
- Package: `lossless-context-mcp`
- Version: `2.0.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-23.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 98 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 11 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1321 tokens (~120/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 95% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.NORTHTEKDevs/lossless-context-mcp server?

io.github.NORTHTEKDevs/lossless-context-mcp runs locally as an npm package, launched with npx -y lossless-context-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add northtekdevs-lossless-context-mcp -- npx -y lossless-context-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "northtekdevs-lossless-context-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "lossless-context-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "northtekdevs-lossless-context-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "lossless-context-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add northtekdevs-lossless-context-mcp -- npx -y lossless-context-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "northtekdevs-lossless-context-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "lossless-context-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add northtekdevs-lossless-context-mcp --command npx --arg -y --arg lossless-context-mcp
```

### Hermes

```yaml
mcp_servers:
  northtekdevs-lossless-context-mcp:
    command: "npx"
    args: ["-y", "lossless-context-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "northtekdevs-lossless-context-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "lossless-context-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add northtekdevs-lossless-context-mcp -t stdio -c npx -a -y lossless-context-mcp
```

### Other

```json
{
  "mcpServers": {
    "northtekdevs-lossless-context-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "lossless-context-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-23 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-20 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-18 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-17 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-14 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-12 (score 70, +16)

- [security improvement] Malware scan: unverified → pass
- [functional] Package version: 1.4.0 → 2.0.0

### 2026-08-11 (score 54, −13)

- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [functional regression] Dependency health: 0.86 → unverified
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 90% → 95%
- [functional improvement] Stability: unverified → 0.07
- [functional] Package version: 1.2.3 → 1.4.0
- [functional] Package version: 1.2.3 → 1.3.0
- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-09 (score 67)

First indexed and scored.

## MCP tools (11)

### `read_file` (~241 tokens)

Read a text file through the context ledger. The FIRST read of a file/view (or the first after a context compaction) returns full content. A later read of an UNCHANGED view returns a short "reuse what you have" marker. A later read of a CHANGED view returns a unified DIFF to apply to the copy you already have. Optionally read just one symbol (function/class by name) or a line range instead of the whole file. All dedup is lossless: it only diffs/withholds content it can prove you still have. Every read is metered (see context_stats) and attested in the signed context receipt. Pass force_full:true for the whole content regardless.

Input parameters:

- `force_full` (boolean): Return full content even when a diff or unchanged-marker would suffice.
- `lines` (string): Return only this 1-based inclusive line range, e.g. "40-90".
- `path` (string, required): Path to the file to read (absolute, or relative to the server cwd).
- `symbol` (string): Return only this function/class/type by name (heuristic brace/indent extraction).

### `read_files` (~96 tokens)

Read a working set of text files in one call, each through the same lossless ledger as read_file (full on first contact, unchanged-marker or diff on re-reads). One call for N files instead of N calls. Per-file errors are reported inline without failing the batch.

Input parameters:

- `force_full` (boolean): Return full content for every file regardless of ledger state.
- `paths` (array, required): Files to read, in order.

### `outline` (~65 tokens)

Return a cheap structural outline of a file: declaration lines (functions, classes, types, methods) with line numbers, bodies elided. Use this to navigate a large/unknown file before reading specific parts with read_file.

Input parameters:

- `path` (string, required): Path to the file to outline.

### `context_stats` (~67 tokens)

Where did this session’s file-read tokens go? Totals, per-repo breakdown, heaviest files, dedup savings, and a USD estimate (LOSSLESS_PRICE_PER_MTOK, default $3/MTok input). Counted with a real tokenizer on exactly what this server sent.

### `working_set` (~97 tokens)

What has this session been working on? A heat-ranked table of the files the flight recorder knows about — from this server's own reads plus any transcript sweeps the hooks performed (last 24h) — with sizes, touch counts, and staleness vs current disk state. Use after a compaction to see what is recoverable, or anytime for orientation.

Input parameters:

- `limit` (integer): Max files to list (default 15).

### `restore_context` (~129 tokens)

Re-emit the working set after a compaction (or /clear) destroyed it. Serves CURRENT disk content of the requested files — by default the top of the pre-compaction manifest the sweep hook wrote — through the lossless ledger, annotating any file that changed since the model last saw it. Budget-capped so a restore cannot blow the fresh context; files over budget are listed, not silently dropped.

Input parameters:

- `budget_tokens` (integer): Approx token budget for restored content (default 25000).
- `files` (array): Specific files to restore (default: the manifest working set).

### `export_pack` (~174 tokens)

Build a fan-out context pack: the stable, hot files (ranked across sessions from the flight-recorder history) rendered as one deterministic block to embed VERBATIM in a custom agent-type's SYSTEM PROMPT. Siblings in a fan-out then hit the prompt cache on that shared prefix instead of each re-reading the same files (measured on a real review fan-out: 46.55% cheaper; per-task injection measured WORSE — see README). Files matching secret patterns are never packed.

Input parameters:

- `budget_tokens` (integer): Approx token ceiling for the pack (default 30000).
- `days` (integer): History window for ranking (default 14).
- `repo` (string): Only pack files from this repo root.
- `top` (integer): Max files in the pack (default 8).

### `coordination_status` (~67 tokens)

The air-traffic radar for concurrent agents on this machine: which agent processes are active (from the coordination plane the guard hooks maintain), what they have been editing, which files have cross-session activity, and where edit conflicts are brewing. Advisory visibility only — sessions without the hooks installed are invisible.

### `context_blame` (~135 tokens)

Forensics: what did the agent see of this file, and when? Every content version the flight recorder observed (SHA-256 + git blob SHA-1, first/last seen, capture source, sessions), plus what else was in context around a focus moment. The evidence-backed answer to "why did the agent do that?" — query history instead of trusting self-report.

Input parameters:

- `at` (string): Focus moment (ISO timestamp). Default: last time the file was seen.
- `path` (string, required): The file to blame.
- `window_minutes` (integer): Co-context window around the focus (default 30).

### `context_receipt` (~189 tokens)

Issue an HMAC-SHA256-signed context receipt: every file/view the model was shown via this ledger, the SHA-256 of each content version, git binding (blob SHA-1 per version, repo HEAD at issue time), delivery kinds, token totals, and an explicit coverage statement. With include_sweep, also attests native-tool reads captured by the transcript-sweep hooks. The auditable answer to "what did the AI see when it did this?". Signs with LOSSLESS_RECEIPT_KEY or the shared trust key file, so it verifies with the same key as trust-mcp receipts. Verify later with verify_context_receipt.

Input parameters:

- `artifact` (string, required): What this context evidence is for (repo, ticket, deploy, session id).
- `include_sweep` (boolean): Also attest files captured by transcript sweeps in the last 24h (source: sweep).

### `verify_context_receipt` (~61 tokens)

Verify a context receipt + signature pair against the local receipt key (timing-safe, canonicalized so JSON field order does not matter).

Input parameters:

- `receipt` (object, required): The receipt object exactly as returned by context_receipt.
- `signature` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/northtekdevs-lossless-context-mcp/lossless-context-mcp#diagnostics

## Score history

- 2026-08-23: 75
- 2026-08-22: 74
- 2026-08-21: 74
- 2026-08-20: 74
- 2026-08-19: 73
- 2026-08-18: 73
- 2026-08-17: 72
- 2026-08-16: 71
- 2026-08-15: 71
- 2026-08-14: 71
- 2026-08-13: 70
- 2026-08-12: 70
- 2026-08-11: 54
- 2026-08-10: 67
- 2026-08-09: 67

## Common questions

### What is the io.github.NORTHTEKDevs/lossless-context-mcp server?

io.github.NORTHTEKDevs/lossless-context-mcp is listed in the public MCP registry as io.github.NORTHTEKDevs/lossless-context-mcp. Agent context flight recorder: restore after compaction, fan-out packs, signed git-bound receipts. This page covers its npm package (lossless-context-mcp).

### Is the io.github.NORTHTEKDevs/lossless-context-mcp server safe to use?

io.github.NORTHTEKDevs/lossless-context-mcp scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 August 2026. It declares no install or post-install scripts. 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.

### What tools does the io.github.NORTHTEKDevs/lossless-context-mcp server expose?

io.github.NORTHTEKDevs/lossless-context-mcp exposes 11 tools: read_file, read_files, outline, context_stats, working_set, and 6 more. Their descriptions and schemas cost roughly 1,321 tokens of context every time the server is loaded.

### Is the io.github.NORTHTEKDevs/lossless-context-mcp server still maintained?

io.github.NORTHTEKDevs/lossless-context-mcp is still listed as active in the MCP registry. We last reached this channel on 23 August 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 io.github.NORTHTEKDevs/lossless-context-mcp server under?

io.github.NORTHTEKDevs/lossless-context-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/lossless-context-mcp
- Socket report: https://socket.dev/npm/package/lossless-context-mcp
- Repository: https://github.com/NORTHTEKDevs/lossless-context-mcp
- Changelog RSS feed: https://verifymcp.io/servers/northtekdevs-lossless-context-mcp/lossless-context-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/northtekdevs-lossless-context-mcp/lossless-context-mcp.json
- HTML version of this page: https://verifymcp.io/servers/northtekdevs-lossless-context-mcp/lossless-context-mcp