UI5 MCP Server

The UI5 MCP server improves the developer experience when working with agentic AI and the UI5 framework.

MCP Servers TypeScript Listed Apache-2.0

Is UI5 MCP Server safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 8.2 / 10
Provenance Attested
Signed commits 23%
Last push 2d ago
Advisories None known
Compare UI5 MCP Server
Suggest a correction

In detail: UI5 MCP Server scores 86.8/100 (Grade A), ranked #70 of 1378 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 8.2/10; 23% of recent commits are signed; no published advisory affects its latest release (@ui5/mcp-server); last pushed 2026-10-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How UI5 MCP Server 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 UI5 MCP Server 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/UI5/mcp-server, Apache-2.0, last pushed 2026-10-14. 23% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Strong

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

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

    • npm @ui5/mcp-server Source link points back to this repo Build provenance attested
  4. What you install today No known advisories

    Latest release checked: @ui5/mcp-server 0.3.2. No published advisory affects it (OSV, checked 2026-10-16).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-31 OSSF Scorecard: 7.7/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 UI5 MCP Server’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 UI5 MCP Server compares in MCP Servers

  1. #20 SageMath MCP 87.3 +0.5
  2. #21 MCP Hangar 87.1 +0.3
  3. #22 UI5 MCP Server 86.8 this agent
  4. #23 Microsoft 365 MCP Server 86.8 ±0
  5. #24 Canvas MCP 86.7 −0.1

Bars show each HVTrust score; the tick marks UI5 MCP Server’s 86.8.

Where the 86.8 comes from

HVTrust dimensions vs the MCP Servers average

86.8 / 100 · 100.0% confidence

UI5 MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
18.9 / 25
8.4 above avg 10.5
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.5 above avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
15.5 / 17
3.2 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
17.7 / 20
5.4 above avg 12.3
AdoptionLog-scaled stars · package downloads
11.5 / 20
4.1 above avg 7.4

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
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 → A
Maintainer Checklist
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
61.5
Activity sub-score · out of 100
#22

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A 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-16 16:07 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
103
Forks
22
Last Push
2026-10-14
2 days ago
Commits (4 wk)
28
Downloads (7d)
93,193
npm
HN mentions (30d)
—
Open Issues
3
Rank Change
▲6
was #76

Analysis

Activity Inputs

61.5 / 100
StarsRepository reach
12.1 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
18.2 / 25
CommunityFork signal
6.3 / 20

Common questions about UI5 MCP Server

Public supply-chain signals for UI5 MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but UI5 MCP Server carries less obvious unverified-evidence risk than projects with thin signals.
Does UI5 MCP Server publish package provenance?
Yes. UI5 MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does UI5 MCP Server have an OpenSSF Scorecard?
UI5 MCP Server has an OpenSSF Scorecard score of 8.2/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 UI5 MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does UI5 MCP Server use?
UI5 MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are UI5 MCP Server's commits signed?
23% of the last 100 commits to UI5 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
UI5 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
medium confidence
1 tags
Broad capability areas detected.
  • shell
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 UI5 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
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain UI5 MCP Server?

For maintainers

HVTrust scores UI5 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.

Reputation Timeline

Signal history
Rank 18HVTrust 3Grade 3Listed 2Scorecard 1Delisted 1Provenance 1MCP 1
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 → A
2026-09-23
Rank Moved
Rank rose 542 spots (#605 → #63)
2026-09-23
HVTrust Changed
HVTrust up 52.6pts (33.6 → 86.2)
2026-09-22
Newly Listed
First tracked at rank #605
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-14
Rank Moved
Rank rose 23 spots (#85 → #62)
2026-09-07
Grade Changed
Trust grade C → A
2026-09-07
Rank Moved
Rank rose 669 spots (#752 → #83)
2026-09-07
HVTrust Changed
HVTrust up 30.7pts (53.5 → 84.2)
2026-09-06
Rank Moved
Rank dropped 14 spots (#738 → #752)
2026-09-05
Rank Moved
Rank dropped 64 spots (#674 → #738)
2026-09-04
Rank Moved
Rank dropped 27 spots (#647 → #674)
2026-09-03
Rank Moved
Rank dropped 42 spots (#605 → #647)
2026-09-02
Rank Moved
Rank dropped 30 spots (#575 → #605)
2026-09-01
Rank Moved
Rank dropped 15 spots (#560 → #575)
2026-08-31
Scorecard Added
OSSF Scorecard: 7.7/10
2026-08-31
Grade Changed
Trust grade D → C
2026-08-31
Rank Moved
Rank rose 232 spots (#792 → #560)
2026-08-31
HVTrust Changed
HVTrust up 10.9pts (43.1 → 54.0)
2026-08-30
Rank Moved
Rank dropped 27 spots (#765 → #792)
2026-08-29
Rank Moved
Rank dropped 49 spots (#716 → #765)
2026-08-28
Rank Moved
Rank dropped 21 spots (#695 → #716)
2026-08-27
Rank Moved
Rank dropped 20 spots (#675 → #695)
2026-08-26
Rank Moved
Rank dropped 104 spots (#571 → #675)
2026-08-25
Rank Moved
Rank rose 12 spots (#583 → #571)
2026-08-13
Rank Moved
Rank dropped 12 spots (#546 → #558)
2026-08-10
Rank Moved
Rank dropped 19 spots (#536 → #555)
2026-08-08
Newly Listed
First tracked at rank #536

Embed Badge Badge guide for maintainers →

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