A
licenseA
qualityC
maintenanceEnables scanning repositories for hardcoded service URLs and clients, and building service-to-service API dependency maps.
3
3 npm
ISC
code-smell-detection-mcp
Related Servers
Alternatives to code-smell-detection-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables local code inspection and analysis for clean code practices, best practices, and actionable recommendations without external API calls or modifying the code.23 npm1MIT
- FlicenseNot gradedqualityBmaintenanceEnables static analysis of code snippets and public GitHub repositories using ruff and semgrep through a secure MCP SSE server.-
- AlicenseNot gradedqualityBmaintenanceEnables automated pull request review, security vulnerability analysis, and code quality improvement suggestions through any MCP client.466 npmMIT
- AlicenseAqualityDmaintenanceEnables comprehensive code analysis including quality assessment, security vulnerability detection, refactoring suggestions, complexity calculations, and automatic documentation generation for multiple programming languages.57 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables scanning projects for dependency vulnerabilities, secrets, license conflicts, code quality, and git health, returning a 0-100 health score with actionable suggestions.7 npmMIT
TDQS
B3.1/5.0
Scored across 13 tools
Disambiguation3/5
Some tools have clear distinctions (e.g., list vs get, by commit vs by file), but there is notable overlap between get_code_analysis_results, get_latest_pyexamine_result, and get_pyexamine_result_by_commit, as well as between get_high_severity_smells and list_smell_findings. Descriptions help clarify, but an agent could easily confuse similar query tools.
Naming Consistency2/5
Naming is inconsistent: list_metric_analyses vs get_code_analysis_results use different prefixes for list operations, and run_metric_analysis vs save_smell_analysis vs analyze_python_smells have varied verb conventions. A consistent verb_noun pattern is not maintained throughout.
Tool Count5/5
13 tools is well-scoped for a code-smell detection server, covering analysis execution, result querying, and filtering without being overwhelming. Each tool serves a distinct analytical purpose, making the count appropriate.
Completeness4/5
The tool set covers analysis execution, result storage, retrieval, and filtering across metric, smell, and code analyses. Minor gaps exist, such as no direct 'run code-analysis' tool distinct from smell analysis, but core workflows are well supported.
Maintenance
ActivityStale
ResponsivenessNo issues