codebase-doctor
Related Servers
Alternatives to codebase-doctor
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceLocal-first security check for AI coding agents — finds hardcoded secrets, exposed .env files, git-history leaks and vulnerable dependencies (OSV), entirely on your machine. Ask your agent "is this safe to ship?" and get a Launch Readiness score with a fix for every finding.MIT
- AlicenseAqualityAmaintenanceLocal, deterministic review of Git changes for coding agents: weakened tests and CI gates, security-boundary changes, input-to-sink flows, and blast radius. Runs the RepoPilot Rust CLI over stdio; no source leaves the machine and no model is called.6611 npm23Apache 2.0
- AlicenseNot gradedqualityBmaintenanceLocal code-graph engine for AI coding workflows: static analysis of Rust, Cangjie, ArkTS, TypeScript/JavaScript, C/C++, Python, and Shell projects into symbols, imports, call graphs, and quality gates, with pre-commit change review and impact analysis. Read-only by design — never executes build scripts or uploads code.61MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to interrogate a local repository deterministically for symbols, dependencies, call paths, routes, tests, and Git impact, returning verified structured evidence with exact line citations instead of requiring the whole codebase to be read.3MIT
- AlicenseNot gradedqualityCmaintenanceExposes repository reconnaissance tools — file listing and verbatim reading, regex search, dependency-tree parsing across Python/Node/Rust/Go, and test-coverage ingestion — so agents can gather line-numbered evidence from real source files. This lets an audit pipeline physically re-verify every claim and drop findings that cannot be located in the code.MIT
- AlicenseNot gradedqualityCmaintenanceLive codebase intelligence for AI agents. Import graph PageRank for file importance, git forensics for co-change coupling and fragile code, convention detection across 16 domains, and blast radius analysis.47 npm3Business Source 1.1
TDQS
Scored across 4 tools
Each tool has a fairly distinct purpose: audit_codebase runs the full audit, verify_changes compares fingerprints against a baseline, explain_finding drills into one finding, and describe_capabilities is meta. The only mild overlap is that audit_codebase and verify_changes both execute a read-only audit, but their descriptions make the baseline-vs-verification distinction clear.
All four tools follow a clean verb_noun snake_case pattern (audit_codebase, describe_capabilities, verify_changes, explain_finding), with no mixed conventions or vague verbs.
Four tools is a tightly scoped, coherent set for a read-only audit workflow (run, explain, verify, describe). It is on the lean side but each tool earns its place, so it lands slightly below ideal breadth rather than being bloated.
The surface covers the core audit lifecycle: run an audit, inspect individual findings, verify repairs, and introspect the server's capabilities. A dedicated findings-listing tool is absent, but findings are surfaced through the report and explain_finding, so agents can work around it; read-only design legitimately omits write operations.