Is Spec Workflow safe and trustworthy?

tashan scores Spec Workflow on public evidence — tashan score 44.0/100, it is currently abandoned, note: a single primary maintainer (bus-factor risk), no known advisories against the current release, its declared dependencies reach: filesystem. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Spec Workflow?

In Claude Code: run `claude mcp add pimzino-spec-workflow -- npx -y @pimzino/spec-workflow-mcp`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

Who maintains Spec Workflow?

See the linked source repository..

‹ The Index

Spec Workflow

npm

MCP server for spec-driven development workflow with real-time web dashboard

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Category: Dev Tools & CI — see all ranked ›

Work: Project management

Who it is for: Product manager · Operations

Install (Claude Code):

claude mcp add pimzino-spec-workflow -- npx -y @pimzino/spec-workflow-mcp

Looking for a replacement? npx tashan-cli doctor is free and tells you everything above about your whole config. tashan Pro names the replacement — which one, and how it measures. $6/mo.

tashan score: 44.0
Adoption: 433/wk
Upkeep: 55.0
Freshness: 49.0
Evidence coverage: 100% of the inputs this score can use
Health: abandoned
License: GPL-3.0

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 2.2.5 — this package, not its dependency tree

Reads and writes filesfrom declared dependencies

No build provenanceno attestation — the published artifact cannot be traced to its source

What changed recently

2026-09-13 @pimzino/spec-workflow-mcp now reads as abandoned, was active Upkeep signals stopped, under enough issue pressure that it is not merely finished.

You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

We recorded 1 change to Spec Workflow in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-pimzino-spec-workflow-mcp.svg)](https://tashan.sh/capability/pkg-pimzino-spec-workflow-mcp.html)

npm ↗ · pkg:@pimzino/spec-workflow-mcp

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?