updated 2026-10-18 00:07 UTC

Spec Workflow MCP

Repository

A Model Context Protocol (MCP) server that provides structured spec-driven development workflow tools for AI-assisted software development, featuring a real-time web dashboard and VSCode extension for monitoring and managing your project's progress directly in your development environment.

MCP Servers TypeScript Listed GPL-3.0

Is Spec Workflow MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.9 / 10
Provenance None
Signed commits 13%
Last push 107d ago
Compare Spec Workflow MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Spec Workflow MCP scores 41.1/100 (Grade D), ranked #1188 of 1378 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.9/10; 13% of recent commits are signed; last pushed 2026-07-03. Every point is earned from checkable signals — never paid placement. How scoring works →

How Spec Workflow MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Spec Workflow MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/Pimzino/spec-workflow-mcp, GPL-3.0, last pushed 2026-07-03. 13% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 2.9/10 (scanned Oct 16, 2026). The checks that decide who can get a change released:

    • Code Review1
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies4
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 1
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging 10
    Pinned-Dependencies 4
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages None

    No registry package. Spec Workflow MCP is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-08-31 OSSF Scorecard: 2.9/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Spec Workflow MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Spec Workflow MCP compares in MCP Servers

  1. #682 XcodeMCP 41.3 +0.2
  2. #683 Scopus MCP 41.1 ±0
  3. #684 Spec Workflow MCP 41.1 this agent
  4. #685 Sperax Crypto MCP 41.0 −0.1
  5. #686 Hermes Atlas MCP 41.0 −0.1

Bars show each HVTrust score; the tick marks Spec Workflow MCP’s 41.1.

Where the 41.1 comes from

HVTrust dimensions vs the MCP Servers average

41.1 / 100 · 100.0% confidence

Spec Workflow MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.3 / 25
6.3 below avg 10.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.8 below avg 13.6
Transparency50% declared license · 50% OSSF Scorecard
11.0 / 17
1.3 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
4.9 / 20
7.3 below avg 12.2
AdoptionLog-scaled stars · package downloads
8.7 / 20
1.3 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-01
Activity Went Stale
No commits for 90 days
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.9/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 107 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Spec Workflow MCP View MCP Servers Report missing data
44.0
Activity sub-score · out of 100
#684
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-18 00:07 UTC · Repo last pushed 107 days ago

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars
4.3k
Forks
356
Last Push
2026-07-03
107 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
6
Rank Change
▼1
was #1187

Analysis

Activity Inputs

44.0 / 100
StarsRepository reach
21.8 / 30
FreshnessLast push recency
10.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
11.9 / 20

Common questions about Spec Workflow MCP

Public trust evidence for Spec Workflow MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Spec Workflow MCP publish package provenance?
No published build provenance is currently detected for Spec Workflow MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Spec Workflow MCP have an OpenSSF Scorecard?
Spec Workflow MCP has an OpenSSF Scorecard score of 2.9/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Spec Workflow MCP actively maintained?
Slowing down. Last push was 107 days ago — keep an eye on whether activity resumes.
What license does Spec Workflow MCP use?
Spec Workflow MCP ships under GPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Spec Workflow MCP's commits signed?
13% of the last 100 commits to Spec Workflow MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Spec Workflow MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • code
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Spec Workflow MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-10-01
Activity Went Stale
No commits for 90 days
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: marketplace → declared

Maintain Spec Workflow MCP?

For maintainers

HVTrust scores Spec Workflow MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 18Listed 2HVTrust 2Surface 2Scorecard 1Delisted 1MCP 1Surface 1Stale 1
2026-10-01
Activity Went Stale
No commits for 90 days
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 455 spots (#651 → #1106)
2026-09-23
HVTrust Changed
HVTrust up 10.5pts (32.2 → 42.7)
2026-09-22
Newly Listed
First tracked at rank #651
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-12
Rank Moved
Rank dropped 11 spots (#1079 → #1090)
2026-09-09
Rank Moved
Rank dropped 14 spots (#1059 → #1073)
2026-09-07
Rank Moved
Rank dropped 36 spots (#1014 → #1050)
2026-09-06
Rank Moved
Rank dropped 14 spots (#1000 → #1014)
2026-09-05
Rank Moved
Rank dropped 50 spots (#950 → #1000)
2026-09-04
Rank Moved
Rank dropped 33 spots (#917 → #950)
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: marketplace → declared
2026-09-03
Rank Moved
Rank dropped 16 spots (#901 → #917)
2026-09-02
Rank Moved
Rank dropped 51 spots (#850 → #901)
2026-09-01
Rank Moved
Rank dropped 31 spots (#819 → #850)
2026-08-31
Scorecard Added
OSSF Scorecard: 2.9/10
2026-08-31
Rank Moved
Rank rose 425 spots (#1244 → #819)
2026-08-31
HVTrust Changed
HVTrust up 24.5pts (18.8 → 43.3)
2026-08-30
Rank Moved
Rank dropped 17 spots (#1227 → #1244)
2026-08-29
Rank Moved
Rank dropped 17 spots (#1210 → #1227)
2026-08-28
Rank Moved
Rank dropped 15 spots (#1195 → #1210)
2026-08-27
Rank Moved
Rank dropped 13 spots (#1182 → #1195)
2026-08-26
Rank Moved
Rank dropped 51 spots (#1131 → #1182)
2026-08-17
Rank Moved
Rank rose 10 spots (#1121 → #1111)
2026-08-16
Rank Moved
Rank dropped 20 spots (#1101 → #1121)
2026-08-10
Newly Listed
First tracked at rank #1096
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 41.1 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/spec-workflow-mcp.svg)](https://hvtracker.net/agents/spec-workflow-mcp)
HTML:
<a href="https://hvtracker.net/agents/spec-workflow-mcp"><img src="https://hvtracker.net/badge/spec-workflow-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON