code-guardian
Related Servers
Alternatives to code-guardian
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityAmaintenanceLocal repository health diagnosis and fix planning for AI-written JavaScript, TypeScript, Python and mixed projects. Its stdio MCP server exposes scans, finding explanations, repair plans, verification, privacy review and DPDP technical readiness checks.22 npm34GPL 3.0- AlicenseNot gradedqualityDmaintenanceScans codebases for TODOs, FIXMEs, code complexity, file stats, and dependencies, generating a health report with a letter grade. Zero configuration required.13 npmMIT
- AlicenseAqualityAmaintenanceScores npm packages, PyPI packages and GitHub repositories 0-100 with an A-F grade and plain-language risks. Scans package.json, requirements.txt and lock files; no API key needed.373 npm1Apache 2.0

repo-doctorofficial
AlicenseNot gradedqualityDmaintenanceMCP 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- AlicenseAqualityAmaintenanceFree deterministic security scan of a public git repository (GitHub, GitLab, Codeberg, Bitbucket): vulnerable dependencies via OSV.dev, secret patterns, and config lint, returned as structured JSON. Tools: scan_repository(url), audit_pricing(). Runs locally over stdio (python3 web/mcp_stdio.py or the Dockerfile) and is also hosted at https://project-feldspar.com/mcp. MIT licence, stdlib-only. Buil2MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents and other MCP clients to interrogate a repository — or a frontend and backend pair — returning a single JSON document of findings such as which calls reach which routes, what is dead, and where to refactor first. Exposes tools like analyze_repo, cross_repo, check_endpoint, and check_coverage, along with contract resources for authoring adapters and rule packs, entirely over local stdio with no network access.MIT
TDQS
Scored across 5 tools
Each tool has a clear role: scan grades, diff compares two scans, plan ranks fixes, orphans finds dead code, explain produces an LLM summary. The main overlap is that orphans' output is largely a specialized slice of scan's findings (acknowledged in the description as 'hygiene repeats it'), and explain is a thin wrapper over scan. Boundaries are still workable because descriptions explicitly state the input dependencies (scan feeds diff/plan/explain).
All names are single lowercase tokens with no camelCase/snake_case mixing, giving a coherent, predictable style. The only deviation is part-of-speech: scan/diff/plan/explain are verbs while 'orphans' is a noun, which slightly breaks the verb-first pattern but remains readable.
Five tools is a tight, well-scoped surface for a read-only repo analysis server, and each tool maps to a distinct workflow step (grade, compare, prioritize, detect dead code, summarize). No filler tools and no redundancy that would warrant pruning.
The analyze-and-prioritize lifecycle is covered, including before/after comparison via diff, which is the key workflow for a read-only grader. Gaps are minor: there is no way to apply or export suggested fixes, no baseline/history management, and no config or rule-selection operation, but agents can work around these by chaining scan and plan.