debt-mcp
Related Servers
Alternatives to debt-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables scanning repositories for TODO and FIXME markers while avoiding false positives in strings and URLs, then reports each marker’s age, author, and staleness using git blame and history. It also counts suppression signals, long functions, and commented-out code inside real comments.MIT
- AlicenseNot gradedqualityBmaintenanceEnables scanning a repository for TODO, FIXME, HACK, and XXX markers, returning counts, file and line findings, severities, and git blame ages as JSON through the scan_todo_debt tool.235 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to scan codebases for TODO/FIXME/XXX patterns and get prioritized results over MCP, supporting CI gates and multiple output formats.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to scan codebases for prioritized findings (TODO, FIXME, XXX) and retrieve results in table, JSON, or SARIF format via MCP.-

modelrouteofficial
FlicenseNot gradedqualityDmaintenanceEnables AI agents to scan code for TODO, FIXME, XXX issues via MCP, providing prioritized findings in table, JSON, or SARIF format.-- AlicenseNot gradedqualityCmaintenanceEnables an agent to mine a repository's git history and answer questions a new teammate would ask: which files are riskiest based on churn, recency and author breadth, who actually knows each file based on surviving lines, which files secretly change together, which directories depend on one person, and what recent commits mean for release notes. All analysis runs through a read-only server sandboxed to a single directory.MIT
TDQS
Scored across 6 tools
Each tool occupies a fairly clear niche: list_todos (flat listing), stale_todos (liveness-split listing), debt_summary (aggregate overview), todo_history (single-marker forensics), hotspot_debt (debt×churn), and large_files_and_complexity (non-git heuristics). The main risk is list_todos vs stale_todos vs debt_summary, which all report marker counts and could be confused, though the detailed descriptions do enough to separate them.
All names are snake_case and descriptive, which keeps things readable. However, the conventions are mixed: only list_todos follows a verb_noun pattern, while the rest are noun phrases (debt_summary, todo_history, hotspot_debt) or adjective-led (stale_todos, large_files_and_complexity).
Six tools is well within the sweet spot, and each one covers a distinct analysis angle (listing, staleness, aggregation, history, churn correlation, non-git signals). No tool feels redundant or like filler.
Coverage of the debt-analysis domain is strong: detection, aging, ownership, trend, hotspots, and non-git complexity signals are all present, and the surface is read-only by design so no CRUD gaps matter. Minor gaps remain, such as diff/PR-scoped debt detection or exporting a report, but agents can work around these by combining tools.