conductor-sdd
Related Servers
Alternatives to conductor-sdd
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceLocal MCP server for AI agents and vibe coding safety: deterministic risk checks (payments, auth, database, secrets, infrastructure), sessions, checkpoints, policy inspection, and fix prompts. Runs over stdio against a local git repository; no language model judges risk.8Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables IDE agents to audit repositories for MCP supply-chain and secret-leak risks, simulate >200K-token cost-cliff exposure, and verify A2A agent cards over JSON-RPC stdio.Apache 2.0
- FlicenseNot gradedqualityNot gradedmaintenanceEnables agents and MCP-compliant clients to run multi-language code in a deterministic, zero-dependency sandbox where AST security analysis blocks dangerous syscalls and isolated execution telemetry is captured. It exposes this through JSON-RPC 2.0 stdio, letting frameworks like LangGraph, CrewAI, Cursor, and Claude Desktop validate and execute agent-generated code safely.-
- AlicenseNot gradedqualityBmaintenanceLocal-first code intelligence and safety layer for AI coding agents. MCP server exposes dependency graph, impact analysis, and AST-compressed repo context, backed by typed local memory, patch-scope safety gates, and git-independent transaction rollback.1MIT
- AlicenseNot gradedqualityCmaintenanceLocal-first MCP server that provides project context, verification gates, and structured tools for coding agents to discover knowledge, run diagnostics, and execute allowlisted commands within a repository.40 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables developers to audit local MCP server code for prompt injection surfaces, unconstrained shell execution, hardcoded secrets, and JSON-RPC schema issues, and to fuzz system prompts against jailbreak payloads. It also generates Shields.io-compatible verification badges for embedding in repository READMEs.73 npmApache 2.0
TDQS
Scored across 5 tools
Each tool targets a clearly distinct phase of the spec-driven development lifecycle: validate, lock, drift verification, checkpoint creation, and rollback. Actions are semantically different (schema validation vs. hashing vs. comparison vs. snapshotting vs. restoration), so misselection is unlikely.
All tool names share the conductor_ prefix followed by a predictable verb_noun pattern (validate_spec, lock_baseline, verify_drift, create_checkpoint, rollback). The lone nounless 'rollback' is a minor deviation but remains clear and consistent with the set.
Five tools is a tight, well-scoped set that maps directly to the workflow: validate → lock → verify → checkpoint → rollback. No redundant or filler tools; each earns its place.
The surface covers the core safety loop for spec-driven coding, including validation, baseline locking, drift detection, and rollback. Minor gaps exist, such as listing/inspecting existing checkpoints or modifying the spec itself, which agents would have to work around.