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.1728 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
- AlicenseAqualityAmaintenanceToken-saving MCP proxy. Hides your MCP servers' tool lists behind a search tool and shrinks large tool results (GitHub, Playwright, logs, test output), keeping the full result available on request. One-command setup for Claude Code, Codex, Claude Desktop and Cursor.101MIT
- 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.489 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 the21,923 PyPI2MIT
- 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-
TDQS
Scored across 6 tools
Each tool has a distinct role: browsing runs/spans, searching text, reading one span, checking seal integrity, and checking proxy stats. The main overlap is between list_digests and list_spans, both of which browse the archive, but their descriptions clarify different granularity and output.
All tool names use consistent snake_case with a verb_noun structure: list_*, search_*, read_*, and get_*_status. The pattern is predictable and easy to parse.
Six tools is well-scoped for an archive browsing and status-checking server. Each tool covers a distinct operation, and none feels redundant or extraneous.
The surface covers listing, skimming, searching, reading spans, verifying seal integrity, and checking proxy status. Minor gaps such as run-level metadata or explicit archive export are not essential for the apparent purpose, so agents can still complete core workflows.