roblox-studio-mcp@0.3.0
CAUTION· not startedPublisher claims: "A lightweight, dependency-free Python client for MCP (Model Context Protocol) servers, with built-in convenience for the Roblox Studio 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: Caution 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
- no vendor host named in the codeAlso roblox.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 under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; 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.
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-16 and scored it 79/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: References a credential file in the home directory; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
the body called the forced kill immediately and used ``grace_seconds``Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# inside the root pointing at ~/.ssh/id_rsa passes an abspath check untouched.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.proc = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.proc = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.wrong kill costs the user's unsaved work in an unrelated process. WitnessesFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# kill target could not be corroborated* from the ordinaryFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# path would rather print one line than guess a PID and kill it.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.The two are not equivalent in strictness - ``kill -0`` succeeds for aFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.confidently-wrong kill this resolver exists to prevent.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.reached ``kill -9``.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# forced kill is the caller's job, not this function's.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# inside the root pointing at ~/.ssh/id_rsa passes an abspath check untouched.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run(["kill", "-9", str(int(pid))], capture_output=True, timeout=30)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# Skip one malformed line; don't kill all pending requests.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.POSIX: ``kill -9``.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.#: How long a graceful stop request is given before the forced kill follows.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.proc = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out."""Whether ``pid`` is still running. Windows uses CIM, macOS uses ``kill -0``.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."""Register the shutdown kill for one connected client, once per client."""Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."""Synchronously kill the proxy child if shutdown caught it alive.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.The kill alone stops the orphan but not the noise: ``__del__`` still callsFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."the kill target could not be corroborated by any "Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.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.
What would make this Verified
1 point to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim bdidk235: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- References a credential file in the home directory≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.