Is MCP Design System Extractor safe to use?

MCP Design System Extractor has an HVTrust score of 66.2/100 (Grade B), ranked #435 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 Design System Extractor?

MCP Design System Extractor scores 66.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 69 GitHub stars and is categorized under MCP Servers.

MCP Design System Extractor

freema/mcp-design-system-extractor

MCP (Model Context Protocol) server that enables AI assistants to interact with Storybook design systems. Extract component HTML, analyze styles, and help with design system adoption and refactoring.

MCP Servers TypeScript Listed MIT

Is MCP Design System Extractor safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 2.7 / 10

Provenance Attested

Signed commits 33%

Last push 7d ago

Compare MCP Design System Extractor

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Design System Extractor scores 66.2/100 (Grade B), ranked #435 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 2.7/10; 33% of recent commits are signed; last pushed 2026-09-19. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Design System Extractor compares in MCP Servers

#254 MCP Fiscal Brasil 66.2 ±0
#255 Npm Sentinel MCP 66.2 ±0
#256 MCP Design System Extractor 66.2 this agent
#257 YADE MCP Server 66.1 −0.1
#258 MCPProxy 66.0 −0.2

Bars show each HVTrust score; the tick marks MCP Design System Extractor’s 66.2.

Where the 66.2 comes from

HVTrust dimensions vs the MCP Servers average

66.2 / 100 · 100.0% confidence

MCP Design System Extractor MCP Servers average (775 agents)

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

12.5 / 25

2.2 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

10.8 / 17

1.4 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

12.1 / 20

in line with avg 12.1

AdoptionLog-scaled stars · package downloads

7.4 / 20

in line with avg 7.2

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-24

Rank Moved

Rank rose 13 spots (#435 → #422)

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.7/10. Tighten the weakest checks to improve public safety evidence.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for MCP Design System Extractor View MCP Servers Report missing data

44.6

Activity sub-score · out of 100

#256

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 B 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

Forks

Last Push

2026-09-19

7 days ago

Commits (4 wk)

Downloads (7d)

175

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼7

was #428

Analysis

Activity Inputs

44.6 / 100

StarsRepository reach

11.1 / 30

FreshnessLast push recency

24.0 / 25

ActivityRecent commits

3.8 / 25

CommunityFork signal

5.5 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

2.7 / 10

OpenSSF Scorecard · scanned Sep 26, 2026

Signed Commits

33%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 8

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 3

Packaging -1

Pinned-Dependencies 5

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Common questions about MCP Design System Extractor

MCP Design System Extractor has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does MCP Design System Extractor publish package provenance?

Yes. MCP Design System Extractor's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does MCP Design System Extractor have an OpenSSF Scorecard?

MCP Design System Extractor has an OpenSSF Scorecard score of 2.7/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 Design System Extractor actively maintained?

Actively maintained. The repository was pushed to within the last 7 day(s).

What license does MCP Design System Extractor use?

MCP Design System Extractor ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Design System Extractor's commits signed?

33% of the last 100 commits to MCP Design System Extractor 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 Design System Extractor 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.

Anthropic

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

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

browser

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 Design System Extractor'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

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

Provenance Added

Package provenance attestation detected

Maintain MCP Design System Extractor?

For maintainers

HVTrust scores MCP Design System Extractor 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-24

Rank Moved

Rank rose 13 spots (#435 → #422)

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

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 657 spots (#1092 → #435)

2026-09-23

HVTrust Changed

HVTrust up 43.7pts (22.4 → 66.1)

2026-09-22

Newly Listed

First tracked at rank #1092

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 15 spots (#416 → #431)

2026-09-19

Grade Changed

Trust grade C → B

2026-09-19

Rank Moved

Rank rose 135 spots (#551 → #416)

2026-09-19

HVTrust Changed

HVTrust up 4.7pts (62.0 → 66.7)

2026-09-19

Activity Score Changed

Activity score up 11pts (34 → 45)

2026-09-11

Rank Moved

Rank dropped 10 spots (#527 → #537)

2026-09-08

Rank Moved

Rank dropped 14 spots (#512 → #526)

2026-09-07

Grade Changed

Trust grade D → C

2026-09-07

Rank Moved

Rank rose 557 spots (#1069 → #512)

2026-09-07

HVTrust Changed

HVTrust up 20.6pts (41.9 → 62.5)

2026-09-06

Rank Moved

Rank dropped 16 spots (#1053 → #1069)

2026-09-05

Rank Moved

Rank dropped 40 spots (#1013 → #1053)

2026-09-04

Rank Moved

Rank dropped 24 spots (#989 → #1013)

2026-09-03

Rank Moved

Rank dropped 56 spots (#933 → #989)

2026-09-02

Rank Moved

Rank dropped 56 spots (#877 → #933)

2026-09-01

Rank Moved

Rank dropped 31 spots (#846 → #877)

2026-08-31

Rank Moved

Rank dropped 30 spots (#816 → #846)

2026-08-30

Scorecard Added

OSSF Scorecard: 2.6/10

2026-08-30

Rank Moved

Rank rose 38 spots (#854 → #816)

2026-08-30

HVTrust Changed

HVTrust up 3.5pts (38.6 → 42.1)

2026-08-29

Rank Moved

Rank dropped 45 spots (#809 → #854)

2026-08-28

Rank Moved

Rank dropped 24 spots (#785 → #809)

2026-08-27

Rank Moved

Rank dropped 23 spots (#762 → #785)

2026-08-26

Rank Moved

Rank dropped 135 spots (#627 → #762)

2026-08-26

Activity Score Changed

Activity score down 8pts (45 → 37)

2026-08-16

Rank Moved

Rank dropped 11 spots (#610 → #621)

2026-08-10

Rank Moved

Rank dropped 24 spots (#579 → #603)

2026-08-08

Newly Listed

First tracked at rank #580

GitHub → npm: mcp-design-system-extractor

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-design-system-extractor.svg)](https://hvtracker.net/agents/mcp-design-system-extractor)
            
HTML:
            <a href="https://hvtracker.net/agents/mcp-design-system-extractor"><img src="https://hvtracker.net/badge/mcp-design-system-extractor.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