Skip to main content
Glama
ProfRandom92

CompText MCP

by ProfRandom92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to CompText MCP

No user-submitted related servers found.

    Related Servers

    • densely

      alibaizhanov
      A
      license
      Not graded
      quality
      A
      maintenance
      Lossless context compression for LLMs, packing text into 2x-8x fewer tokens with byte-exact reconstruction. Provides MCP tools to compress files/text and expand exact slices, verified by sha256.
      30 PyPI
      6
      MIT

    • Òtítọ́

      BASHBOP
      A
      license
      A
      quality
      B
      maintenance
      Local-first code context CLI + MCP server: discover, index, and search repos; generate task-aware context packs, code maps, agent harnesses, and PR-review/merge-readiness gates for coding agents and reviewers.
      4
      13
      548 npm
      1
      MIT

    • DevProjex MCP Server

      Avazbek22
      A
      license
      A
      quality
      A
      maintenance
      Local-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.
      17
      7
      24
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: contract checking, GitHub packaging, Hugging Face export, context packing, replay digest, Rust audit, and status. There is no overlap or ambiguity.

    Naming Consistency5/5

    All tools follow a consistent 'comptext_' prefix followed by descriptive snake_case names (e.g., comptext_contract_check, comptext_status). The pattern is uniform and predictable.

    Tool Count5/5

    With 7 tools, the count is well within the ideal range (3-15). Each tool serves a clear function without excess or deficiency for the server's apparent scope.

    Completeness4/5

    The tools cover core workflows: contract checks, exports, context packing, digests, audits, and status. Minor gaps might exist (e.g., no tool for clearing or resetting state), but the set is largely complete for typical usage.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources