tzero-mcp
Related Servers
Alternatives to tzero-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceNext-gen AST codebase map, token compression (70%~85% savings), and context packaging engine for AI coding agents & IDEs.43MIT
- AlicenseAqualityDmaintenanceProvides intelligent code context and analysis through semantic compression, AST parsing, and multi-language support. Offers 60-80% token reduction while enabling AI assistants to understand codebases through local analysis, OpenAI-enhanced insights, and GitHub repository integration.611 npm3MIT
- AlicenseBqualityCmaintenanceEnables LLMs to efficiently read, write, and refactor code using precise AST-based operations, reducing token usage and context window waste.2525 npm3MIT
- AlicenseNot gradedqualityDmaintenanceProvides structured, token-efficient code context for AI assistants by indexing codebases with AST-level analysis, supporting 17+ languages, enabling semantic search, call-site tracking, and PR attribution.158 PyPI41MIT
- AlicenseNot gradedqualityDmaintenanceMake any LLM a codebase expert instantly. Provides deep code intelligence through semantic search, architecture mapping, security analysis, and smart context that fits perfectly in token windows.MIT
- FlicenseAqualityBmaintenanceEnables precise source code retrieval via tree-sitter AST parsing, cutting AI token costs by 86-99% by indexing codebases and fetching only needed symbols and structural queries (e.g., blast radius, importers) on demand.6-
TDQS
Scored across 21 tools
Tools target distinct code-analysis operations (context generation, dependency graphs, architecture rules, quality audits, token metrics). Sibling Routing guidelines explicitly differentiate overlapping tools like get_project_context_tree vs get_smart_skeleton_context and analyze_change_impact vs trace_symbol_call_chain. However, several graph-analysis tools (query_module_dependencies, analyze_change_impact, trace_symbol_call_chain, rank_repository_pagerank) have adjacent scopes that could still cause occasional misselection.
All tool names are snake_case and follow a verb_noun structure (get_*, query_*, generate_*, audit_*, etc.). The specific verbs vary but are semantically appropriate and consistent, with no camelCase or chaotic style.
21 tools is in the heavy range (16-25) for a single server. Although each appears to serve a distinct sub-purpose, the set is large enough that discovery and selection may be cumbersome.
The surface covers major static-analysis workflows: context generation, dependency mapping, impact analysis, call tracing, architecture enforcement, security scanning, quality audits, and token metrics. Some gaps exist, such as no direct symbol-by-name lookup beyond semantic search or no runtime/test coverage analysis, but these are minor for the apparent read-only static-analysis domain.