# Vision Driven Design (VDD) MCP Server (remote · vdd.simonmak.com)

Spec-driven development MCP server: 8 phases, bi-directional traceability, 7 quality gates.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `vdd.simonmak.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/simonplmak-cloud-vision-driven-design/api-mcp.md), [page](https://verifymcp.io/servers/simonplmak-cloud-vision-driven-design/api-mcp)

## Channel facts

- Endpoint: `https://vdd.simonmak.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.8.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (vdd_init).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4755 tokens (~317/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Vision Driven Design (VDD) MCP Server server?

Vision Driven Design (VDD) MCP Server is a hosted endpoint at https://vdd.simonmak.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http simonplmak-cloud-vision-driven-design 'https://vdd.simonmak.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "simonplmak-cloud-vision-driven-design": {
      "url": "https://vdd.simonmak.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "simonplmak-cloud-vision-driven-design": {
      "type": "http",
      "url": "https://vdd.simonmak.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.simonplmak-cloud-vision-driven-design]
url = "https://vdd.simonmak.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "simonplmak-cloud-vision-driven-design": {
      "type": "remote",
      "url": "https://vdd.simonmak.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add simonplmak-cloud-vision-driven-design --url 'https://vdd.simonmak.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  simonplmak-cloud-vision-driven-design:
    url: "https://vdd.simonmak.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "simonplmak-cloud-vision-driven-design": {
      "Transport": "http",
      "Url": "https://vdd.simonmak.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add simonplmak-cloud-vision-driven-design -t streamable-http -u 'https://vdd.simonmak.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "simonplmak-cloud-vision-driven-design": {
      "type": "http",
      "url": "https://vdd.simonmak.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 62)

First indexed and scored.

## MCP tools (15)

### `vdd_init` (~292 tokens)

Initialize Constitution

VDD Phase 0: Generate constitution.md at the project root — the immutable tech stack, conventions, security constraints, naming rules, and banned patterns that every later phase obeys. Overwrites any existing constitution.md. Run this first, before vdd_vision; to change a constitution that already exists, use vdd_amend instead of re-running this. projectRoot sets the directory constitution.md is written to and that later phases resolve every vdd/ artifact against (default ".").

Input parameters:

- `actionItemId` (string): Tactical action item ID (e.g., 'A-001')
- `artifactFiles` (object): Map of artifact path → content for serverless validate/drift detection
- `availableTools` (array): MCP/tool names available to the host agent (e.g., ['brave-search','perplexity','context7','gh_grep','playwright','filesystem'])
- `capabilities` (array): Alias for availableTools
- `description` (string): Freeform description input
- `feature` (string): Feature name / spec directory name
- `projectRoot` (string): Path to project root directory
- `researchFindings` (string): Consolidated research subagent findings to synthesize into strategy.md
- `statement` (string): Freeform input (required for vision)
- `taskId` (string): Task ID to implement (e.g., 'TASK-003')

### `vdd_vision` (~318 tokens)

Expand Vision

VDD Phase 1: Expand a freeform vision statement into vdd/vision.md — Impact Model (Goal, Actors, Impacts), Stakeholder Map, Success Metrics (leading + lagging), Constraints & Boundaries, and Target Domains. Overwrites any existing vdd/vision.md. Requires statement (freeform 1-3 paragraph intent, not a title) and a prior vdd_init. Run once, after vdd_init and before vdd_strategize; to revise a vision once downstream artifacts exist, use vdd_amend so the change cascades instead of re-running this.

Input parameters:

- `actionItemId` (string): Tactical action item ID (e.g., 'A-001')
- `artifactFiles` (object): Map of artifact path → content for serverless validate/drift detection
- `availableTools` (array): MCP/tool names available to the host agent (e.g., ['brave-search','perplexity','context7','gh_grep','playwright','filesystem'])
- `capabilities` (array): Alias for availableTools
- `description` (string): Freeform description input
- `feature` (string): Feature name / spec directory name
- `projectRoot` (string): Path to project root directory
- `researchFindings` (string): Consolidated research subagent findings to synthesize into strategy.md
- `statement` (string): Freeform input (required for vision)
- `taskId` (string): Task ID to implement (e.g., 'TASK-003')

### `vdd_strategize` (~314 tokens)

Research Strategy

VDD Phase 2: Produce research-backed strategy into vdd/strategy.md — strategic pillars, competitive analysis, and a risk register, resolved from the vision target-domain primers. Overwrites vdd/strategy.md. Requires vdd/vision.md; run after vdd_vision and before vdd_tactics. Two-pass: call once with availableTools to get the research-subagent dispatch specs, then re-call with researchFindings to synthesize strategy.md (a first call with neither returns only the dispatch specs). To change strategy after artifacts exist, use vdd_amend.

Input parameters:

- `actionItemId` (string): Tactical action item ID (e.g., 'A-001')
- `artifactFiles` (object): Map of artifact path → content for serverless validate/drift detection
- `availableTools` (array): MCP/tool names available to the host agent (e.g., ['brave-search','perplexity','context7','gh_grep','playwright','filesystem'])
- `capabilities` (array): Alias for availableTools
- `description` (string): Freeform description input
- `feature` (string): Feature name / spec directory name
- `projectRoot` (string): Path to project root directory
- `researchFindings` (string): Consolidated research subagent findings to synthesize into strategy.md
- `statement` (string): Freeform input (required for vision)
- `taskId` (string): Task ID to implement (e.g., 'TASK-003')

### `vdd_tactics` (~306 tokens)

Audit Tactics

VDD Phase 3: Audit the existing codebase into vdd/tactics.md — repo audit, technical-debt assessment, gap analysis, MoSCoW-prioritized action items (A-001, A-002, …), dependency map, and infrastructure requirements. Overwrites vdd/tactics.md. Requires vdd/strategy.md; run after vdd_strategize and before vdd_specify. Needs a filesystem-capable host to scan the repo, so check with vdd_detect_environment first if the host may lack one.

Input parameters:

- `actionItemId` (string): Tactical action item ID (e.g., 'A-001')
- `artifactFiles` (object): Map of artifact path → content for serverless validate/drift detection
- `availableTools` (array): MCP/tool names available to the host agent (e.g., ['brave-search','perplexity','context7','gh_grep','playwright','filesystem'])
- `capabilities` (array): Alias for availableTools
- `description` (string): Freeform description input
- `feature` (string): Feature name / spec directory name
- `projectRoot` (string): Path to project root directory
- `researchFindings` (string): Consolidated research subagent findings to synthesize into strategy.md
- `statement` (string): Freeform input (required for vision)
- `taskId` (string): Task ID to implement (e.g., 'TASK-003')

### `vdd_specify` (~312 tokens)

Generate Spec

VDD Phase 4: Generate vdd/specs/<id>/spec.md for one tactical action item — user stories, Always/Ask/Never boundaries, Given/When/Then acceptance criteria (AC), MoSCoW priorities, non-functional requirements, and impact verification. Overwrites the spec file. Pass actionItemId (e.g. "A-001") or a freeform description to skip the V/S/T chain. Use for a NEW spec; to resolve leftover [NEEDS CLARIFICATION] markers in an existing spec use vdd_clarify instead.

Input parameters:

- `actionItemId` (string): Tactical action item ID (e.g., 'A-001')
- `artifactFiles` (object): Map of artifact path → content for serverless validate/drift detection
- `availableTools` (array): MCP/tool names available to the host agent (e.g., ['brave-search','perplexity','context7','gh_grep','playwright','filesystem'])
- `capabilities` (array): Alias for availableTools
- `description` (string): Freeform description input
- `feature` (string): Feature name / spec directory name
- `projectRoot` (string): Path to project root directory
- `researchFindings` (string): Consolidated research subagent findings to synthesize into strategy.md
- `statement` (string): Freeform input (required for vision)
- `taskId` (string): Task ID to implement (e.g., 'TASK-003')

### `vdd_clarify` (~313 tokens)

Clarify Spec

VDD Phase 4b: Clarify an existing spec — scans vdd/specs/<feature>/spec.md and returns the items to resolve: every [NEEDS CLARIFICATION] marker, [e.g.] placeholder, and happy-path acceptance criterion (AC) still needing an edge-case counterpart (AC-E*). Read-only; returns the list without editing the file (the host agent then applies the resolutions). Pass feature (spec directory name). Run after vdd_specify when a spec has unresolved markers; to author a brand-new spec use vdd_specify instead.

Input parameters:

- `actionItemId` (string): Tactical action item ID (e.g., 'A-001')
- `artifactFiles` (object): Map of artifact path → content for serverless validate/drift detection
- `availableTools` (array): MCP/tool names available to the host agent (e.g., ['brave-search','perplexity','context7','gh_grep','playwright','filesystem'])
- `capabilities` (array): Alias for availableTools
- `description` (string): Freeform description input
- `feature` (string): Feature name / spec directory name
- `projectRoot` (string): Path to project root directory
- `researchFindings` (string): Consolidated research subagent findings to synthesize into strategy.md
- `statement` (string): Freeform input (required for vision)
- `taskId` (string): Task ID to implement (e.g., 'TASK-003')

### `vdd_plan` (~294 tokens)

Generate Plan

VDD Phase 5: Generate the technical blueprint under vdd/specs/<feature>/ — plan.md (component breakdown, AC coverage map, technology choices, verification toolchain), data-model.md (entities, indexes, migrations), and contracts/ (request/response/error schemas). Overwrites these files. Requires an existing spec for the feature; run after vdd_specify or vdd_clarify and before vdd_tasks — if no spec exists yet, run vdd_specify first.

Input parameters:

- `actionItemId` (string): Tactical action item ID (e.g., 'A-001')
- `artifactFiles` (object): Map of artifact path → content for serverless validate/drift detection
- `availableTools` (array): MCP/tool names available to the host agent (e.g., ['brave-search','perplexity','context7','gh_grep','playwright','filesystem'])
- `capabilities` (array): Alias for availableTools
- `description` (string): Freeform description input
- `feature` (string): Feature name / spec directory name
- `projectRoot` (string): Path to project root directory
- `researchFindings` (string): Consolidated research subagent findings to synthesize into strategy.md
- `statement` (string): Freeform input (required for vision)
- `taskId` (string): Task ID to implement (e.g., 'TASK-003')

### `vdd_tasks` (~284 tokens)

Generate Tasks

VDD Phase 6: Break the plan into atomic test-first tasks in vdd/specs/<feature>/tasks.md — each references acceptance criteria (AC) and contracts, is sized S/M/L, and is marked [P] when parallelizable. Overwrites tasks.md. Requires plan.md; run after vdd_plan. To fetch the next uncompleted task from an existing tasks.md use vdd_get_next_task instead of re-running this.

Input parameters:

- `actionItemId` (string): Tactical action item ID (e.g., 'A-001')
- `artifactFiles` (object): Map of artifact path → content for serverless validate/drift detection
- `availableTools` (array): MCP/tool names available to the host agent (e.g., ['brave-search','perplexity','context7','gh_grep','playwright','filesystem'])
- `capabilities` (array): Alias for availableTools
- `description` (string): Freeform description input
- `feature` (string): Feature name / spec directory name
- `projectRoot` (string): Path to project root directory
- `researchFindings` (string): Consolidated research subagent findings to synthesize into strategy.md
- `statement` (string): Freeform input (required for vision)
- `taskId` (string): Task ID to implement (e.g., 'TASK-003')

### `vdd_get_next_task` (~278 tokens)

Get Next Task

VDD Phase 7a: Read vdd/specs/<feature>/tasks.md and return the next uncompleted task (or a completion marker when none remain). Read-only; never edits tasks.md. Pass feature (the exact spec directory name). Use before each implementation session to keep context isolated; to regenerate the whole list use vdd_tasks, and to execute the returned task use vdd_implement.

Input parameters:

- `actionItemId` (string): Tactical action item ID (e.g., 'A-001')
- `artifactFiles` (object): Map of artifact path → content for serverless validate/drift detection
- `availableTools` (array): MCP/tool names available to the host agent (e.g., ['brave-search','perplexity','context7','gh_grep','playwright','filesystem'])
- `capabilities` (array): Alias for availableTools
- `description` (string): Freeform description input
- `feature` (string): Feature name / spec directory name
- `projectRoot` (string): Path to project root directory
- `researchFindings` (string): Consolidated research subagent findings to synthesize into strategy.md
- `statement` (string): Freeform input (required for vision)
- `taskId` (string): Task ID to implement (e.g., 'TASK-003')

### `vdd_implement` (~302 tokens)

Implement Task

VDD Phase 7b: Prepare one task for implementation — loads constitution, spec, plan, and contracts and returns the implementation instruction plus the impact-chain commit-message format. Read-only; the tool writes nothing — the host agent performs the code edits, verification, and commit. Pass taskId (e.g. "TASK-003") from the task returned by vdd_get_next_task. Run one task at a time, after vdd_get_next_task; for read-only inspection of tasks use vdd_get_next_task instead.

Input parameters:

- `actionItemId` (string): Tactical action item ID (e.g., 'A-001')
- `artifactFiles` (object): Map of artifact path → content for serverless validate/drift detection
- `availableTools` (array): MCP/tool names available to the host agent (e.g., ['brave-search','perplexity','context7','gh_grep','playwright','filesystem'])
- `capabilities` (array): Alias for availableTools
- `description` (string): Freeform description input
- `feature` (string): Feature name / spec directory name
- `projectRoot` (string): Path to project root directory
- `researchFindings` (string): Consolidated research subagent findings to synthesize into strategy.md
- `statement` (string): Freeform input (required for vision)
- `taskId` (string): Task ID to implement (e.g., 'TASK-003')

### `vdd_validate` (~313 tokens)

Validate Impact

VDD Phase 8: Validate the full chain — bidirectional traceability matrix, drift detection, orphan detection, uncovered vision goals, impact metrics vs targets, and 28 S&T assumption checks across 7 gates. Writes vdd/impact-report.generated.md and never overwrites a hand-authored vdd/impact-report.md. Run after implementation is complete; for a lightweight per-feature consistency check or the project-wide matrix use vdd_inspect. artifactFiles maps artifact path→content for serverless runs where the tool cannot read the filesystem — omit it when running locally against projectRoot.

Input parameters:

- `actionItemId` (string): Tactical action item ID (e.g., 'A-001')
- `artifactFiles` (object): Map of artifact path → content for serverless validate/drift detection
- `availableTools` (array): MCP/tool names available to the host agent (e.g., ['brave-search','perplexity','context7','gh_grep','playwright','filesystem'])
- `capabilities` (array): Alias for availableTools
- `description` (string): Freeform description input
- `feature` (string): Feature name / spec directory name
- `projectRoot` (string): Path to project root directory
- `researchFindings` (string): Consolidated research subagent findings to synthesize into strategy.md
- `statement` (string): Freeform input (required for vision)
- `taskId` (string): Task ID to implement (e.g., 'TASK-003')

### `vdd_inspect` (~323 tokens)

Inspect Project

VDD Cross-phase: Read-only inspection of the current project in one call — scope selects the view. scope="project" (default) returns the bidirectional V→S→T→SP→PL→TK traceability matrix across all vdd/ artifacts; scope="feature" returns per-feature spec metrics (acceptance-criteria count, unresolved [NEEDS CLARIFICATION] markers, [e.g.] placeholder density, and whether plan.md/tasks.md exist). Never modifies files. Pass feature for the feature scope; for release-readiness validation with gates use vdd_validate, and to author a spec use vdd_specify.

Input parameters:

- `actionItemId` (string): Tactical action item ID (e.g., 'A-001')
- `artifactFiles` (object): Map of artifact path → content for serverless validate/drift detection
- `availableTools` (array): MCP/tool names available to the host agent (e.g., ['brave-search','perplexity','context7','gh_grep','playwright','filesystem'])
- `capabilities` (array): Alias for availableTools
- `description` (string): Freeform description input
- `feature` (string): Feature name / spec directory name
- `projectRoot` (string): Path to project root directory
- `researchFindings` (string): Consolidated research subagent findings to synthesize into strategy.md
- `statement` (string): Freeform input (required for vision)
- `taskId` (string): Task ID to implement (e.g., 'TASK-003')

### `vdd_amend` (~305 tokens)

Amend Requirements

VDD Cross-phase: Plan a requirement-change cascade through the whole chain — identifies the highest affected level and returns the ordered steps to update downward V→S→T→SP→PL→TK and re-run affected gates (G1–G7). Read-only; returns the cascade plan without editing artifacts (the host agent applies the edits and commits). Pass the change as description. Use when a requirement changes after artifacts already exist; to build a phase from scratch the first time, run that phase's own tool instead of vdd_amend.

Input parameters:

- `actionItemId` (string): Tactical action item ID (e.g., 'A-001')
- `artifactFiles` (object): Map of artifact path → content for serverless validate/drift detection
- `availableTools` (array): MCP/tool names available to the host agent (e.g., ['brave-search','perplexity','context7','gh_grep','playwright','filesystem'])
- `capabilities` (array): Alias for availableTools
- `description` (string): Freeform description input
- `feature` (string): Feature name / spec directory name
- `projectRoot` (string): Path to project root directory
- `researchFindings` (string): Consolidated research subagent findings to synthesize into strategy.md
- `statement` (string): Freeform input (required for vision)
- `taskId` (string): Task ID to implement (e.g., 'TASK-003')

### `vdd_clone` (~338 tokens)

Clone Website

Crawl and capture a target domain into a clone dataset + manifest — WordPress-aware schema inference, Payload collections, and a Next.js + Payload + Postgres scaffold manifest (vdd/clone-manifest.json). Writes vdd/clone-dataset.json, vdd/clone-manifest.json, and vdd/clone.md. Pass the domain as description; tune maxPages, timeoutMs, concurrency, crawl, browser, and refresh (set refresh=true to bypass a cached dataset and re-crawl). Open-world: makes network requests to the target site. Use for cloning an external site; it is not part of the VDD phase pipeline, so for the normal init→validate flow call those phase tools instead.

Input parameters:

- `actionItemId` (string): Tactical action item ID (e.g., 'A-001')
- `artifactFiles` (object): Map of artifact path → content for serverless validate/drift detection
- `availableTools` (array): MCP/tool names available to the host agent (e.g., ['brave-search','perplexity','context7','gh_grep','playwright','filesystem'])
- `capabilities` (array): Alias for availableTools
- `description` (string): Freeform description input
- `feature` (string): Feature name / spec directory name
- `projectRoot` (string): Path to project root directory
- `researchFindings` (string): Consolidated research subagent findings to synthesize into strategy.md
- `statement` (string): Freeform input (required for vision)
- `taskId` (string): Task ID to implement (e.g., 'TASK-003')

### `vdd_detect_environment` (~330 tokens)

Detect Environment

VDD Environment Detection: Report which tools/MCPs each VDD phase requires vs treats as optional — across the 8-phase pipeline (init through validate) plus the cross-phase helpers (amend, clone, inspect, get-next-task) — and which of the host agent availableTools are present vs missing. Read-only; returns a capability report without modifying files. Run before vdd_strategize to plan research-subagent dispatch, or when a phase fails for lack of a tool; to inspect artifacts instead of capabilities use vdd_inspect. Pass availableTools (or its alias capabilities); omitting both returns the per-phase requirements without the present/missing comparison.

Input parameters:

- `actionItemId` (string): Tactical action item ID (e.g., 'A-001')
- `artifactFiles` (object): Map of artifact path → content for serverless validate/drift detection
- `availableTools` (array): MCP/tool names available to the host agent (e.g., ['brave-search','perplexity','context7','gh_grep','playwright','filesystem'])
- `capabilities` (array): Alias for availableTools
- `description` (string): Freeform description input
- `feature` (string): Feature name / spec directory name
- `projectRoot` (string): Path to project root directory
- `researchFindings` (string): Consolidated research subagent findings to synthesize into strategy.md
- `statement` (string): Freeform input (required for vision)
- `taskId` (string): Task ID to implement (e.g., 'TASK-003')

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/simonplmak-cloud-vision-driven-design/api-mcp#diagnostics

## Score history

- 2026-09-29: 63
- 2026-09-28: 63
- 2026-09-27: 62

## Common questions

### What is the Vision Driven Design (VDD) MCP Server server?

Vision Driven Design (VDD) MCP Server is listed in the public MCP registry as io.github.simonplmak-cloud/vision-driven-design. Spec-driven development MCP server: 8 phases, bi-directional traceability, 7 quality gates. This page covers its hosted endpoint (https://vdd.simonmak.com/api/mcp).

### Is the Vision Driven Design (VDD) MCP Server server safe to use?

Vision Driven Design (VDD) MCP Server scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Vision Driven Design (VDD) MCP Server server expose?

Vision Driven Design (VDD) MCP Server exposes 15 tools: vdd_init, vdd_vision, vdd_strategize, vdd_tactics, vdd_specify, and 10 more. Their descriptions and schemas cost roughly 4,622 tokens of context every time the server is loaded.

### Does the Vision Driven Design (VDD) MCP Server server require authentication?

No. We connected to Vision Driven Design (VDD) MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Vision Driven Design (VDD) MCP Server server still maintained?

Vision Driven Design (VDD) MCP Server is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://vdd.simonmak.com/api/mcp
- Repository: https://github.com/simonplmak-cloud/vision-driven-design
- Website: https://vdd.simonmak.com/
- Changelog RSS feed: https://verifymcp.io/servers/simonplmak-cloud-vision-driven-design/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/simonplmak-cloud-vision-driven-design/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/simonplmak-cloud-vision-driven-design/api-mcp