Vision Driven Design MCP server — 15 tools for bi-directional traceability across an 8-phase, spec-driven development chain (Vision → Strategy → Tactics → Spec → Plan → Tasks) with 7 quality gates.
Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
start_vdd_projectRun the VDD chain from a vision statement to a test-first task list, gate by gate.Run the VDD chain from a vision statement to a test-first task list, gate by gate.
No input schema was published for this tool.
visionFreeform 1-3 paragraph vision: who it is for, the change you want, how you will measure it.Freeform 1-3 paragraph vision: who it is for, the change you want, how you will measure it.
No input schema was published for this tool.
projectRootProject root to write constitution.md and vdd/ into (default ".").Project root to write constitution.md and vdd/ into (default ".").
No input schema was published for this tool.
implement_next_taskPick the next uncompleted task for a feature, implement it test-first, and keep traceability.Pick the next uncompleted task for a feature, implement it test-first, and keep traceability.
No input schema was published for this tool.
featureSpec directory name under vdd/specs/ (kebab-case).Spec directory name under vdd/specs/ (kebab-case).
No input schema was published for this tool.
change_requirementCascade a requirement change down the V→S→T→SP→PL→TK chain and re-run the affected gates.Cascade a requirement change down the V→S→T→SP→PL→TK chain and re-run the affected gates.
No input schema was published for this tool.
changeThe requirement change, in plain language.The requirement change, in plain language.
No input schema was published for this tool.
vddNo description publishedThis tool published no description. Forge does not invent one.
7 of 8 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Vision Driven Design MCP server — 15 tools for bi-directional traceability across an 8-phase, spec-driven development chain (Vision → Strategy → Tactics → Spec → Plan → Tasks) with 7 quality gates.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.