plimsoll
Related Servers
Alternatives to plimsoll
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceA local, read-only MCP server that provides AI coding agents with structural evidence about a repository, including dependency analysis and impact assessment, while naming the boundary of every answer without any LLM calls.15 npmApache 2.0- AlicenseAqualityCmaintenanceMCP server for git archaeology — churn hotspots, blame summaries, bus factor, commit forensics and file history over any local repository.113MIT
- AlicenseNot gradedqualityCmaintenanceMCP 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.4 npm2MIT
- AlicenseNot gradedqualityDmaintenanceA read-only MCP server for AI coding agents to inspect repositories, audit code quality, route engineering skills, and plan safe issue/PR workflows.1MIT
- FlicenseNot gradedqualityDmaintenanceLocal MCP server for static Python/TypeScript code audits, Playwright test generation, and SDLC health checks with a 0-100 quality score.-
- AlicenseBqualityDmaintenanceRead-only MCP server that exposes SonarQube Web API tools for issue retrieval, quality gate status, and source context, enabling coding agents to fix code issues.8203 npm1MIT
TDQS
Scored across 3 tools
explain (single-mark evidence drill-down), report (full repository report), and status (delta digest since base) each target a different granularity, and the descriptions make the distinction reasonably clear. The main risk is report vs status, since status returns a capped subset of what report already contains, which could cause an agent to pick the wrong one for a full picture.
All three names are single lowercase words in the same style: explain, report, status. There is no mixing of conventions or verb styles, so the naming is predictable even if it isn't a verb_noun pattern.
Three tools map cleanly onto three views (detail, full, delta) of the same analysis, so each earns its place. It is on the lean side for a measurement/reporting server, but not thin enough to be a mismatch.
The read surface is coherent (run a report, get a delta summary, verify a single mark), but there is no way to manage the baseline itself, list repositories, or acknowledge standing debt items even though report and status reference acknowledged items. These are notable gaps an agent would hit when trying to act on the findings rather than just read them.