Umbraco CMS MCP Dev

MCP Servers TypeScript Grade B Listed MIT
65.5/100
Rank #414 of 1328
Compare Umbraco CMS MCP Dev

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-09-04 · 4d ago
Recent change
Grade Changed +8

Is Umbraco CMS MCP Dev safe? Umbraco CMS MCP Dev scores 65.5/100 (Grade B), ranked #414 of 1328 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 5.1/10; 81% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-07
Grade Changed
Trust grade D → B
2026-09-07
Rank Moved
Rank rose 636 spots (#1046 → #410)
2026-09-07
HVTrust Changed
HVTrust up 22.8pts (42.8 → 65.6)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.1/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.
56.4
Activity sub-score · out of 100
#231

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

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars
39
Forks
5
Last Push
2026-09-04
4 days ago
Commits (4 wk)
31
Downloads (7d)
1,593
npm
HN mentions (30d)
Open Issues
9
Rank Change
▼4
was #410

Analysis

HVTrust Dimensions vs MCP Servers

65.5 / 100 · 100.0% confidence

Umbraco CMS MCP Dev MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.4 / 25
0.5 above avg 9.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
0.8 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
17.7 / 20
5.5 above avg 12.2
AdoptionLog-scaled stars · package downloads
8.1 / 20
1.2 above avg 6.9

Activity Inputs

56.4 / 100
StarsRepository reach
9.6 / 30
FreshnessLast push recency
24.4 / 25
ActivityRecent commits
18.8 / 25
CommunityFork signal
3.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.1 / 10
OpenSSF Scorecard · scanned Sep 3, 2026
Signed Commits
81%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 1
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 2
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is Umbraco CMS MCP Dev safe?

Umbraco CMS MCP Dev has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Umbraco CMS MCP Dev publish package provenance?
No published build provenance is currently detected for Umbraco CMS MCP Dev. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Umbraco CMS MCP Dev have an OpenSSF Scorecard?
Umbraco CMS MCP Dev has an OpenSSF Scorecard score of 5.1/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 Umbraco CMS MCP Dev actively maintained?
Actively maintained. The repository was pushed to within the last 4 day(s).
What license does Umbraco CMS MCP Dev use?
Umbraco CMS MCP Dev ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Umbraco CMS MCP Dev's commits signed?
81% of the last 100 commits to Umbraco CMS MCP Dev 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
Umbraco CMS MCP Dev appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration 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 Umbraco CMS MCP Dev?

For maintainers

HVTrust scores Umbraco CMS MCP Dev 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 17HVTrust 2Listed 1Scorecard 1Grade 1
2026-09-07
Grade Changed
Trust grade D → B
2026-09-07
Rank Moved
Rank rose 636 spots (#1046 → #410)
2026-09-07
HVTrust Changed
HVTrust up 22.8pts (42.8 → 65.6)
2026-09-06
Rank Moved
Rank dropped 19 spots (#1027 → #1046)
2026-09-05
Rank Moved
Rank dropped 44 spots (#983 → #1027)
2026-09-04
Rank Moved
Rank dropped 23 spots (#960 → #983)
2026-09-03
Rank Moved
Rank dropped 51 spots (#909 → #960)
2026-09-02
Rank Moved
Rank dropped 41 spots (#868 → #909)
2026-09-01
Rank Moved
Rank dropped 25 spots (#843 → #868)
2026-08-31
Rank Moved
Rank dropped 32 spots (#811 → #843)
2026-08-30
Rank Moved
Rank dropped 30 spots (#781 → #811)
2026-08-29
Rank Moved
Rank dropped 47 spots (#734 → #781)
2026-08-28
Rank Moved
Rank dropped 28 spots (#706 → #734)
2026-08-27
Rank Moved
Rank dropped 19 spots (#687 → #706)
2026-08-26
Scorecard Added
OSSF Scorecard: 5.1/10
2026-08-26
Rank Moved
Rank rose 202 spots (#889 → #687)
2026-08-26
HVTrust Changed
HVTrust up 18.8pts (23.7 → 42.5)
2026-08-24
Rank Moved
Rank dropped 10 spots (#879 → #889)
2026-08-16
Rank Moved
Rank dropped 21 spots (#879 → #900)
2026-08-12
Rank Moved
Rank rose 18 spots (#898 → #880)
2026-08-10
Rank Moved
Rank dropped 56 spots (#836 → #892)
2026-08-08
Newly Listed
First tracked at rank #828

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 65.5 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/umbraco-cms-mcp-dev.svg)](https://hvtracker.net/agents/umbraco-cms-mcp-dev)
HTML:
<a href="https://hvtracker.net/agents/umbraco-cms-mcp-dev"><img src="https://hvtracker.net/badge/umbraco-cms-mcp-dev.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