CompText MCP
Related Servers
Alternatives to CompText MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceLossless 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.70 PyPI8MIT
- AlicenseAqualityBmaintenanceLocal-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.14428 npm3MIT
- AlicenseAqualityBmaintenanceZero-dependency stdio bridge to Moltline Studio's fleet of 14 hosted MCP servers covering code review, time operations, data transforms, business ops, education, research, outreach and more. Free tier requires no registration; premium tools unlock with a license. Independently audited, MCPize Verified A.10MIT
- AlicenseBqualityDmaintenanceA 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.33MIT
- AlicenseAqualityBmaintenanceTurn any folder or Git repo into safe, token-efficient context for LLMs, AI chats, and coding agents like Claude Code, Codex, and Cursor — local-first GUI, TUI, CLI, and a read-only MCP server with Live Context, agent journal, Smart Ignore, secret/PII redaction, Git scopes, and code compression. Windows, macOS, Linux.839Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables 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.16 npm4MIT
TDQS
Scored across 7 tools
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.
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.
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.
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.