Skip to main content
Glama
Sign In
CRAP Score MCP

CRAP Score MCP

by paulboutin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to CRAP Score MCP

No user-submitted related servers found.

    Related Servers

    • code-health-mcp

      nagavitalp
      A
      license
      A
      quality
      D
      maintenance
      Provides comprehensive code quality analysis with quantitative metrics, historical trends, and refactoring risk prediction for C#, Python, and TypeScript codebases.
      5
      12 npm
      MIT

    • 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

    • readyorai

      TedoNeObichaJavaScript
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables local code inspection and analysis for clean code practices, best practices, and actionable recommendations without external API calls or modifying the code.
      82 npm
      1
      MIT

    • butter-code-health

      CodingButter
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to analyze code health in TypeScript/JavaScript projects, providing tools to run analysis, start a dashboard, and get summaries.
      8 npm
      3
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3/5.0

    Scored across 4 tools

    Disambiguation4/5

    The tools target distinct levels of the domain: single-function analysis, repository hotspot ranking, full repository reporting, and change-session review. There is some conceptual overlap between hotspot findings and the full report, but the descriptions make the scope difference clear enough to avoid most misselection.

    Naming Consistency5/5

    All tool names use snake_case with a clear verb_noun pattern: analyze_function_health, scan_repository_hotspots, get_repository_report, review_changes. The conventions are predictable and consistent throughout.

    Tool Count5/5

    Four tools are well-scoped for a CRAP score/code-health server. Each tool maps to a distinct workflow step, and there are no redundant or filler tools.

    Completeness4/5

    The surface covers core workflows: scanning repository hotspots, reporting assessed functions, inspecting a specific function, and reviewing changes against a baseline. A few secondary operations, such as explicit scan-status or repository discovery, are not separate tools, but the main CRAP-score lifecycle is covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources