ctxfw
Related Servers
Alternatives to ctxfw
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI coding agents to reduce token usage and context bloat through AST skeletonization, prompt distillation, caching, and token-budget governance while preserving essential code context.1314,624 npm42MIT
- AlicenseAqualityBmaintenanceNeuro-symbolic deterministic context pruning middleware. Reduces tokens by 60%, drops local CPU TTFT by 62%, and prevents IP leakage via formal SPARQL contracts.23MIT
- AlicenseAqualityCmaintenanceDeterministic repository context packing for AI coding agents: selects, compresses, and budgets only the files a task needs. Measured 83% fewer input tokens at the same task coverage, fully local, no LLM in the loop.924 PyPI9Functional Source , Version 1.1, MIT Future
- AlicenseNot gradedqualityBmaintenanceReduces token consumption for AI coding agents by 50-70% through intelligent code context filtering, Git delta tracking, and local SQLite/Tree-sitter indexing.167 npmMIT
- AlicenseAqualityBmaintenanceEnterprise AST codebase context reduction engine with up to 95% token savings, 20 tools, polyglot support, and zero-leak security guardrails. "Toprak Ahmet Aydoğmuş"22331 PyPI17MIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to reduce token usage by condensing source code into AST skeletons, extracting specific symbols, compressing logs, and estimating token budgets.4MIT
TDQS
Scored across 5 tools
Each tool targets a distinct operation: single-file pruning, multi-module bundle compilation, spec evaluation, patch evaluation, and audit retrieval. Descriptions explicitly disambiguate boundaries, e.g. prune_file says 'for multi-module dependency graphs, use resolve_context_bundle instead' and evaluate_spec_axioms points to evaluate_patch for diffs.
All five tools use snake_case with a leading verb (prune_file, resolve_context_bundle, evaluate_spec_axioms, evaluate_patch, query_audit_ledger). The verb_noun pattern is predictable and the two evaluate_* tools share a consistent prefix for their judgment family.
Five tools is well-scoped for a context-bundling and verification framework: two for context generation, two for evaluation gates, one for audit. No tool looks redundant and none of the sub-capabilities appear padded.
The prune/bundle, spec-evaluate, patch-evaluate, and audit-query lifecycle forms a coherent closed loop, but session management is an implicit dependency: session_id (SES-...) is consumed as input with no tool to create or list sessions, and TokenCast budget state is referenced but never exposed.