lossless-context-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOSSLESS_RECEIPT_KEY | No | HMAC key used for signing context receipts. If not set, falls back to the shared trust-mcp key file. | |
| LOSSLESS_PRICE_PER_MTOK | No | Price per million tokens used for USD estimation in context_stats. Default is $3/MTok. | 3 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_fileA | 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. |
| read_filesA | 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. |
| outlineA | 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. |
| context_statsA | 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. |
| context_receiptA | Issue an HMAC-SHA256-signed context receipt for this session: every file/view the model was shown, the SHA-256 of each content version, how it was delivered (full/diff/unchanged), and token totals. 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. |
| verify_context_receiptA | Verify a context receipt + signature pair against the local receipt key (timing-safe, canonicalized so JSON field order does not matter). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: single-file read, batch read, structural outline, usage statistics, receipt creation, and receipt verification. The only overlapping pair is read_file/read_files, but the plural and description make the batch distinction unambiguous.
The naming is mostly predictable but mixes verb-led tools (read_file, read_files, verify_context_receipt) with noun-led tools (outline, context_stats, context_receipt). The underscore convention is consistent, but the lack of a uniform verb_noun pattern is a minor deviation.
Six tools is well-scoped for a file-context ledger server, covering reading, outlining, batching, statistics, and audit without unnecessary bloat or obvious omissions.
The server covers the full intended workflow: navigate with outline, read with read_file/read_files, monitor usage with context_stats, and audit with context_receipt/verify_context_receipt. No critical operations are missing for its stated purpose.