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.
      56 PyPI
      8
      MIT

    • Solumbe

      BASHBOP
      A
      license
      A
      quality
      A
      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.
      14
      749 npm
      2
      MIT

    • CodexPro Runtime

      Menglook
      A
      license
      B
      quality
      B
      maintenance
      A local, evidence-driven MCP runtime and control plane for open-source maintainers that provides workspace-bounded tools including controlled file operations, command execution, validation primitives, durable execution records, and human review workflows via stdio and Streamable HTTP transports.
      33
      MIT

    • repoflux

      dirka111q-maker
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables local LLM tools and agentic IDEs to inspect repository token maps, retrieve clean token-bounded codebase snapshots, and audit code for hardcoded secrets via MCP over stdio.
      656 npm
      4
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    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