Is Ux MCP Server safe to use?

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

What is the trust score for Ux MCP Server?

Ux MCP Server scores 42.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 29 GitHub stars and is categorized under MCP Servers.

Ux MCP Server

elsahafy/ux-mcp-server

MCP server providing 28 UX knowledge resources, 23 analysis tools & 4 workflow prompts. Works with Claude, Cursor, Continue.dev, Cline, Zed & any MCP client. WCAG, Nielsen heuristics, design systems, e-commerce, PWA, AI/ML & more.

MCP Servers JavaScript Listed MIT

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

OSSF Scorecard 4.6 / 10

Provenance None

Signed commits 32%

Last push 178d ago

Compare Ux MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Ux MCP Server scores 42.9/100 (Grade D), ranked #1103 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 4.6/10; 32% of recent commits are signed; last pushed 2026-04-01. Every point is earned from checkable signals — never paid placement. How scoring works →

How Ux MCP Server compares in MCP Servers

#646 Microsoft MCP Server for Enterprise 43.0 +0.1
#647 Opendocswork MCP 43.0 +0.1
#648 Ux MCP Server 42.9 this agent
#649 Apple Docs MCP 42.8 −0.1
#650 Flstudio MCP 42.8 −0.1

Bars show each HVTrust score; the tick marks Ux MCP Server’s 42.9.

Where the 42.9 comes from

HVTrust dimensions vs the MCP Servers average

42.9 / 100 · 100.0% confidence

Ux MCP Server MCP Servers average (775 agents)

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

7.4 / 25

2.9 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

12.4 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

0.1 / 20

12.0 below avg 12.1

AdoptionLog-scaled stars · package downloads

6.2 / 20

1.0 below 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 140 spots (#1237 → #1097)

2026-09-23

HVTrust Changed

HVTrust up 26.8pts (16.3 → 43.1)

Maintainer Checklist

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

Compare with another agent Get email alerts for Ux MCP Server View MCP Servers Report missing data

11.5

Activity sub-score · out of 100

#648

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

Forks

Last Push

2026-04-01

178 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #1102

Analysis

Activity Inputs

11.5 / 100

StarsRepository reach

8.9 / 30

FreshnessLast push recency

0.3 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

2.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.6 / 10

OpenSSF Scorecard · scanned Sep 19, 2026

Signed Commits

32%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 8

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 3

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 0

Common questions about Ux MCP Server

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

No published build provenance is currently detected for Ux 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 Ux MCP Server have an OpenSSF Scorecard?

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

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

What license does Ux MCP Server use?

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

Are Ux MCP Server's commits signed?

32% of the last 100 commits to Ux 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

Ux MCP Server 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 Ux 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-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Ux MCP Server?

For maintainers

HVTrust scores Ux 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-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank rose 140 spots (#1237 → #1097)

2026-09-23

HVTrust Changed

HVTrust up 26.8pts (16.3 → 43.1)

2026-09-22

Newly Listed

First tracked at rank #1237

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-12

Rank Moved

Rank dropped 14 spots (#1070 → #1084)

2026-09-11

Rank Moved

Rank dropped 10 spots (#1060 → #1070)

2026-09-09

Rank Moved

Rank dropped 13 spots (#1049 → #1062)

2026-09-07

Rank Moved

Rank rose 220 spots (#1261 → #1041)

2026-09-07

HVTrust Changed

HVTrust up 14.3pts (29.7 → 44.0)

2026-09-06

Rank Moved

Rank dropped 14 spots (#1247 → #1261)

2026-09-05

Rank Moved

Rank dropped 20 spots (#1227 → #1247)

2026-09-04

Rank Moved

Rank dropped 18 spots (#1209 → #1227)

2026-09-03

Rank Moved

Rank dropped 42 spots (#1167 → #1209)

2026-09-02

Scorecard Added

OSSF Scorecard: 4.6/10

2026-09-02

Rank Moved

Rank rose 125 spots (#1292 → #1167)

2026-09-02

HVTrust Changed

HVTrust up 13.4pts (16.5 → 29.9)

2026-08-29

Rank Moved

Rank dropped 12 spots (#1262 → #1274)

2026-08-26

Rank Moved

Rank dropped 25 spots (#1221 → #1246)

2026-08-16

Rank Moved

Rank dropped 26 spots (#1188 → #1214)

2026-08-10

Rank Moved

Rank dropped 72 spots (#1114 → #1186)

2026-08-08

Newly Listed

First tracked at rank #1109

GitHub → npm: @elsahafy/ux-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

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