Skip to main content
Glama
nagavitalp

code-health-mcp

by nagavitalp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to code-health-mcp

No user-submitted related servers found.

    Related Servers

    • CodeBase Optimizer

      liadgez
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides comprehensive codebase analysis including project structure evaluation, cross-language duplicate detection, microservices validation, and configuration optimization with AI-powered pattern learning that generates actionable improvement reports.
      MIT

    • DependencyMCP Server

      mkearl
      A
      license
      A
      quality
      D
      maintenance
      Analyzes codebases to generate dependency graphs and architectural insights across multiple programming languages, helping developers understand code structure and validate against architectural rules.
      6
      28 npm
      20
      MIT

    • Smart Code Reviewer

      renjismzy
      A
      license
      A
      quality
      D
      maintenance
      Enables comprehensive code analysis including quality assessment, security vulnerability detection, refactoring suggestions, complexity calculations, and automatic documentation generation for multiple programming languages.
      5
      7 npm
      MIT

    • ward

      user31133
      F
      license
      Not graded
      quality
      D
      maintenance
      AI-powered code quality analysis that detects security issues, bugs, code smells, and performance problems across multiple languages.
      4
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct dimension of code health: single-file analysis, repository-wide analysis, historical trends, risk prediction, and dependency structure. There is no overlapping purpose or ambiguity between these five tools.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (analyze_file, analyze_repository, get_complexity_trends, predict_refactor_risk, get_dependency_graph). This makes the toolset highly predictable and easy to navigate.

    Tool Count5/5

    Five tools is well-scoped for a focused code health analysis server. Each tool covers a meaningful capability without redundancy or bloat, and the number is within the ideal 3–15 range.

    Completeness5/5

    The toolset covers the full analysis lifecycle: targeted file inspection, whole-repository analysis, historical trends, forward-looking risk prediction, and dependency coupling. For a read-only analysis domain, there are no obvious missing operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources