lossless-context-mcp (NORTHTEKDevs/lossless-context-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Emerging
74/100
11 days ago

lossless-context-mcp

MCP server providing lossless file reads with deduplication, per-repo token metering, and HMAC-signed context receipts. Enables auditable, vendor-neutral measurement of what an AI agent saw.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

NORTHTEKDevs

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: LOSSLESS_RECEIPT_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configLOSSLESS_ARCHIVE_BYTEScontent-addressed, capped at 512 MiB () with LRU eviction; event
configLOSSLESS_ARCHIVE_EXCLUDEplus your own globs) are never stored — the check covers
configLOSSLESS_CONTEXT_DIRThe archive lives at ~/.lossless-context/archive (override: ),
configLOSSLESS_COORDhow much it catches in practice is not yet measured. =off disables
configLOSSLESS_COORD_INTENT_SECSat the permission prompt lingers up to (90 s) before
configLOSSLESS_COORD_SESSION_SECS
configLOSSLESS_EVENTS_DAYSlogs age out after 30 days (). Nothing ever leaves your machine.
configLOSSLESS_GUARD_SEEN_CAP
configLOSSLESS_LEDGER_BYTES
configLOSSLESS_MANIFEST_TOP_K
configLOSSLESS_MARKER_COST_BYTES
configLOSSLESS_MAX_BYTES
configLOSSLESS_PRICE_PER_MTOK
🔐 secretLOSSLESS_RECEIPT_KEY
configLOSSLESS_RECEIPT_KEYFILE
configLOSSLESS_SWEEP_EXACT_BYTES
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

11/11 tools missing one or more hints — read_file (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); read_files (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); outline (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +8 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

Only 3/11 tools referenced in tests (27%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

4 child_process/subprocess calls in production code — runs shell commands (bench/smoke.mjs:18, bench/smoke.mjs:47, bench/smoke.mjs:207)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/northtekdevs-lossless-context-mcp-1fv5ao)](https://m8ven.ai/mcp/northtekdevs-lossless-context-mcp-1fv5ao)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 47440a012e701fd8eddd4167fb5c3fa7faa44fdb
code hash: 996c29bfb97cd2b25373c67f9ce20ff1734f3356594b912831270179960de037
verified: 8/20/2026, 9:50:34 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client