physbox-mcp@0.74.0
VERIFIED· not startedPublisher claims: "PhysBox: MCP - Server for local simulation apps" 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
- no credential variables read in the code
- Where it talks to
- physbox.io (its own)
- What we saw when it ran
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable and talks to physbox.io, its own; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 0.71.0
vet-skills diff physbox-mcp 0.71.0 0.74.0In the sandbox, this version reached for nothing 0.71.0 did not. Compared from the two recorded runs, not from source.
0.71.0 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
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-22 and scored it 86/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
…stop: soft-reset the controller and stop the spindle, at once. Never gated, and never refused for any reason.\n\nThis is the one to reach for the moment something looks wro…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.… how many steps it failed on; physics_run_headless returns them as warnings. api.log output is in physics_run_headless `logs` and physics_get_telemetry `scriptLogs`; api.s…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…ncy stop: soft-reset the controller and kill the beam, at once. Never gated and never refused.\n\nReach for this the moment something looks wrong — a cut in the wrong place…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct."DO NOT DELIBERATE ABOUT AN E-STOP. If the user says stop, or something looks wrong, call circuit_machine_estop first and work out what happened afterwards. It is never gated and never refused.",Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.… or actuator name is a warning too, naming what the model has. `logs` is the api.log output [{ t, body, msg }], oldest first: the last 200 lines, with `logsDropped` counti…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.`mcp-docs.json` — the thing both apps' CLAUDE.md tells them to edit — wasFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.@mcp.tool(description=get_doc(etch_docs, "etch_machine_estop", "Emergency stop: soft-reset the controller and kill the beam"))Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.…ing.", "etch_machine_estop": "Emergency stop: soft-reset the controller and kill the beam, at once. Never gated and never refused.\n\nReach for this the moment s…Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.exec(compile(ast.Module(body=[fn], type_ignores=[]), str(SERVER), "exec"), ns)Fix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.exec(compile(ast.Module(body=body, type_ignores=[]), str(SERVER), "exec"), ns)Fix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.# NTFS a chmod cannot clear the group/other bits, so only assert the mode whereFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.… stop: soft-reset the controller and stop the spindle, at once. Never gated and never refused.\n\nReach for this the moment something looks wrong — a cut in the wrong place…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.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
Not checked against OSV yet; the weekly check has not reached this version.