Bi-directional traceability for AI-assisted development — prove every commit tra
Bi-directional traceability for AI-assisted development — prove every commit traces to the business goal that authorised it. 8-phase chain, 7 gates, 113 checks. MCP server at vdd.simonmak.com. Skill for Claude Code, Cursor and OpenCode.
active Production-safe Score 94/100 http no auth
At a glance
| Endpoint | https://vdd.simonmak.com/api/sse |
|---|---|
| Source | https://github.com/simonplmak-cloud/vision-driven-design |
| Transport | http |
| Tools | 15 |
| Auth | none |
| First seen | 2026-09-03 04:06:47 |
| Last checked | 2026-11-17 21:47:55 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 442 / 769 ms |
| Last successful check | 2026-11-17 21:47:55 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (15)
vdd_init— VDD Phase 0: Generate constitution.md at the project root — the immutable tech stack, conventions, security constraints, naming rules, and bvdd_vision— VDD Phase 1: Expand a freeform vision statement into vdd/vision.md — Impact Model (Goal, Actors, Impacts), Stakeholder Map, Success Metricsvdd_strategize— VDD Phase 2: Produce research-backed strategy into vdd/strategy.md — strategic pillars, competitive analysis, and a risk register, resolvedvdd_tactics— VDD Phase 3: Audit the existing codebase into vdd/tactics.md — repo audit, technical-debt assessment, gap analysis, MoSCoW-prioritized actiovdd_specify— VDD Phase 4: Generate vdd/specs/<id>/spec.md for one tactical action item — user stories, Always/Ask/Never boundaries, Given/When/Then accepvdd_clarify— VDD Phase 4b: Clarify an existing spec — scans vdd/specs/<feature>/spec.md and returns the items to resolve: every [NEEDS CLARIFICATION] marvdd_plan— VDD Phase 5: Generate the technical blueprint under vdd/specs/<feature>/ — plan.md (component breakdown, AC coverage map, technology choicesvdd_tasks— VDD Phase 6: Break the plan into atomic test-first tasks in vdd/specs/<feature>/tasks.md — each references acceptance criteria (AC) and contvdd_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; nvdd_implement— VDD Phase 7b: Prepare one task for implementation — loads constitution, spec, plan, and contracts and returns the implementation instructionvdd_validate— VDD Phase 8: Validate the full chain — bidirectional traceability matrix, drift detection, orphan detection, uncovered vision goals, impactvdd_inspect— VDD Cross-phase: Read-only inspection of the current project in one call — scope selects the view. scope="project" (default) returns the bidvdd_amend— VDD Cross-phase: Plan a requirement-change cascade through the whole chain — identifies the highest affected level and returns the ordered svdd_clone— Crawl and capture a target domain into a clone dataset + manifest — WordPress-aware schema inference, Payload collections, and a Next.js + Pvdd_detect_environment— VDD Environment Detection: Report which tools/MCPs each VDD phase requires vs treats as optional — across the 8-phase pipeline (init through
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:47:55 | ✓ | ✓ | 655 ms | 91 | active |
| 2026-11-17 21:32:49 | ✓ | ✓ | 483 ms | 91 | active |
| 2026-11-17 21:17:37 | ✓ | ✓ | 316 ms | 91 | active |
| 2026-11-17 21:02:37 | ✓ | ✓ | 277 ms | 94 | active |
| 2026-11-17 20:47:17 | ✓ | ✓ | 282 ms | 94 | active |
| 2026-11-17 20:32:13 | ✓ | ✓ | 298 ms | 94 | active |
| 2026-11-17 20:17:07 | ✓ | ✓ | 250 ms | 94 | active |
| 2026-11-17 20:01:29 | ✓ | ✓ | 327 ms | 90 | active |
| 2026-11-17 19:46:13 | ✓ | ✓ | 553 ms | 90 | active |
| 2026-11-17 19:31:08 | ✓ | ✓ | 446 ms | 91 | active |
| 2026-11-17 19:16:03 | ✓ | ✓ | 442 ms | 91 | active |
| 2026-11-17 19:00:24 | ✓ | ✓ | 312 ms | 90 | active |
| 2026-11-17 18:45:23 | ✓ | ✓ | 276 ms | 94 | active |
| 2026-11-17 18:30:20 | ✓ | ✓ | 314 ms | 90 | active |
| 2026-11-17 18:15:16 | ✓ | ✓ | 424 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://vdd.simonmak.com/api/sse") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/vdd-simonmak-com-api-sse # JSON