Obra CTO
Related Servers
Alternatives to Obra CTO
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLocal-first production-readiness MCP server for AI-built apps. It runs read-only checks, produces an evidence-based readiness score, and guides fixes before launch.115Apache 2.0
- FlicenseNot gradedqualityBmaintenanceLocal MCP server for static Python/TypeScript code audits, Playwright test generation, and SDLC health checks with a 0-100 quality score.-
- AlicenseNot gradedqualityAmaintenanceA secure, local-first MCP server for read-only inspection and troubleshooting of development environments, exposing narrow, typed, auditable capabilities for repository inspection, log summarization, Docker review, and security scanning without granting unrestricted machine access.MIT
- AlicenseNot gradedqualityBmaintenancePrivate, local-first code intelligence MCP server that builds a static graph of repositories and exposes search, architecture, impact analysis, and review tools via MCP.MIT
- AlicenseAqualityAmaintenanceAn MCP server that scans local codebases for quantum-vulnerable cryptography (secp256k1, Ed25519, RSA, etc.) and CI signing commands, classifying each finding as quantum-broken, post-quantum, or neither. It runs entirely locally with no network calls, providing a deterministic inventory for AI agents.41,732 PyPIApache 2.0
- AlicenseAqualityAmaintenanceocal-first, read-only MCP server that audits repository test architecture across ten language ecosystems. It returns deterministic evidence-backed findings, blockers, rankings, and repository-native test plans without modifying source files.19278 npmMIT
TDQS
Scored across 5 tools
Each tool has a distinct, non-overlapping purpose: scanning project signals, running tests, checking dependencies, preparing code review data, and producing the final score. Clear boundaries prevent misselection.
All tool names follow a consistent verb_noun pattern (e.g., scan_project, run_tests) using snake_case, making the set predictable and easy to navigate.
Five tools cover the full workflow of build readiness assessment without redundancy. The count is well-scoped for the domain, neither too sparse nor excessive.
The tool set covers the entire lifecycle: initial scanning, testing, vulnerability checking, in-depth code review preparation, and final scoring. No obvious gaps for its stated purpose.