ontoprune-mcp
Related Servers
Alternatives to ontoprune-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceIn-memory polyglot AST pruning and deterministic context firewall for coding agents, eliminating up to 72.4% token bloat with zero telemetry egress.65166 PyPI8Apache 2.0
- 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
- 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
- AlicenseNot gradedqualityBmaintenanceDeterministic context compression for MCP agents, reducing token usage via 11 tools for prompts, history, shell output, file deltas, and code navigation without ML or GPU.9MIT
- 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
- AlicenseNot gradedqualityDmaintenanceModel-agnostic context management middleware for LLM-powered workflows, providing persistent selective memory across sub-conversations using RAG over embedded summaries.MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: prune_context extracts a compact contract from source code, while verify_response validates LLM-generated code against such a contract. Their descriptions and argument sets make the boundary unambiguous.
Both names follow a consistent verb_noun pattern in snake_case: prune_context and verify_response. There are no mixed conventions or vague verbs.
Two tools is slightly below the typical 3-15 sweet spot, but each tool is substantial, non-redundant, and directly supports a focused extract-and-verify workflow. The set does not feel bloated or padded.
The pair covers the core lifecycle of extracting a contract and verifying code against it, with flexible input options for files or rendered contracts. Minor gaps exist for symbol discovery, batch pruning, or contract management, but agents can work around them.