Is MCP Server Spec Driven Development safe to use?

MCP Server Spec Driven Development has an HVTrust score of 38.9/100 (Grade D), ranked #1187 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Server Spec Driven Development?

MCP Server Spec Driven Development scores 38.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 437 GitHub stars and is categorized under MCP Servers.

MCP Server Spec Driven Development

formulahendry/mcp-server-spec-driven-development

Spec-Driven Development MCP Server, not just Vibe Coding

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 1.9 / 10

Provenance None

Signed commits 22%

Last push 365d ago

Compare MCP Server Spec Driven Development

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Server Spec Driven Development scores 38.9/100 (Grade D), ranked #1187 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 1.9/10; 22% of recent commits are signed; last pushed 2025-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Server Spec Driven Development compares in MCP Servers

#705 Dmca Takedown MCP 39.1 +0.2
#706 Unreal MCP Ue4 39.1 +0.2
#707 MCP Server Spec Driven Development 38.9 this agent
#708 XamlMcp 38.7 −0.2
#709 Terminal MCP Server 38.5 −0.4

Bars show each HVTrust score; the tick marks MCP Server Spec Driven Development’s 38.9.

Where the 38.9 comes from

HVTrust dimensions vs the MCP Servers average

38.9 / 100 · 100.0% confidence

MCP Server Spec Driven Development MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

3.5 / 25

6.8 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

10.1 / 17

2.1 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

0 / 20

12.1 below avg 12.1

AdoptionLog-scaled stars · package downloads

8.5 / 20

1.3 above avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank rose 93 spots (#1280 → #1187)

2026-09-23

HVTrust Changed

HVTrust up 24.7pts (14.1 → 38.8)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 1.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 365 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for MCP Server Spec Driven Development View MCP Servers Report missing data

23.3

Activity sub-score · out of 100

#707

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 B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

437

Forks

Last Push

2025-09-26

365 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #1188

Analysis

Activity Inputs

23.3 / 100

StarsRepository reach

15.8 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

7.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

1.9 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

22%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 1

Contributors 10

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 0

Common questions about MCP Server Spec Driven Development

Public trust evidence for MCP Server Spec Driven Development 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 MCP Server Spec Driven Development publish package provenance?

No published build provenance is currently detected for MCP Server Spec Driven Development. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does MCP Server Spec Driven Development have an OpenSSF Scorecard?

MCP Server Spec Driven Development has an OpenSSF Scorecard score of 1.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 MCP Server Spec Driven Development actively maintained?

Stale. The repository has not been pushed to in 365 days. Consider whether the project is still being maintained.

What license does MCP Server Spec Driven Development use?

MCP Server Spec Driven Development ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Server Spec Driven Development's commits signed?

22% of the last 100 commits to MCP Server Spec Driven Development 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

MCP Server Spec Driven Development appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

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 MCP Server Spec Driven Development'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-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain MCP Server Spec Driven Development?

For maintainers

HVTrust scores MCP Server Spec Driven Development 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

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank rose 93 spots (#1280 → #1187)

2026-09-23

HVTrust Changed

HVTrust up 24.7pts (14.1 → 38.8)

2026-09-22

Newly Listed

First tracked at rank #1280

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-09

Rank Moved

Rank dropped 11 spots (#1162 → #1173)

2026-09-08

Rank Moved

Rank rose 124 spots (#1286 → #1162)

2026-09-08

HVTrust Changed

HVTrust up 12.0pts (26.5 → 38.5)

2026-09-06

Rank Moved

Rank dropped 12 spots (#1266 → #1278)

2026-09-05

Rank Moved

Rank dropped 14 spots (#1252 → #1266)

2026-09-04

Rank Moved

Rank dropped 14 spots (#1238 → #1252)

2026-09-03

Rank Moved

Rank dropped 37 spots (#1201 → #1238)

2026-09-02

Rank Moved

Rank dropped 36 spots (#1165 → #1201)

2026-09-01

Rank Moved

Rank dropped 41 spots (#1124 → #1165)

2026-08-31

Rank Moved

Rank dropped 30 spots (#1094 → #1124)

2026-08-30

Rank Moved

Rank dropped 48 spots (#1046 → #1094)

2026-08-29

Rank Moved

Rank dropped 50 spots (#996 → #1046)

2026-08-28

Scorecard Added

OSSF Scorecard: 1.9/10

2026-08-28

Rank Moved

Rank rose 257 spots (#1253 → #996)

2026-08-28

HVTrust Changed

HVTrust up 9.8pts (16.7 → 26.5)

2026-08-26

Rank Moved

Rank dropped 29 spots (#1215 → #1244)

2026-08-16

Rank Moved

Rank dropped 26 spots (#1192 → #1218)

2026-08-10

Rank Moved

Rank dropped 70 spots (#1128 → #1198)

2026-08-08

Newly Listed

First tracked at rank #1125

GitHub → npm: mcp-server-spec-driven-development

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-server-spec-driven-development.svg)](https://hvtracker.net/agents/mcp-server-spec-driven-development)
            
HTML:
            <a href="https://hvtracker.net/agents/mcp-server-spec-driven-development"><img src="https://hvtracker.net/badge/mcp-server-spec-driven-development.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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