Skip to main content
Glama

Related Servers

Alternatives to context-guardian

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Provides 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.
      3
      1
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Token-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.
      10
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Aggregator 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.
      4
      89 npm
      2
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      A 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 the
      2
      1,923 PyPI
      2
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Token-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

    A4.4/5.0

    Scored across 6 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessNo issues