A
licenseA
qualityD
maintenanceAn MCP server that provides local code quality analysis for AI coding assistants, supporting file analysis, git diff review, and full project scanning with quality scoring.
4
3
MIT
Scopewalker MCP
by timohaa
Related Servers
Alternatives to Scopewalker MCP
No user-submitted related servers found.
Related Servers
flyto-indexerofficial
AlicenseNot gradedqualityAmaintenanceMCP server that gives AI assistants impact analysis, cross-project reference tracking, and code health scoring.47 PyPI4Apache 2.0- AlicenseNot gradedqualityBmaintenanceAn MCP server that provides code quality checks for AI coding assistants, including file size limits, ESLint, architecture compliance, anti-pattern scanning, and comment compliance.7 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server that analyzes codebases to provide dependency graphs, impact analysis, and file insights across 15+ programming languages, enabling AI assistants to understand project structure and navigate code efficiently.MIT
- AlicenseCqualityDmaintenanceAn MCP server that analyzes local or remote GitHub repositories, providing intelligent code context and structure to AI coding assistants.1013MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that analyzes codebases and generates contextual prompts, making it easier for AI assistants to understand and work with code repositories.18MIT
TDQS
B3.4/5.0
Scored across 9 tools
Disambiguation4/5
Most tools target a distinct static-analysis concern (line counts, complexity, smells, dead code), and the descriptions clarify their purpose with filters and detail options. There is slight overlap between get_functions and get_code_inventory, and between line-count reporting and threshold checking, but an agent can usually disambiguate with context.
Naming Consistency4/5
Tool names consistently use lowercase snake_case and mostly follow a get_<noun> pattern such as get_line_counts and get_complexity_metrics. The deviations check_thresholds and find_dead_code still use clear verb_noun naming, so the overall pattern remains predictable.
Tool Count5/5
Nine tools is a well-scoped size for a code-analysis MCP server. Each tool covers a distinct inspection area without unnecessary redundancy or bloat.
Completeness4/5
The tool set covers the major static-analysis workflows: size, structure, functions, complexity, code smells, documentation coverage, prop drilling, and dead code. A minor possible gap is dependency or import-level analysis, but the surface appears largely complete for its stated scope.
Maintenance
ActivityActive
ResponsivenessNo issues