updated 2026-08-12 05:02 UTC

UI5 MCP Server

UI5/mcp-server

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

MCP Servers TypeScript Grade D Listed Apache-2.0
43.8/100
Rank #554 of 1283
Compare UI5 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 C · 2/5 signals
Last push
2026-08-11 · 1d ago
Recent change
Rank +1

Is UI5 MCP Server safe? UI5 MCP Server scores 43.8/100 (Grade D), ranked #554 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; no OSSF Scorecard result yet; 11% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#205 Api MCP Server — 43.9 (D) → #206 Mdk MCP Server — 43.8 (D) → #208 Search1API — 43.6 (D) → #209 Scrcpy MCP — 43.5 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 19 spots (#536 → #555)
2026-08-08
Newly Listed
First tracked at rank #536
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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 UI5 MCP Server View MCP Servers Report missing data
61.0
Activity sub-score · out of 100
#207
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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
96
Forks
19
Last Push
2026-08-11
yesterday
Commits (4 wk)
27
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
▼1
was #553

Analysis

HVTrust Dimensions vs MCP Servers

43.8 / 100 · 67.0% confidence

UI5 MCP Server MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.1 / 25
3.1 above avg 5.0
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.7 above avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
17.7 / 20
5.3 above avg 12.4
AdoptionLog-scaled stars · package downloads
4.8 / 20
1.0 below avg 5.8

Activity Inputs

61.0 / 100
StarsRepository reach
11.9 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
18.1 / 25
CommunityFork signal
6.0 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
—
Not available
Signed Commits
11%
of last 100 commits verified

Is UI5 MCP Server safe?

Public trust evidence for UI5 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 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?
No OpenSSF Scorecard data is currently published for UI5 MCP Server. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is UI5 MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 1 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?
11% 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

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Listed 1Rank 1
2026-08-10
Rank Moved
Rank dropped 19 spots (#536 → #555)
2026-08-08
Newly Listed
First tracked at rank #536
GitHub → npm: @ui5/mcp-server

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 43.8 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON