Umbraco CMS MCP Dev
Is Umbraco CMS MCP Dev safe? Promising trust profile, but some evidence still deserves review.
Compare Umbraco CMS MCP Dev
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Umbraco CMS MCP Dev scores 66.0/100 (Grade B), ranked #440 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 5.6/10; 88% of recent commits are signed; last pushed 2026-09-22. Every point is earned from checkable signals — never paid placement. How scoring works →
How Umbraco CMS MCP Dev compares in MCP Servers
- #257 YADE MCP Server 66.1 +0.1
- #258 MCPProxy 66.0 ±0
- #259 Umbraco CMS MCP Dev 66.0 this agent
- #260 Redmine MCP Server 66.0 ±0
- #261 MindsHub 65.8 −0.2
Bars show each HVTrust score; the tick marks Umbraco CMS MCP Dev’s 66.0.
Where the 66.0 comes from
HVTrust dimensions vs the MCP Servers average
66.0 / 100 · 100.0% confidenceUmbraco CMS MCP Dev MCP Servers average (775 agents)
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
55.7 / 100Supply Chain Trust
Common questions about Umbraco CMS MCP Dev
Does Umbraco CMS MCP Dev publish package provenance?
Does Umbraco CMS MCP Dev have an OpenSSF Scorecard?
Is Umbraco CMS MCP Dev actively maintained?
What license does Umbraco CMS MCP Dev use?
Are Umbraco CMS MCP Dev's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Umbraco CMS MCP Dev'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.
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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/umbraco-cms-mcp-dev)
<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
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