Starwind UI MCP

Framework-aware Starwind UI v3 tools for Astro and React setup, components, docs, and migration.

MCP Servers TypeScript Listed MIT

Is Starwind UI MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.4 / 10
Provenance None
Signed commits 22%
Last push 57d ago
Advisories None known
Compare Starwind UI MCP
Suggest a correction

In detail: Starwind UI MCP scores 50.5/100 (Grade C), ranked #969 of 1371 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 4.4/10; 22% of recent commits are signed; no published advisory affects its latest release (@starwind-ui/mcp); last pushed 2026-08-15. Every point is earned from checkable signals — never paid placement. How scoring works →

How Starwind UI 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.

Chain of custody

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

  1. Source Partly signed

    github.com/starwind-ui/starwind-ui-mcp, MIT, last pushed 2026-08-15. 22% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

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

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions9
    • Pinned Dependencies10
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 0
    Contributors 6
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 10
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 9
    Vulnerabilities 0
  3. Published packages Linked, not attested

    • npm @starwind-ui/mcp Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @starwind-ui/mcp 0.5.1. No published advisory affects it (OSV, checked 2026-10-11).

Changes to this chain

  • 2026-09-05 OSSF Scorecard: 4.4/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Starwind UI 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.

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 Starwind UI MCP compares in MCP Servers

  1. #546 OSS Snowflake MCP Server 50.7 +0.2
  2. #547 Tomyud1 Godot MCP 50.6 +0.1
  3. #548 Starwind UI MCP 50.5 this agent
  4. #549 MCPSpend 50.5 ±0
  5. #550 JADX MCP Server 50.5 ±0

Bars show each HVTrust score; the tick marks Starwind UI MCP’s 50.5.

Where the 50.5 comes from

HVTrust dimensions vs the MCP Servers average

50.5 / 100 · 100.0% confidence

Starwind UI MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.6 / 25
3.8 below avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
12.2 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
8.2 / 20
4.0 below avg 12.2
AdoptionLog-scaled stars · package downloads
6.7 / 20
0.7 below 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-09
Rank Moved
Rank dropped 19 spots (#933 → #952)
2026-09-30
Rank Moved
Rank dropped 14 spots (#896 → #910)
2026-09-26
Rank Moved
Rank rose 11 spots (#906 → #895)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.4/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 57 days ago. Fresh activity helps separate stable projects from stale ones.
32.2
Activity sub-score · out of 100
#548

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 →

Signals refreshed 2026-10-11 08:08 UTC · Repo last pushed 57 days ago

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
35
Forks
17
Last Push
2026-08-15
57 days ago
Commits (4 wk)
0
Downloads (7d)
178
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼8
was #961

Analysis

Activity Inputs

32.2 / 100
StarsRepository reach
9.3 / 30
FreshnessLast push recency
17.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
5.8 / 20

Common questions about Starwind UI MCP

Public trust evidence for Starwind UI 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 Starwind UI MCP publish package provenance?
No published build provenance is currently detected for Starwind UI 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 Starwind UI MCP have an OpenSSF Scorecard?
Starwind UI MCP has an OpenSSF Scorecard score of 4.4/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 Starwind UI MCP actively maintained?
Slowing down. Last push was 57 days ago — keep an eye on whether activity resumes.
What license does Starwind UI MCP use?
Starwind UI MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Starwind UI MCP's commits signed?
21% of the last 100 commits to Starwind UI 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
Starwind UI MCP 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 Starwind UI 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-09-24
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Starwind UI MCP?

For maintainers

HVTrust scores Starwind UI 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.

Reputation Timeline

Signal history
Rank 22HVTrust 5Listed 2Grade 2Scorecard 1Score 1Delisted 1MCP 1
2026-10-09
Rank Moved
Rank dropped 19 spots (#933 → #952)
2026-09-30
Rank Moved
Rank dropped 14 spots (#896 → #910)
2026-09-26
Rank Moved
Rank rose 11 spots (#906 → #895)
2026-09-24
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-24
Grade Changed
Trust grade D → C
2026-09-24
Rank Moved
Rank rose 45 spots (#943 → #898)
2026-09-23
Rank Moved
Rank rose 158 spots (#1101 → #943)
2026-09-23
HVTrust Changed
HVTrust up 27.3pts (22.1 → 49.4)
2026-09-22
Newly Listed
First tracked at rank #1101
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-14
Rank Moved
Rank dropped 113 spots (#749 → #862)
2026-09-14
HVTrust Changed
HVTrust down 3.4pts (55.5 → 52.1)
2026-09-14
Activity Score Changed
Activity score down 11pts (47 → 36)
2026-09-12
Rank Moved
Rank dropped 10 spots (#737 → #747)
2026-09-11
Rank Moved
Rank dropped 41 spots (#696 → #737)
2026-09-08
Rank Moved
Rank dropped 10 spots (#671 → #681)
2026-09-07
Rank Moved
Rank dropped 60 spots (#611 → #671)
2026-09-06
Rank Moved
Rank dropped 12 spots (#599 → #611)
2026-09-05
Scorecard Added
OSSF Scorecard: 4.4/10
2026-09-05
Grade Changed
Trust grade D → C
2026-09-05
Rank Moved
Rank rose 567 spots (#1166 → #599)
2026-09-05
HVTrust Changed
HVTrust up 23.3pts (34.3 → 57.6)
2026-09-04
Rank Moved
Rank rose 113 spots (#1279 → #1166)
2026-09-04
HVTrust Changed
HVTrust up 12.5pts (21.8 → 34.3)
2026-09-03
Rank Moved
Rank dropped 186 spots (#1093 → #1279)
2026-09-03
HVTrust Changed
HVTrust down 13.0pts (34.8 → 21.8)
2026-09-02
Rank Moved
Rank dropped 46 spots (#1047 → #1093)
2026-09-01
Rank Moved
Rank dropped 42 spots (#1005 → #1047)
2026-08-31
Rank Moved
Rank dropped 31 spots (#974 → #1005)
2026-08-30
Rank Moved
Rank dropped 49 spots (#925 → #974)
2026-08-29
Rank Moved
Rank dropped 52 spots (#873 → #925)
2026-08-28
Rank Moved
Rank dropped 32 spots (#841 → #873)
2026-08-27
Rank Moved
Rank dropped 22 spots (#819 → #841)
2026-08-26
Rank Moved
Rank dropped 109 spots (#710 → #819)
2026-08-16
Newly Listed
First tracked at rank #707

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 50.5 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/starwind-ui-mcp.svg)](https://hvtracker.net/agents/starwind-ui-mcp)
HTML:
<a href="https://hvtracker.net/agents/starwind-ui-mcp"><img src="https://hvtracker.net/badge/starwind-ui-mcp.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.4 · Raw JSON