Is shadcn-ui MCP Server safe to use?

shadcn-ui MCP Server has an HVTrust score of 50.2/100 (Grade C), ranked #893 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for shadcn-ui MCP Server?

shadcn-ui MCP Server scores 50.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 3.0k GitHub stars and is categorized under MCP Servers.

shadcn-ui MCP Server

Jpisnice/shadcn-ui-mcp-server

A mcp server to allow LLMS gain context about shadcn ui component structure,usage and installation,compaitable with reac

MCP Servers TypeScript Grade C Listed MIT

50.2/100

Rank #893 of 1328

Compare shadcn-ui MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-05-16 · 115d ago

Recent change

Rank +12

Is shadcn-ui MCP Server safe? shadcn-ui MCP Server scores 50.2/100 (Grade C), ranked #893 of 1328 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 3.3/10; 34% of recent commits are signed; last pushed 2026-05-16. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#502 Switzerland MCP 🇨🇭 — 50.3 (C) → #503 MCP Brasil — 50.2 (C) → #505 Zapier — 50.1 (C) → #506 Mobile Device MCP — 50.1 (C) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-08

Rank Moved

Rank dropped 11 spots (#882 → #893)

2026-09-07

Rank Moved

Rank dropped 42 spots (#840 → #882)

2026-09-06

Rank Moved

Rank dropped 11 spots (#829 → #840)

Maintainer Checklist

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

Compare with another agent Get email alerts for shadcn-ui MCP Server View MCP Servers Report missing data

41.4

Activity sub-score · out of 100

#504

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 C 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-08

Activity & Reach

Stars

3.0k

Forks

304

Last Push

2026-05-16

115 days ago

Commits (4 wk)

Downloads (7d)

3,080

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼11

was #882

Analysis

HVTrust Dimensions vs MCP Servers

50.2 / 100 · 100.0% confidence

shadcn-ui MCP Server MCP Servers average (778 agents)

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

5.8 / 25

4.1 below avg 9.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.3 / 17

0.7 below avg 12.0

Maintenance60% last-push freshness · 40% commit activity

4.3 / 20

7.9 below avg 12.2

AdoptionLog-scaled stars · package downloads

13.0 / 20

6.1 above avg 6.9

Activity Inputs

41.4 / 100

StarsRepository reach

20.8 / 30

FreshnessLast push recency

9.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

11.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.3 / 10

OpenSSF Scorecard · scanned Aug 31, 2026

Signed Commits

34%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 6

Dangerous-Workflow 0

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 3

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is shadcn-ui MCP Server safe?

Public trust evidence for shadcn-ui MCP Server 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 shadcn-ui MCP Server publish package provenance?

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

Does shadcn-ui MCP Server have an OpenSSF Scorecard?

shadcn-ui MCP Server has an OpenSSF Scorecard score of 3.3/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 shadcn-ui MCP Server actively maintained?

Slowing down. Last push was 115 days ago — keep an eye on whether activity resumes.

What license does shadcn-ui MCP Server use?

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

Are shadcn-ui MCP Server's commits signed?

34% of the last 100 commits to shadcn-ui MCP Server 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

shadcn-ui MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

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 shadcn-ui MCP Server'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-02

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-08-14

Activity Went Stale

No commits for 90 days

Maintain shadcn-ui MCP Server?

For maintainers

HVTrust scores shadcn-ui MCP Server 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-08

Rank Moved

Rank dropped 11 spots (#882 → #893)

2026-09-07

Rank Moved

Rank dropped 42 spots (#840 → #882)

2026-09-06

Rank Moved

Rank dropped 11 spots (#829 → #840)

2026-09-05

Grade Changed

Trust grade D → C

2026-09-05

Rank Moved

Rank rose 363 spots (#1192 → #829)

2026-09-05

HVTrust Changed

HVTrust up 18.2pts (32.2 → 50.4)

2026-09-04

Rank Moved

Rank dropped 17 spots (#1175 → #1192)

2026-09-03

Rank Moved

Rank dropped 42 spots (#1133 → #1175)

2026-09-02

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-09-02

Grade Changed

Trust grade C → D

2026-09-02

Rank Moved

Rank dropped 486 spots (#647 → #1133)

2026-09-02

HVTrust Changed

HVTrust down 18.8pts (51.1 → 32.3)

2026-09-01

Rank Moved

Rank dropped 24 spots (#623 → #647)

2026-08-31

Scorecard Added

OSSF Scorecard: 3.3/10

2026-08-31

Grade Changed

Trust grade D → C

2026-08-31

Rank Moved

Rank rose 413 spots (#1036 → #623)

2026-08-31

HVTrust Changed

HVTrust up 19.9pts (31.3 → 51.2)

2026-08-30

Rank Moved

Rank dropped 57 spots (#979 → #1036)

2026-08-29

Rank Moved

Rank dropped 48 spots (#931 → #979)

2026-08-28

Rank Moved

Rank dropped 35 spots (#896 → #931)

2026-08-27

Rank Moved

Rank dropped 30 spots (#866 → #896)

2026-08-26

Rank Moved

Rank dropped 111 spots (#755 → #866)

2026-08-16

Rank Moved

Rank dropped 15 spots (#738 → #753)

2026-08-14

Activity Went Stale

No commits for 90 days

2026-08-10

Newly Listed

First tracked at rank #737

GitHub → npm: @jpisnice/shadcn-ui-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

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