XamlMcp

An MCP-based AI development toolkit for XAML UI frameworks.

MCP Servers C# Grade D Listed Apache-2.0
40.1/100
Rank #1044 of 1320
Compare XamlMcp

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-05 · 30d ago
Recent change
Rank +10

Is XamlMcp safe? XamlMcp scores 40.1/100 (Grade D), ranked #1044 of 1320 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 →

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-04
Rank Moved
Rank dropped 85 spots (#959 → #1044)
2026-09-04
Activity Score Changed
Activity score down 9pts (38 → 29)
2026-09-03
Rank Moved
Rank dropped 55 spots (#904 → #959)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.6/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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
29.4
Activity sub-score · out of 100
#586

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-09-04 22:32 UTC · Repo last pushed 30 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
26
Forks
0
Last Push
2026-08-05
30 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
0
Rank Change
▼85
was #959

Analysis

HVTrust Dimensions vs MCP Servers

40.1 / 100 · 100.0% confidence

XamlMcp MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.2 / 25
6.4 below avg 9.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
10.7 / 17
1.1 below avg 11.8
Maintenance60% last-push freshness · 40% commit activity
10.0 / 20
2.2 below avg 12.2
AdoptionLog-scaled stars · package downloads
3.4 / 20
2.9 below avg 6.3

Activity Inputs

29.4 / 100
StarsRepository reach
8.6 / 30
FreshnessLast push recency
20.8 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
0.0 / 20

Supply Chain Trust

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

Is XamlMcp safe?

Public trust evidence for XamlMcp 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 XamlMcp publish package provenance?
No published build provenance is currently detected for XamlMcp. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does XamlMcp have an OpenSSF Scorecard?
XamlMcp has an OpenSSF Scorecard score of 2.6/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 XamlMcp actively maintained?
Maintained. Last push was 30 days ago.
What license does XamlMcp use?
XamlMcp ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are XamlMcp's commits signed?
0% of the last 100 commits to XamlMcp 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
XamlMcp 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
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

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
Rank 15HVTrust 2Score 2Listed 1Scorecard 1
2026-09-04
Rank Moved
Rank dropped 85 spots (#959 → #1044)
2026-09-04
Activity Score Changed
Activity score down 9pts (38 → 29)
2026-09-03
Rank Moved
Rank dropped 55 spots (#904 → #959)
2026-09-02
Rank Moved
Rank dropped 132 spots (#772 → #904)
2026-09-02
HVTrust Changed
HVTrust down 3.1pts (46.1 → 43.0)
2026-09-02
Activity Score Changed
Activity score down 10pts (48 → 38)
2026-09-01
Rank Moved
Rank dropped 71 spots (#701 → #772)
2026-08-31
Rank Moved
Rank dropped 46 spots (#655 → #701)
2026-08-30
Rank Moved
Rank dropped 23 spots (#632 → #655)
2026-08-29
Rank Moved
Rank dropped 41 spots (#591 → #632)
2026-08-28
Rank Moved
Rank dropped 18 spots (#573 → #591)
2026-08-27
Rank Moved
Rank dropped 15 spots (#558 → #573)
2026-08-26
Scorecard Added
OSSF Scorecard: 2.6/10
2026-08-26
Rank Moved
Rank rose 380 spots (#938 → #558)
2026-08-26
HVTrust Changed
HVTrust up 26.0pts (22.7 → 48.7)
2026-08-24
Rank Moved
Rank dropped 14 spots (#924 → #938)
2026-08-22
Rank Moved
Rank rose 12 spots (#939 → #927)
2026-08-17
Rank Moved
Rank rose 13 spots (#949 → #936)
2026-08-16
Rank Moved
Rank dropped 25 spots (#924 → #949)
2026-08-10
Rank Moved
Rank dropped 53 spots (#862 → #915)
2026-08-08
Newly Listed
First tracked at rank #848

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 40.1 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/xamlmcp.svg)](https://hvtracker.net/agents/xamlmcp)
HTML:
<a href="https://hvtracker.net/agents/xamlmcp"><img src="https://hvtracker.net/badge/xamlmcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
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