Specky Sdd MCP Server

specky-sdd npm v3.13.0 Source verified

Published by paulasilvatech — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Specky — Spec-Driven Development CLI toolkit. 58 MCP tools, 13 agents, 22 prompts, 14 skills, 16 hooks. Unified `specky` CLI installs to Claude Code, GitHub Copilot, Cursor, or OpenCode on macOS, Linux, and Windows.

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 94/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

high Shell/command execution in server code (dist/cli/commands/apm.js)MTC-SRC-002

In the server's implementation (`dist/cli/commands/apm.js:12`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: spawnSync } from "node:child_process"; import { writeFileSync } from "node:fs"; import { resolve } from "node:path"; im

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/cli/commands/apm.js

high Shell/command execution in server code (dist/cli/commands/hooks.js)MTC-SRC-002

In the server's implementation (`dist/cli/commands/hooks.js:4`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: spawnSync } from "node:child_process"; import { existsSync, readdirSync } from "node:fs"; import { resolve } from "node

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/cli/commands/hooks.js

Tools 46

Each tool and what it can reach — statically extracted from the published source.

  • sdd_create_prnetwork egress
  • sdd_advance_phaseno sensitive capability
  • sdd_amendno sensitive capability
  • sdd_auto_pipelineno sensitive capability
  • sdd_batch_importno sensitive capability
  • sdd_batch_transcriptsno sensitive capability
  • sdd_check_ecosystemno sensitive capability
  • sdd_check_syncno sensitive capability
  • sdd_checklistno sensitive capability
  • sdd_checkpointno sensitive capability
Show 36 more tools ↓
  • sdd_clarifyno sensitive capability
  • sdd_compliance_checkno sensitive capability
  • sdd_context_statusno sensitive capability
  • sdd_create_branchno sensitive capability
  • sdd_cross_analyzeno sensitive capability
  • sdd_discoverno sensitive capability
  • sdd_export_work_itemsno sensitive capability
  • sdd_figma_to_specno sensitive capability
  • sdd_generate_devcontainerno sensitive capability
  • sdd_generate_dockerfileno sensitive capability
  • sdd_generate_iacno sensitive capability
  • sdd_generate_pbtno sensitive capability
  • sdd_generate_testsno sensitive capability
  • sdd_get_statusno sensitive capability
  • sdd_get_templateno sensitive capability
  • sdd_implementno sensitive capability
  • sdd_import_documentno sensitive capability
  • sdd_import_transcriptno sensitive capability
  • sdd_initno sensitive capability
  • sdd_list_checkpointsno sensitive capability
  • sdd_metricsno sensitive capability
  • sdd_model_routingno sensitive capability
  • sdd_researchno sensitive capability
  • sdd_restoreno sensitive capability
  • sdd_run_analysisno sensitive capability
  • sdd_scan_codebaseno sensitive capability
  • sdd_setup_codespacesno sensitive capability
  • sdd_setup_local_envno sensitive capability
  • sdd_validate_earsno sensitive capability
  • sdd_validate_iacno sensitive capability
  • sdd_verify_tasksno sensitive capability
  • sdd_verify_testsno sensitive capability
  • sdd_write_bugfixno sensitive capability
  • sdd_write_designno sensitive capability
  • sdd_write_specno sensitive capability
  • sdd_write_tasksno sensitive capability

What this scan could not see

Versions 3

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v3.13.0 latest A 94/100 2 1.13.0 2026-09-09
v3.12.1 A 94/100 2 1.12.1 2026-08-10
v3.12.0 A 94/100 2 1.12.1 2026-08-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/specky-sdd/badge.svg)](https://mcptrustchecker.com/registry/specky-sdd)
HTML
<a href="https://mcptrustchecker.com/registry/specky-sdd"><img src="https://mcptrustchecker.com/registry/specky-sdd/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/specky-sdd/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan specky-sdd --online

Use the free API → How scoring works

More in Developer Tools