t-rush-mcp
Related Servers
Alternatives to t-rush-mcp
No user-submitted related servers found.
Related Servers
FlicenseNot gradedqualityDmaintenanceEnables AI agents to scan code for TODO, FIXME, XXX issues via MCP, providing prioritized findings in table, JSON, or SARIF format.-- 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.-
- AlicenseAqualityBmaintenanceEnables AI coding tools to analyze projects and files for technical debt across multiple languages, calculate SQALE remediation metrics, scan dependencies, and generate prioritized recommendations through MCP tools and resources.1664 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to review code-health deltas, preview proposed changes, score files or whole projects, and get explanations of code smells through MCP tools.MIT
- AlicenseAqualityDmaintenanceScans codebases for TODO comments and exposes them as structured data to LLMs, enabling AI assistants to inspect, prioritize, and propose fixes.58 npmISC
TDQS
Scored across 6 tools
Most tools have clearly distinct purposes: find_todos ranks priorities, scan_todos_raw returns an unranked list, search_todos does fuzzy searches, resolve_todo marks completion, and get_streak_status/aggregate_debt handle stats. The main potential confusion is between find_todos and scan_todos_raw, as both scan for TODOs, though the ranking distinction helps.
All tool names use lowercase snake_case with leading verbs (find, resolve, scan, search, get, aggregate), forming a consistent pattern. Minor deviations exist: resolve_todo is singular while most others are plural, and scan_todos_raw appends 'raw' as a modifier, slightly breaking the simple verb_noun structure.
Six tools are well-scoped for a tech debt tracking server. Each tool serves a distinct aspect—scanning, ranking, searching, resolving, streak stats, and cross-repo aggregation—so the count feels appropriate without being sparse or bloated.
The tool surface covers the core lifecycle: scanning and ranking TODOs, searching for specific items, resolving them, and tracking streaks across repositories. Minor gaps exist, such as no ability to reopen a resolved TODO or add a TODO, but these are acceptable limitations for a tech debt scanner.