XamlMcp
An MCP-based AI development toolkit for XAML UI frameworks.
Is XamlMcp safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare XamlMcp
How does it stack up against its MCP Servers neighbours?
- Unreal MCP Ue4 +0.4 higher
- MCP Server Spec Driven Development +0.2 higher
- Terminal MCP Server 0.2 lower
In detail: XamlMcp scores 38.7/100 (Grade D), ranked #1189 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.6/10; recent commits are unsigned; last pushed 2026-08-05. Every point is earned from checkable signals — never paid placement. How scoring works →
How XamlMcp compares in MCP Servers
- #706 Unreal MCP Ue4 39.1 +0.4
- #707 MCP Server Spec Driven Development 38.9 +0.2
- #708 XamlMcp 38.7 this agent
- #709 Terminal MCP Server 38.5 −0.2
- #710 OneTool MCP 38.5 −0.2
Bars show each HVTrust score; the tick marks XamlMcp’s 38.7.
Where the 38.7 comes from
HVTrust dimensions vs the MCP Servers average
38.7 / 100 · 100.0% confidenceXamlMcp 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 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
Activity & Reach
Analysis
Activity Inputs
26.6 / 100Supply Chain Trust
Common questions about XamlMcp
Does XamlMcp publish package provenance?
Does XamlMcp have an OpenSSF Scorecard?
Is XamlMcp actively maintained?
What license does XamlMcp use?
Are XamlMcp'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 XamlMcp'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 XamlMcp?
For maintainers
HVTrust scores XamlMcp 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/xamlmcp)
<a href="https://hvtracker.net/agents/xamlmcp"><img src="https://hvtracker.net/badge/xamlmcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON