# playproof (npm · playproof) See and playtest browser games: frame-by-frame motion, crash hunting, phone layouts, frame pacing. - Trust score: 83/100 (high trust) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-04 ## Components - npm · `playproof`: 83/100 (this document), [markdown](https://verifymcp.io/servers/emirhanozl-playproof/playproof.md), [page](https://verifymcp.io/servers/emirhanozl-playproof/playproof) ## Channel facts - Registry: `npm` - Package: `playproof` - Version: `0.3.2` - Transport: `stdio` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-04. - **Supply Chain Security**: 100/100 - No malware found by supply-chain analysis. - No known CVEs affecting this package version or its production dependencies. - No install/post-install scripts declared. - 0 of 1 dependencies flagged as unhealthy. - **Provenance & Transparency**: 97/100 - Source repository is publicly reachable at the declared URL. - Cryptographically verified build provenance (signed, bound to EmirhanOzl/playproof). - Clear OSI-approved license (MIT). - Actively maintained (last published 12 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 55/100 - AI-judged instruction clarity (good). - Context-footprint check failed: tool/resource definitions use about 2417 tokens (~402/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 43/100 - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### How do I install the playproof MCP server? playproof runs locally as an npm package, launched with npx -y playproof. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add emirhanozl-playproof -- npx -y playproof ``` ### Cursor ```json { "mcpServers": { "emirhanozl-playproof": { "command": "npx", "args": [ "-y", "playproof" ] } } } ``` ### VS Code ```json { "servers": { "emirhanozl-playproof": { "command": "npx", "args": [ "-y", "playproof" ] } } } ``` ### Codex ```bash codex mcp add emirhanozl-playproof -- npx -y playproof ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "emirhanozl-playproof": { "type": "local", "command": [ "npx", "-y", "playproof" ], "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add emirhanozl-playproof --command npx --arg -y --arg playproof ``` ### Hermes ```yaml mcp_servers: emirhanozl-playproof: command: "npx" args: ["-y", "playproof"] ``` ### Netclaw ```json { "McpServers": { "emirhanozl-playproof": { "Transport": "stdio", "Command": "npx", "Arguments": [ "-y", "playproof" ] } } } ``` ### Vellum ```bash assistant mcp add emirhanozl-playproof -t stdio -c npx -a -y playproof ``` ### Other ```json { "mcpServers": { "emirhanozl-playproof": { "command": "npx", "args": [ "-y", "playproof" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-03 (score 83, +1) No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-31 (score 82, +1) No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-29 (score 81, +1) No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-27 (score 80, +3) - [functional improvement] Stability: unverified → 0.17 ### 2026-10-23 (score 77, +15) - [security improvement] Malware scan: unverified → pass ### 2026-10-22 (score 62) First indexed and scored. ## MCP tools (6) ### `frames` (~576 tokens) Film an animation frame by frame Runs the game on a virtual clock, optionally performs steps to trigger something, then films it frame by frame. Returns a contact sheet (tiles with frame number and time, dashed boxes around what moved, a bar per frame of how much changed) and an onion-skin image (the whole motion ghosted into one picture), plus flagged sudden jumps, one-frame flicker and stalls. Runs are deterministic: pass compare = the folder of an earlier run to see exactly what a code change did. Input parameters: - `area` (string): CSS selector of the game area (default: the largest canvas) - `compare` (string): Output folder of an earlier frames run to compare with - `device` (string): Device to emulate: "iPhone 15", "Pixel 8", "desktop" (default) or "390x844@3 mobile" - `duration` (string): How long to film, e.g. 800ms or 1.5s (default 1s) - `fps` (number): Tiles per second on the sheet (default: fit about 24 tiles) - `ready` (string): JavaScript expression that is true once the game has loaded - `scenario` (string): Name of a scenario in playproof.config.json: supplies steps, duration, zoom and device - `steps` (string): Steps separated by ";". Steps (separate with ";" or new lines, "#" starts a comment line): wait