Is Webcomponents MCP Server safe to use?

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

What is the trust score for Webcomponents MCP Server?

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

Webcomponents MCP Server

UI5/webcomponents-mcp-server

The UI5 Web Components MCP Server improves the developer experience when working with agentic AI and the UI5 Web Compone

MCP Servers TypeScript Grade D Listed Apache-2.0

45.6/100

Rank #896 of 1320

Compare Webcomponents 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-31 · 4d ago

Recent change

Rank +7

Is Webcomponents MCP Server safe? Webcomponents MCP Server scores 45.6/100 (Grade D), ranked #896 of 1320 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; OSSF Scorecard rates its supply-chain practices 4.2/10; 35% of recent commits are signed; last pushed 2026-08-31. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#483 SmartBear MCP — 45.6 (D) → #484 Brave Search MCP Server — 45.6 (D) → #486 AEC Model Bridge — 45.5 (D) → #487 Word MCP Live — 45.5 (D) →

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-04

Rank Moved

Rank dropped 15 spots (#881 → #896)

2026-09-03

Rank Moved

Rank dropped 53 spots (#828 → #881)

2026-09-02

Rank Moved

Rank dropped 43 spots (#785 → #828)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.2/10. Tighten the weakest checks to improve public safety evidence.

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 Webcomponents MCP Server View MCP Servers Report missing data

34.4

Activity sub-score · out of 100

#485

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 →

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars

Forks

Last Push

2026-08-31

4 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼15

was #881

Analysis

HVTrust Dimensions vs MCP Servers

45.6 / 100 · 67.0% confidence

Webcomponents MCP Server MCP Servers average (778 agents)

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

14.5 / 25

5.0 above avg 9.5

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.1 / 17

in line with avg 11.8

Maintenance60% last-push freshness · 40% commit activity

11.7 / 20

0.5 below avg 12.2

AdoptionLog-scaled stars · package downloads

3.1 / 20

3.1 below avg 6.2

Activity Inputs

34.4 / 100

StarsRepository reach

7.8 / 30

FreshnessLast push recency

24.4 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

2.2 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

4.2 / 10

OpenSSF Scorecard · scanned Sep 1, 2026

Signed Commits

35%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 1

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 4

SAST 10

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is Webcomponents MCP Server safe?

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

Yes. Webcomponents MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Webcomponents MCP Server have an OpenSSF Scorecard?

Webcomponents MCP Server has an OpenSSF Scorecard score of 4.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 Webcomponents MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 4 day(s).

What license does Webcomponents MCP Server use?

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

Are Webcomponents MCP Server's commits signed?

34% of the last 100 commits to Webcomponents 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

Webcomponents 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

Maintain Webcomponents MCP Server?

For maintainers

HVTrust scores Webcomponents 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-04

Rank Moved

Rank dropped 15 spots (#881 → #896)

2026-09-03

Rank Moved

Rank dropped 53 spots (#828 → #881)

2026-09-02

Rank Moved

Rank dropped 43 spots (#785 → #828)

2026-09-01

Rank Moved

Rank dropped 34 spots (#751 → #785)

2026-08-31

Rank Moved

Rank dropped 18 spots (#733 → #751)

2026-08-30

Rank Moved

Rank dropped 26 spots (#707 → #733)

2026-08-29

Rank Moved

Rank dropped 47 spots (#660 → #707)

2026-08-28

Rank Moved

Rank dropped 21 spots (#639 → #660)

2026-08-27

Rank Moved

Rank dropped 17 spots (#622 → #639)

2026-08-26

Scorecard Added

OSSF Scorecard: 4.2/10

2026-08-26

Rank Moved

Rank rose 27 spots (#649 → #622)

2026-08-26

HVTrust Changed

HVTrust up 5.9pts (39.5 → 45.4)

2026-08-24

Rank Moved

Rank dropped 10 spots (#640 → #650)

2026-08-17

Rank Moved

Rank rose 14 spots (#652 → #638)

2026-08-16

Rank Moved

Rank dropped 15 spots (#637 → #652)

2026-08-10

Rank Moved

Rank dropped 24 spots (#603 → #627)

2026-08-08

Newly Listed

First tracked at rank #604

GitHub → npm: @ui5/webcomponents-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

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