crapkit
Related Servers
Alternatives to crapkit
AlicenseNot gradedqualityBmaintenanceEnables access to Codacy's code quality platform through natural language, providing repository management, security analysis, pull request reviews, and local CLI-based code analysis. Supports comprehensive code quality monitoring including issues, coverage, security vulnerabilities, and technical debt assessment across organizations and repositories.391 npm63MIT- AlicenseAqualityAmaintenanceDocGuard, an official, zero-dependency Node.js MCP server (npm: docguard-cli, docguard mcp) exposing 5 read-only doc-governance tools: guard, score, explain, verify-claims, diagnose.71,567 npm1,278 PyPI30MIT
- AlicenseAqualityAmaintenanceDiffgate MCP server acts as a code review engine, enabling AI coding agents to analyze and validate code diffs before application. It enhances AI workflows by providing self-checking capabilities to optimise and secure code changes.766 npm5Apache 2.0
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for git archaeology — churn hotspots, blame summaries, bus factor, commit forensics and file history over any local repository.3MIT

repo-doctorofficial
AlicenseNot gradedqualityCmaintenanceMCP server that produces scored, evidence-cited audits of public GitHub repos via tools for fetching metadata, reading files, scanning git history, and checking hygiene.MIT- FlicenseNot gradedqualityAmaintenanceAnalyzes repositories, explains architecture, calculates change impact, and enforces guardrails for AI Agents like Claude Code, Cursor, and Codex via MCP tools.-
- AlicenseNot gradedqualityCmaintenanceAnalyzes codebases to produce structured quality health reports with risk-scored modules based on git churn, test coverage, and test-to-source mapping, acting as an MCP server for AI coding agents and a standalone CLI.MIT
- AlicenseAqualityAmaintenancePHP static analysis MCP server with 11 tools for querying 60+ code quality metrics, detecting problems (God Class, dependency cycles, SOLID violations), analyzing dependencies, identifying refactoring priorities, and mapping test coverage — all from live analysis data.112 npm90MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for persistent code exploration and diff-aware review, exposing explore and review tools to map call paths, blast radius, and generate explainable risk-scored reports.22 npm2MIT
TDQS
Scored across 12 tools
Each tool targets a distinct operation: history, gate, next item, worklist, brief, config, ratchet, trend, claims, coupling, duplicates, and runs. Even similarly named get_function_history and get_function_brief are clearly separated by context (across-run history vs edit-start packet).
All tool names follow a consistent verb_noun pattern in snake_case: get_ for single-item retrieval, list_ for enumerations, and check_ for validations. There are no mixed conventions or vague verbs.
12 tools is well within the ideal 3-15 range. Each tool covers a distinct aspect of the code-quality analysis domain (metrics, queue, config, coupling, duplicates) with no redundancy or bloat.
The surface covers all major read-only workflows: function inspection, work selection, trend analysis, gate checks, config validation, and structural analysis (coupling/duplication). Write operations like releasing claims or running tests are intentionally CLI-side, so there are no obvious gaps for the server's role.