PxDCA - LogicMCP Server
Related Servers
Alternatives to PxDCA - LogicMCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides MCP tools for AI agents to generate deterministic pairwise/N-way test cases, analyze boundary values, build bidirectional traceability matrices, and design complete test packages from requirements.1MIT
- AlicenseDqualityDmaintenanceA deterministic MCP server that checks project code alignment with SPEC documents through static analysis without AI involvement.4MIT
- AlicenseNot gradedqualityCmaintenanceAI-powered MCP server for automotive functional safety engineering. Enables generation of HARA, FMEA, safety requirements, and compliance checks grounded in ISO 26262 standards.16MIT
- AlicenseBqualityDmaintenanceAn MCP server that gives LLM agents structured, safe, and traceable access to engineering project documentation stored in Markdown/Git repositories, enabling management of requirements, decisions, tests, tasks, and impact analysis.147 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables natural language queries on technical specifications and automated code compliance checks using local RAG with vector search, integrated via MCP.-
- AlicenseNot gradedqualityBmaintenanceProvides a local-first MCP server for AI-native software delivery, enabling structured specifications, human approval gates, controlled repository operations, verification evidence, review, and traceability.Apache 2.0
TDQS
Scored across 4 tools
Each tool targets a distinct workflow stage: requirements generation, architecture generation, audit, and skill generation. The descriptions explicitly mark each as the unique entry point for its stage, leaving no ambiguity.
All names use a consistent snake_case verb_noun pattern (generate_requirements, generate_architecture, run_audit, generate_skill). The single 'run_' verb for audit is semantically appropriate rather than inconsistent.
Four tools map cleanly onto the PxDCA pipeline stages, with each tool earning its place. The count is well-scoped and not bloated or thin for the stated purpose.
The surface covers the core lifecycle: requirements → architecture → audit, plus an optional skill generator. Minor gaps like no explicit session listing/deletion or document revision tools after completion exist, but the core workflow is complete.