MCP (Model Context Protocol) bridge for Unreal Engine 5 — lets AI assistants control the UE5 editor
The publisher performed an authenticated act of publication — proving control of a namespace in the official MCP registry, or appearing in a first-party catalogue an operator curates. That establishes WHO published it. It is not a security finding, and attested artifacts carry Flagged verdicts too.
2 critical findings reported by cisco-skill-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
github: https://github.com/aadeshrao123/Unreal-MCP, 60 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- unrealmcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
7 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
8 findings · 7.9s
v0.3.26
3 findings · 2.3s
v0.1.0
0 findings · 28.0s
v0.1.0
1 finding · 28.0s
vv0.3.2
Incomplete run
0 findings · 0.4s
v0.71.0
0 findings · 0.3s
v2.3.8
45 findings · 0.7s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
No report in this scan: nerlo-multi-source.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 9, 2026 | Flagged82 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·!: incompletetrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 57 findings across every scanner that examined this package. None of the 2 findings rated critical by their scanner were dismissed.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
2 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/docs/SKILL.md · reported by cisco-skill-scanner
1 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: AAK-GHA-IMMUTABLE-001 · Files: .github/workflows/release.yml · reported by agent-audit-kit
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
2 COMMAND_INJECTION_JS_CHILD_PROCESS
Files: /repo/cli/npm/install.js, /repo/cli/npm/run.js · reported by cisco-skill-scanner
1 AAK-SEC-MD-001
Files: SECURITY.md · reported by agent-audit-kit
1 AAK-SUPPLY-004
Files: pyproject.toml · reported by agent-audit-kit
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 GO-2025-3503
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2025-3563
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2025-3750
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2025-3751
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2025-3849
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2025-3956
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2025-4006
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2025-4007
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2025-4008
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2025-4009
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2025-4010
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2025-4011
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2025-4012
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2025-4013
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2025-4014
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2025-4015
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2025-4155
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2025-4175
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4337
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4340
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4341
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4342
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4403
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4601
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4602
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4603
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4864
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4865
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4869
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4870
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4918
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4946
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4947
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4970
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4971
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4976
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4977
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4980
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4981
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4982
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-4986
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-5037
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-5038
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-5039
Files: /repo/cli/go.mod · reported by osv-scanner
1 GO-2026-5856
Files: /repo/cli/go.mod · reported by osv-scanner
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 opt.nerlo-rules.nerlo-install-run-bundled-artifact
Files: /repo/CONTRIBUTING.md · reported by nerlo-install-instruction
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 YARA_code_execution_generic
Files: /repo/Source/UnrealMCPBridge/Private/EpicUnrealMCPBridge.cpp · reported by cisco-skill-scanner
Critical command injection risks identified
The artifact contains critical command injection vulnerabilities in `/repo/cli/npm/install.js` and `/repo/cli/npm/run.js`. These issues allow for shell execution through child processes. Additionally, a medium severity finding indicates a potential for code execution, and another medium finding points to a supply chain risk.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.