io.github.juanklagos/sdd-mcp

NPM · @JUANKLAGOS/SDD-MCP · SCANNED AUG 7

Spec-Driven Development workflow: specs, plans, gates, status and logbook tools. Bilingual EN/ES.

Available components

+45 this week 64 64 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87

No malware found by supply-chain analysis.Pass
Known CVEs were checked across the 98 of 102 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Dependency health was assessed across the 98 of 102 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency45

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
Clear OSI-approved license (MIT).Pass
Actively maintained (last published 15 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability47

7% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 1767 tokens (~65/item across 27 items; 21 tools + 6 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management37

Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage93

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
74% of tool parameters carry a description.Partial
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Supports UI / widget rendering.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @juanklagos/sdd-mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add juanklagos-sdd-mcp -- npx -y @juanklagos/sdd-mcp

# add to Codex CLI

codex mcp add juanklagos-sdd-mcp -- npx -y @juanklagos/sdd-mcp

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "juanklagos-sdd-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@juanklagos/sdd-mcp"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add juanklagos-sdd-mcp --command npx --arg -y --arg @juanklagos/sdd-mcp

# ~/.hermes/config.yaml

mcp_servers:
  juanklagos-sdd-mcp:
    command: "npx"
    args: ["-y", "@juanklagos/sdd-mcp"]

// mcp.json

{
  "mcpServers": {
    "juanklagos-sdd-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@juanklagos/sdd-mcp"
      ]
    }
  }
}

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

6 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
5 Aug 26 0
- Security disclosure: unverified → fail ▼ functional
4 Aug 26 +4
- Security disclosure: fail → unverified ▼ functional
- Stability: unverified → 0.27 ▲ functional
2 Aug 26 +54
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Schema quality: unverified → 7 ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- First check of Capabilities: pass functional
- Licence: MIT functional
1 Aug 26 −14
- Schema quality: 7 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
31 Jul 26 −24
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
27 Jul 26 43

First indexed and scored.

Show 5 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 7 Aug 2026 · Analysed npm/@juanklagos/[email protected]

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result	No attestation
Ecosystem	npm

Dependencies 98 packages

Packages resolved	98
Deprecated	97
Stale	29
Tree resolution	Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools · 21 exposed · ~1,685 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

sdd_append_project_log Append project log entry ~54

Append content to bitacora/global/PROJECT_LOG.md.

Input Output Examples

Name	Type	Req	Description
entry	string	yes	–
projectRoot	string	yes	Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Name	Type	Req	Description
content	string	yes	–
path	string	yes	–

No examples provided.

sdd_approve_spec Approve spec ~142

Surgically fill the existing approval block of a spec.md: Estado -> Aprobado, approval date -> today, approver -> given name, evidence when provided (always wins) or when the line is empty. Fails clearly when the block is missing.

Input Output Examples

Name	Type	Req	Description
approver	string	yes	Person or role approving the spec.
evidence	string	–	Approval evidence (link or short quote); overwrites the evidence line when given.
projectRoot	string	yes	Absolute target project path. Recommended default inside this template: ./www/<project-name>.
specId	string	yes	Numbered spec folder id such as 001-my-feature.

Name	Type	Req	Description
approvalDate	string	yes	–
approver	string	yes	–
evidenceUpdated	boolean	yes	–
fieldsUpdated	array	yes	–
specId	string	yes	–
status	string	yes	–

No examples provided.

sdd_board_app Show SDD board ~84

Show the visual SDD board inside the client (MCP Apps): spec cards with approval status and task progress, board connections, the gate semaphore and dependency warnings. Read-only view; hosts without MCP Apps support get the same data as JSON text.

Input Output Examples

Name	Type	Req	Description
projectRoot	string	yes	Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Name	Type	Req	Description
board	object	yes	–
gate	object	yes	–
projectRoot	string	yes	–

No examples provided.

sdd_board_connect Connect board cards ~99

Connect two existing board cards with an optional labeled edge and persist specs/board.canvas. Idempotent for identical edges.

Input Output Examples

Name	Type	Req	Description
fromNode	string	yes	Source node id, e.g. a spec id like 001-my-feature.
label	string	–	–
projectRoot	string	yes	Absolute target project path. Recommended default inside this template: ./www/<project-name>.
toNode	string	yes	Target node id.

Name	Type	Req	Description
canvas	object	yes	–

No examples provided.

sdd_board_read Read SDD board ~63

Read the visual SDD Builder board: the specs/board.canvas layout (JSON Canvas) plus every spec with its approval status and task progress.

Input Output Examples

Name	Type	Req	Description
projectRoot	string	yes	Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Name	Type	Req	Description
canvas	object	yes	–
specs	array	yes	–

No examples provided.

sdd_board_write Write SDD board ~70

Replace the specs/board.canvas layout (JSON Canvas: nodes + edges). Only layout is stored; markdown files are never touched by this tool.

Input Output Examples

Name	Type	Req	Description
canvas	object	yes	–
projectRoot	string	yes	Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Name	Type	Req	Description
edges	number	yes	–
nodes	number	yes	–
ok	boolean	yes	–

No examples provided.

sdd_check_gate Check SDD gate ~44

Verify whether implementation can proceed under SDD rules.

Input Output Examples

Name	Type	Req	Description
projectRoot	string	yes	Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Name	Type	Req	Description
approvedSpecs	number	yes	–
errors	number	yes	–
messages	array	yes	–
ok	boolean	yes	–
totalSpecs	number	yes	–
verdict	string	yes	–
warnings	number	yes	–

No examples provided.

sdd_create_spec Create numbered spec ~59

Create the next numbered spec folder from the template.

Input Output Examples

Name	Type	Req	Description
featureName	string	yes	–
owner	string	–	–
projectRoot	string	yes	Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Name	Type	Req	Description
indexUpdated	boolean	yes	–
specDir	string	yes	–
specId	string	yes	–

No examples provided.

sdd_create_workspace Create SDD workspace ~58

Create a runnable SDD workspace inside the recommended default folder ./www/<project-name>.

Input Output Examples

Name	Type	Req	Description
assistant	string	–	–
profile	string	–	–
projectName	string	yes	–
useSpecKit	boolean	–	–

Name	Type	Req	Description
assistant	string	yes	–
layout	string	yes	–
profile	string	yes	–
projectRoot	string	yes	–
sddRoot	string	yes	–
usedSpecKit	boolean	yes	–

No examples provided.

sdd_gate_summary Gate semaphore summary ~94

One-call gate semaphore: runs the SDD gate check plus the structural validation and groups every message by the spec it belongs to (the same data the SDD Builder chip and per-card badges show). Includes advisory dependencyWarnings from the board's typed edges (approved spec depending on a not-approved one).

Input Output Examples

Name	Type	Req	Description
projectRoot	string	yes	Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Name	Type	Req	Description
approvedSpecs	number	yes	–
dependencyWarnings	array	yes	–
errors	number	yes	–
gate	object	yes	–
generalIssues	array	yes	–
ok	boolean	yes	–
specIssues	object	yes	–
totalSpecs	number	yes	–
validation	object	yes	–
verdict	string	yes	–
warnings	number	yes	–

No examples provided.

sdd_generate_roadmap Generate roadmap ~55

Generate docs/roadmap.mmd and docs/roadmap.md from specs/INDEX.md.

Input Output Examples

Name	Type	Req	Description
projectRoot	string	yes	Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Name	Type	Req	Description
markdown	string	yes	–
markdownPath	string	yes	–
mermaid	string	yes	–
mermaidPath	string	yes	–

No examples provided.

sdd_generate_status Generate status dashboard ~46

Generate STATUS.md from the current project specs and logbook.

Input Output Examples

Name	Type	Req	Description
projectRoot	string	yes	Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Name	Type	Req	Description
content	string	yes	–
path	string	yes	–

No examples provided.

sdd_list_specs List SDD specs ~42

List numbered specs and their approval status.

Input Output Examples

Name	Type	Req	Description
projectRoot	string	yes	Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Name	Type	Req	Description
specs	array	yes	–

No examples provided.

sdd_read_tasks Read spec tasks ~71

Read the checkbox tasks of a spec's tasks.md with their line numbers and done state.

Input Output Examples

Name	Type	Req	Description
projectRoot	string	yes	Absolute target project path. Recommended default inside this template: ./www/<project-name>.
specId	string	yes	Numbered spec folder id such as 001-my-feature.

Name	Type	Req	Description
specId	string	yes	–
tasks	array	yes	–

No examples provided.

sdd_record_user_consent Record user consent ~101

Record explicit user consent before implementation starts. Pass specId so the consent is bound to that spec; without it the entry is a legacy, markerless line that only covers specs approved before it.

Input Output Examples

Name	Type	Req	Description
projectRoot	string	yes	Absolute target project path. Recommended default inside this template: ./www/<project-name>.
specId	string	–	Numbered spec folder id such as 001-my-feature.
summary	string	yes	–

Name	Type	Req	Description
logFile	string	yes	–
summary	string	yes	–
timestamp	string	yes	–

No examples provided.

sdd_set_task_done Set spec task done ~107

Toggle one checkbox line in a spec's tasks.md (surgical edit, atomic write) and return the updated tasks.

Input Output Examples

Name	Type	Req	Description
done	boolean	yes	–
line	integer	yes	Zero-based line number of the task, as returned by sdd_read_tasks.
projectRoot	string	yes	Absolute target project path. Recommended default inside this template: ./www/<project-name>.
specId	string	yes	Numbered spec folder id such as 001-my-feature.

Name	Type	Req	Description
specId	string	yes	–
tasks	array	yes	–

No examples provided.

sdd_update_spec_sections Update spec sections ~222

Replace ONLY the content under the guided-editor headings of a spec.md (user story, acceptance scenarios, EARS criteria, requirements, spec properties, success criteria, out of scope — the full template) preserving everything else, the approval block included. Tolerant to the EN/ES headings of the canonical repo template (specs/_template/spec.md).

Input Output Examples

Name	Type	Req	Description
criteria	array	–	EARS acceptance criteria (bullet list).
outOfScope	string	–	Out of scope (free text).
projectRoot	string	yes	Absolute target project path. Recommended default inside this template: ./www/<project-name>.
properties	array	–	Spec properties — universal, testable properties (bullet list).
requirements	array	–	Requirements (bullet list).
scenarios	array	–	Acceptance scenarios (numbered list).
specId	string	yes	Numbered spec folder id such as 001-my-feature.
story	string	–	Main user story (free text).
successCriteria	array	–	Success criteria (bullet list).

Name	Type	Req	Description
created	array	yes	–
specId	string	yes	–
updated	array	yes	–

No examples provided.

sdd_validate Validate SDD project ~45

Validate the SDD structure and required files of a project.

Input Output Examples

Name	Type	Req	Description
projectRoot	string	yes	Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Name	Type	Req	Description
errors	number	yes	–
messages	array	yes	–
ok	boolean	yes	–
warnings	number	yes	–

No examples provided.

sdd_write_daily_log Write daily log ~68

Create or replace a daily log entry in bitacora/diaria.

Input Output Examples

Name	Type	Req	Description
content	string	yes	–
date	string	yes	Use YYYY-MM-DD.
projectRoot	string	yes	Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Name	Type	Req	Description
content	string	yes	–
path	string	yes	–

No examples provided.

sdd_write_decision Write decision ~80

Create or replace a decision file in bitacora/decisiones.

Input Output Examples

Name	Type	Req	Description
content	string	yes	–
fileName	string	yes	Use a markdown filename such as 2026-03-18-decision.md.
projectRoot	string	yes	Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Name	Type	Req	Description
content	string	yes	–
path	string	yes	–

No examples provided.

sdd_write_handoff Write handoff ~81

Create or replace a handoff file in bitacora/handoffs.

Input Output Examples

Name	Type	Req	Description
content	string	yes	–
fileName	string	yes	Use a markdown filename such as 2026-03-18-handoff.md.
projectRoot	string	yes	Absolute target project path. Recommended default inside this template: ./www/<project-name>.

Name	Type	Req	Description
content	string	yes	–
path	string	yes	–

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 7 Aug

Day	Score
27 Jul	43
28 Jul	43
30 Jul	43
31 Jul	19
1 Aug	5
2 Aug	59
3 Aug	59
4 Aug	63
5 Aug	63
6 Aug	64
7 Aug	64