Unreal MCP
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to control Unreal Engine through the native C++ Automation Bridge plugin. Built with TypeScript and C++.
Is Unreal MCP safe? Promising trust profile, but some evidence still deserves review.
Compare Unreal MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Unreal MCP scores 62.5/100 (Grade C), ranked #631 of 1374 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.4/10; recent commits are unsigned; last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →
How Unreal MCP could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 77.2 B · #135 of 778
- Raise the OSSF Scorecard from 5.4 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +7.4 → 69.9 B · #225 of 778
- Sign every commit0% signed today +5.0 → 67.5 B · #256 of 778
Chain of custody
Scanners check what the code says. This traces who ships Unreal MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Unsigned
github.com/ChiR24/Unreal_mcp, MIT, last pushed 2026-11-09. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 5.4/10 (scanned Oct 26, 2026, refresh pending). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies9
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 0CI-Tests 10CII-Best-Practices 0Code-Review 0Contributors 3Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 9SAST 7Security-Policy 0Signed-Releases 0Token-Permissions 0Vulnerabilities 7 -
Published packages Not linked
- npm unreal-engine-mcp-server Source link isn't a GitHub repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
Changes to this chain
- 2026-08-29 OSSF Scorecard: 5.7/10
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Unreal MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Unreal MCP compares in MCP Servers
- #345 MCP Server For ISO27001 62.6 +0.1
- #346 MCP Uptime Kuma 62.5 ±0
- #347 Unreal MCP 62.5 this agent
- #348 Docling MCP 62.5 ±0
- #349 Yuque MCP Server 62.4 −0.1
Bars show each HVTrust score; the tick marks Unreal MCP’s 62.5.
Where the 62.5 comes from
HVTrust dimensions vs the MCP Servers average
62.5 / 100 · 100.0% confidenceUnreal MCP MCP Servers average (778 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 C 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
78.7 / 100Common questions about Unreal MCP
Does Unreal MCP publish package provenance?
Does Unreal MCP have an OpenSSF Scorecard?
Is Unreal MCP actively maintained?
What license does Unreal MCP use?
Are Unreal MCP'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 Unreal MCP'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 Unreal MCP?
For maintainers
HVTrust scores Unreal MCP 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/unreal-mcp)
<a href="https://hvtracker.net/agents/unreal-mcp"><img src="https://hvtracker.net/badge/unreal-mcp.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.4 · Raw JSON