mcpforunityserver@10.3.0
VERIFIED· not startedPublisher claims: "MCP for Unity Server: A Unity package for Unity Editor integration via the Model Context Protocol (MCP)." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
UNITY_MCP_API_KEY_CACHE_TTLUNITY_MCP_API_KEY_LOGIN_URLUNITY_MCP_API_KEY_SERVICE_TOKENUNITY_MCP_API_KEY_SERVICE_TOKEN_HEADERUNITY_MCP_API_KEY_VALIDATION_URLUNITY_MCP_INSTANCE_TOKENor--api-key-service-token-header/--api-key-service-token/--unity-instance-tokenConfiguration, not credentials: PYTEST_CURRENT_TEST, UNITY_MCP_DEFAULT_INSTANCE, UNITY_MCP_DISABLE_FOCUS_NUDGE, UNITY_MCP_ENABLE_HTTP_SERVER, UNITY_MCP_FORMAT, UNITY_MCP_HOST, UNITY_MCP_HTTP_HOST, UNITY_MCP_HTTP_PORT, UNITY_MCP_HTTP_REMOTE_HOSTED, UNITY_MCP_HTTP_URL, UNITY_MCP_INSTANCE, UNITY_MCP_NUDGE_DURATION_S, UNITY_MCP_PROJECT_SCOPED_TOOLS, UNITY_MCP_SKIP_STARTUP_CONNECT, UNITY_MCP_TELEMETRY_ENDPOINT, UNITY_MCP_TELEMETRY_TIMEOUT, UNITY_MCP_TIMEOUT, UNITY_MCP_TRANSPORT- Where it talks to
- no vendor host named in the codeAlso coplay.dev, openupm.com, unity3d.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names coplay.dev, openupm.com, unity3d.com as well as its own vendor. The guard injects UNITY_MCP_API_KEY_CACHE_TTL, UNITY_MCP_API_KEY_LOGIN_URL, UNITY_MCP_API_KEY_SERVICE_TOKEN, UNITY_MCP_API_KEY_SERVICE_TOKEN_HEADER, UNITY_MCP_API_KEY_VALIDATION_URL, UNITY_MCP_INSTANCE_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-10 and scored it 92/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for mcpforunityserver@10.3.0 as of 4d ago. This is the package itself, not its dependencies.