Home / MCP registry index / com.ascent-partners/vision-driven-design
Vision Driven Design (VDD) MCP Server
com.ascent-partners/vision-driven-design in the official MCP registry.
Endpoint https://vdd.simonmak.com/api/mcp. Source: github.com/simonmak-ascent/vision-driven-design.
The registry describes it as: Spec-driven development MCP server: 8 phases, bi-directional traceability, 7 quality gates.
We read its 15 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
vdd_init vdd_vision vdd_strategize vdd_tactics vdd_specify vdd_clarify vdd_plan vdd_tasks vdd_get_next_task vdd_implement vdd_validate vdd_inspect vdd_amend vdd_clone vdd_detect_environment
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-ascent-partners-vision-driven-design)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.