Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.formulahendry/spec-driven-development

NPM · MCP-SERVER-SPEC-DRIVEN-DEVELOPMENT · SCANNED SEP 20

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Available components

npm · mcp-server-spec-driven-development 62
0 this week 62 Trust /100
Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency43
Schema Quality & AI Usability36
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • Instruction-quality not yet verified: the AI judgement didn't run.Unverified
  • Nothing to assess: this server exposes no tool/resource definitions to measure a footprint for. See how to fix → Fail
  • Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
  • Nothing to assess: this server exposes no tools, so there are no tool definitions to check for coverage.Fail
Tool Safety0
  • Injection markers not yet verified: our capture carried no server instructions, tool names or descriptions for the scan to read.Unverified
  • Destructive-tool annotations not yet verified: our capture listed no tools, so there were no annotations to read.Unverified
  • Manipulation not yet verified: our capture carried no tool text for a judge to read, so we will not certify text no model has read as clean.Unverified
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the io.github.formulahendry/spec-driven-development MCP server?

io.github.formulahendry/spec-driven-development runs locally as an npm package, launched with npx -y mcp-server-spec-driven-development. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mcp-server-spec-driven-development

# add to Claude Code
claude mcp add formulahendry-spec-driven-development -- npx -y mcp-server-spec-driven-development
// .cursor/mcp.json
{
  "mcpServers": {
    "formulahendry-spec-driven-development": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-spec-driven-development"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "formulahendry-spec-driven-development": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-spec-driven-development"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add formulahendry-spec-driven-development -- npx -y mcp-server-spec-driven-development
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "formulahendry-spec-driven-development": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-server-spec-driven-development"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add formulahendry-spec-driven-development --command npx --arg -y --arg mcp-server-spec-driven-development
# ~/.hermes/config.yaml
mcp_servers:
  formulahendry-spec-driven-development:
    command: "npx"
    args: ["-y", "mcp-server-spec-driven-development"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "formulahendry-spec-driven-development": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-server-spec-driven-development"
      ]
    }
  }
}
# add to Vellum
assistant mcp add formulahendry-spec-driven-development -t stdio -c npx -a -y mcp-server-spec-driven-development
// mcp.json
{
  "mcpServers": {
    "formulahendry-spec-driven-development": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-spec-driven-development"
      ]
    }
  }
}
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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −2
    • Stability: pass → 0.83 functional
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/mcp-server-spec-driven-development@0.1.1

Provenance No attestation

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

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

The sandbox run completed and this package exposed no tools.

Common questions

What is the io.github.formulahendry/spec-driven-development MCP server?

io.github.formulahendry/spec-driven-development is an MCP server listed in the public MCP registry as io.github.formulahendry/spec-driven-development. MCP Server that facilitates spec-driven development workflows, not just Vibe Coding. This page covers its npm package (mcp-server-spec-driven-development).

Is the io.github.formulahendry/spec-driven-development MCP server safe to use?

io.github.formulahendry/spec-driven-development scores 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.formulahendry/spec-driven-development MCP server expose?

io.github.formulahendry/spec-driven-development exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.

Is the io.github.formulahendry/spec-driven-development MCP server still maintained?

io.github.formulahendry/spec-driven-development is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.formulahendry/spec-driven-development MCP server under?

io.github.formulahendry/spec-driven-development declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.