MCP Safety Board · server report · November 2026
AnkleBreaker-Studio/unity-mcp-server
C
72 / 100
Grade C · ★ 545 · JavaScript checked by hand
How the score was worked out
| Check | What was found | Points |
|---|---|---|
| Risky tools labelled | 9 of 9 tools whose name or description suggests delete, write or run declare neither destructiveHint nor readOnlyHint. −2 each. | −18 |
| Tools with any label | 0 of 80 tools (0%) carry any annotation; fewer than half. | −10 |
| README install command | The README has no npx / bunx / uvx / pnpm dlx launch command, so there is nothing to pin. | 0 |
| Committed config | No committed MCP config with an unpinned package, a moving tag, a broad filesystem root, a privileged docker server or plain http. | 0 |
| Score | 100 minus the penalties above (never below 0). | 72 |
Changes that would raise this grade
- +18Label the 9 tools that delete, write or run: add destructiveHint (or readOnlyHint) to their annotations. Alone, this gives 90 (A).
- +10Add annotations to 40 more tools so at least half of all 80 tools are labelled (labelling the risky tools above counts too). Alone, this gives 82 (B).
Doing all of these gives 100 (A).
What was checked
- Commit checked
a669788cd367- Repository
- github.com/AnkleBreaker-Studio/unity-mcp-server
- Tools found
- 80, of which 0 carry any label (0%)
- Risky tools
- 9, of which 0 labelled
- README install
- no npx/uvx snippet
- Last push
- 2026-10-23
Static reading of this one commit. No code was installed or run. This is a hygiene grade, not a security audit.
Maintainer?
Fixed something, or think a count is wrong? Request a re-check (opens a GitHub issue). Re-checks run on the latest commit.
README badge
[](https://mcp-safety-board.pages.dev/s/anklebreaker-studio--unity-mcp-server.html)Want a written review of your agent's tools and permissions?
48-hour written review. Which tools your agent can call, what each one can change, which need a confirmation step, and what to lock down first. Send a message to start.