A
licenseNot graded
qualityB
maintenanceMCP server for testing assistance that scans codebases, identifies untested areas, generates and runs tests, and reports results.
Apache 2.0
fleet-of-one-mcp-server
Related Servers
Alternatives to fleet-of-one-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for security bug-finding that proves every finding by running exploits, enabling agents to verify changes and find bugs with execution-based evidence.9Apache 2.0
- AlicenseNot gradedqualityCmaintenanceMCP server that extracts and links code, tasks, documentation, and git history into a graph, then diagnoses discrepancies and generates reports.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAutomated testing tool for MCP servers that checks protocol conformance, tool quality, and reliability, providing a scorecard with spec citations and non-zero exit codes for CI.12 npmMIT
- AlicenseAqualityAmaintenanceAn MCP server that enforces disciplined Git workflows by planning coding tasks into small, test-gated commits, ensuring tests pass before staging and preventing out-of-scope or oversized changes.46 npm1MIT
- AlicenseCqualityDmaintenanceAn MCP server that guides QA and verification processes by breaking down tasks into manageable steps and providing LLM-driven, confidence-scored tool recommendations.112 npm6MIT
TDQS
A4.4/5.0
Scored across 2 tools
Disambiguation5/5
verify_done and check_repro serve entirely distinct purposes: one validates success (tests pass and changes made), while the other validates expected failure (reproduction of a bug). No overlap or confusion between them.
Naming Consistency5/5
Both tool names follow the same verb_noun pattern with lowercase and underscores: verify_done and check_repro. The naming is consistent and predictable.
Tool Count3/5
At 2 tools, the set is on the borderline of feeling thin, but it is acceptable for its narrow verification-focused domain. The tools cover the two primary verification gates without being excessive.
Completeness4/5
The two tools cover the core verification lifecycle: confirming task completion and confirming bug reproduction. Minor gaps exist, such as verifying partial changes or checking for regressions, but these are workable for the stated purpose.
Maintenance
ActivityStale
ResponsivenessNo issues