lossless-context-mcp
Related Servers
Alternatives to lossless-context-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLocal-first MCP server that gives AI agents token-efficient context from any codebase: project tree, search, and budgeted packs. Secret redaction is enforced by the server, Git scopes and syntax-aware compression keep packs small. The same engine ships as a GUI, TUI, and CLI.17724Apache 2.0
- AlicenseCqualityAmaintenanceLocal-first MCP server that turns project documentation and source code into durable, evidence-backed context for AI agents, with bounded retrieval and explicit gap reporting.8318 npmApache 2.0
- FlicenseNot gradedqualityBmaintenanceMCP server for Agent Context OS that compiles engineering docs into a knowledge graph, detects code drift, and serves token-budgeted context packs to AI coding agents via MCP.-
- AlicenseCqualityCmaintenanceSmart MCP server that reads your code, understands file connections, and provides precise context to AI coding assistants, reducing token usage and preventing errors from outdated or irrelevant files.173MIT
- AlicenseAqualityCmaintenanceRead-only MCP server providing AI access to verifiable web, GitHub, and local sources, plus a managed fantasy entity catalog, with strong security and provenance tracking.101MIT

logicstamp-mcpofficial
AlicenseAqualityCmaintenanceMCP server that provides AI assistants with structured access to codebases via LogicStamp Context, enabling component analysis, dependency graphs, drift detection, and token-optimized context delivery.78 npm4MIT
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.