Unitymcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Unitymcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
ProjectM QA MCP is a Unity Package Manager package that installs a small Unity Editor command bridge and ships a bundled Node MCP server.
The package is intentionally ProjectM-focused. It avoids the long-lived WebSocket bridge used by general Unity MCP packages and uses request/response JSON files under .codex/unity-commands.
Use Unity Package Manager with a Git URL:
{
"dependencies": {
"com.nx3games.projectm.qa-mcp": "https://github.com/chdnl0420-svg/UnityMCP.git"
}
}For local development, add this folder as a local package:
{
"dependencies": {
"com.nx3games.projectm.qa-mcp": "file:D:/Project/UnityMCP"
}
}Add a server entry to C:\Users\NX3GAMES\.codex\config.toml. Adjust the args path to the installed package location.
[mcp_servers.projectm-qa-mcp]
command = "node"
args = ['D:\Project\UnityMCP\Server~\build\index.js']
startup_timeout_sec = 120
[mcp_servers.projectm-qa-mcp.env]
PROJECTM_UNITY_PATH = 'C:\Program Files\Unity\Hub\Editor\2022.3.76f1\Editor\Unity.exe'
PROJECTM_DEFAULT_PROJECT_PATH = 'C:\Project\CLIENT_KSH_ASIA_L\client\ProjectM'
PROJECTM_COMMAND_ROOT = 'C:\Project\CLIENT_KSH_ASIA_L\client\ProjectM\.codex\unity-commands'cd D:\Project\UnityMCP\Server~
npm install
npm test
npm run buildThe generated MCP server entrypoint is:
Server~/build/index.jsunity_status must return real JSON data, not just a connection signal. Editor commands must write response JSON with success, command, elapsedMs, logs, outputs, and error. Test tools parse Unity Test Framework XML and expose failure counts. Screenshot tools verify that a PNG exists and has non-zero size.
If Unity does not answer a command, inspect:
<ProjectM>/.codex/unity-commands/requests
<ProjectM>/.codex/unity-commands/responses
<ProjectM>/.codex/unity-commands/processed
%LOCALAPPDATA%/Unity/Editor/Editor.logUse unity_kill_stale without kill=true first. It reports candidates and reasons before termination is requested.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.