MCP Unity

Model Context Protocol (MCP) plugin to connect with Unity Editor — designed for Cursor, Claude Code, Codex, Windsurf and

MCP Servers C# Grade D Listed MIT
49.3/100
Rank #922 of 1328
Compare MCP Unity

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-09-03 · 5d ago
Recent change
Rank +9

Is MCP Unity safe? MCP Unity scores 49.3/100 (Grade D), ranked #922 of 1328 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 3.1/10; 29% of recent commits are signed; last pushed 2026-09-03. 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-08
Rank Moved
Rank dropped 16 spots (#906 → #922)
2026-09-07
Rank Moved
Rank dropped 40 spots (#866 → #906)
2026-09-06
Rank Moved
Rank dropped 14 spots (#852 → #866)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
64.8
Activity sub-score · out of 100
#529

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-08 15:03 UTC · Repo last pushed 5 days ago

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars
1.9k
Forks
239
Last Push
2026-09-03
5 days ago
Commits (4 wk)
5?
Downloads (7d)
HN mentions (30d)
Open Issues
2
Rank Change
▼16
was #906

Analysis

HVTrust Dimensions vs MCP Servers

49.3 / 100 · 100.0% confidence

MCP Unity MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.3 / 25
4.6 below 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
11.1 / 17
0.9 below avg 12.0
Maintenance60% last-push freshness · 40% commit activity
13.2 / 20
1.0 above avg 12.2
AdoptionLog-scaled stars · package downloads
7.9 / 20
1.0 above avg 6.9

Activity Inputs

64.8 / 100
StarsRepository reach
19.7 / 30
FreshnessLast push recency
24.3 / 25
ActivityRecent commits
9.7 / 25
CommunityFork signal
11.1 / 20

Supply Chain Trust

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

Is MCP Unity safe?

Public trust evidence for MCP Unity 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 MCP Unity publish package provenance?
No published build provenance is currently detected for MCP Unity. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does MCP Unity have an OpenSSF Scorecard?
MCP Unity has an OpenSSF Scorecard score of 3.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 MCP Unity actively maintained?
Actively maintained. The repository was pushed to within the last 5 day(s).
What license does MCP Unity use?
MCP Unity ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Unity's commits signed?
28% of the last 100 commits to MCP Unity 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
MCP Unity appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
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
How this surface has changed

Detected changes to MCP Unity'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.

2026-09-02
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none

Maintain MCP Unity?

For maintainers

HVTrust scores MCP Unity 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 17Grade 2Listed 1HVTrust 1Scorecard 1Surface 1
2026-09-08
Rank Moved
Rank dropped 16 spots (#906 → #922)
2026-09-07
Rank Moved
Rank dropped 40 spots (#866 → #906)
2026-09-06
Rank Moved
Rank dropped 14 spots (#852 → #866)
2026-09-05
Rank Moved
Rank dropped 61 spots (#791 → #852)
2026-09-04
Grade Changed
Trust grade C → D
2026-09-04
Rank Moved
Rank dropped 58 spots (#733 → #791)
2026-09-03
Rank Moved
Rank dropped 48 spots (#685 → #733)
2026-09-02
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none
2026-09-02
Rank Moved
Rank dropped 52 spots (#633 → #685)
2026-09-01
Rank Moved
Rank dropped 30 spots (#603 → #633)
2026-08-31
Rank Moved
Rank dropped 30 spots (#573 → #603)
2026-08-29
Rank Moved
Rank dropped 31 spots (#536 → #567)
2026-08-27
Rank Moved
Rank dropped 16 spots (#511 → #527)
2026-08-26
Scorecard Added
OSSF Scorecard: 3.2/10
2026-08-26
Grade Changed
Trust grade D → C
2026-08-26
Rank Moved
Rank rose 413 spots (#924 → #511)
2026-08-26
HVTrust Changed
HVTrust up 29.6pts (23.0 → 52.6)
2026-08-23
Rank Moved
Rank dropped 22 spots (#893 → #915)
2026-08-19
Rank Moved
Rank dropped 11 spots (#883 → #894)
2026-08-17
Rank Moved
Rank rose 11 spots (#895 → #884)
2026-08-16
Rank Moved
Rank dropped 26 spots (#869 → #895)
2026-08-13
Rank Moved
Rank dropped 14 spots (#861 → #875)
2026-08-10
Newly Listed
First tracked at rank #865

Embed Badge Badge guide for maintainers →

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