context-guardian
Related Servers
Alternatives to context-guardian
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server providing context usage estimation, conversation compaction, and durable semantic memory via local embeddings and SQLite.1710 npm3MIT
- AlicenseAqualityCmaintenanceProvides reversible context compression for AI agents, reducing token usage while preserving the ability to retrieve original content, and serves as an MCP server for integration with tools like GitHub Copilot and Claude Code.31Apache 2.0
- AlicenseAqualityAmaintenanceAggregator MCP proxy that collapses N downstream MCP servers into 4 meta-tools with progressive tool discovery, and compresses large tool outputs (HTML→Markdown, JSON summarization) with full-output retrieval via read_more and a per-session token-savings report.475 npm2MIT
- AlicenseAqualityAmaintenanceA transparent proxy that sits in front of any other MCP server and shrinks its tool output before it reaches the model. Lossless by default: the transformed bytes are a denser encoding of the same data, with a round-trip gate asserting an exact inverse over the corpus, so nothing is dropped, summarised, or offloaded to a cache that expires. Repeated calls to the same tool emit a delta against the2733 PyPI1MIT
- FlicenseNot gradedqualityDmaintenanceToken-optimized multi-agent orchestration MCP server that owns session state, compacts context between agent hops, routes work to smaller models when safe, and reports estimated token savings.1-
- AlicenseNot gradedqualityBmaintenanceCompresses multi-turn conversation history by stripping verbose boilerplate and filler tokens while preserving critical tool parameters and named entities, deterministically cutting inference costs by 40-60%. Runs as a zero-dependency Python MCP server or importable module, compatible with Claude Desktop, Cursor, and other MCP runtimes.7MIT
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes: guardian_status reads live proxy metrics, search_spans searches archived conversation text, and read_span fetches one specific span's content. Although search_spans and read_span both touch spans, the search-vs-read boundary is unambiguous.
All names use consistent snake_case, which is good. There's a minor deviation in verb style: search_spans and read_span are verb_noun, while guardian_status is a noun phrase (status) rather than an action, but the names remain predictable and readable.
Three tools is on the lean side, but for a focused read-only observability surface (status + archive search + span read) each tool earns its place. It's slightly thin rather than excessive.
Status, search, and span retrieval cover the main inspection workflow. Minor gaps exist, such as enumerating all runs/spans without a prior search or triggering/configuring compaction, but these are workable around for an inspection tool.