# @simonmak-ascent/mcp

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.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.9.2
- **Author:** simonmak-ascent
- **License:** MIT
- **npm:** @simonmak-ascent/mcp
- **Endpoints:** streamable-http https://vdd.simonmak.com/api/mcp
- **Source:** https://github.com/simonmak-ascent/vision-driven-design
- **Endpoint health:** reachable (last checked 2026-10-04T19:35:02.536Z, 1 sample) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-04T19:34:36.576Z
- **Version scanned:** 1.9.2
- **CVEs:** none found by OSV at scan time

## Tools

8 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `start_vdd_project` — Run the VDD chain from a vision statement to a test-first task list, gate by gate.
- `vision` — Freeform 1-3 paragraph vision: who it is for, the change you want, how you will measure it.
- `projectRoot` — Project root to write constitution.md and vdd/ into (default ".").
- `implement_next_task` — Pick the next uncompleted task for a feature, implement it test-first, and keep traceability.
- `feature` — Spec directory name under vdd/specs/ (kebab-case).
- `change_requirement` — Cascade a requirement change down the V→S→T→SP→PL→TK chain and re-run the affected gates.
- `change` — The requirement change, in plain language.
- `vdd`

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@simonmak-ascent/mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs locally and hosted; read-only tool surface.
- Floor 16, ceiling 34 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40simonmak-ascent%2Fmcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40simonmak-ascent%2Fmcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40simonmak-ascent%2Fmcp
- HTML page: https://forgeregistry.com/registry/%40simonmak-ascent%2Fmcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.