Robloxstudio Mcp Remake MCP Server

robloxstudio-mcp-remake npm v1.1.4

Published by qqww2w2k — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
B
87/100
Last scanned get badge →
Trust
B · 87/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
B Why this grade threat 94 − adoption risk = 87/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 6.3 = 94. What the published surface and source actually contain:

PointsWhat was foundCategory
−6.3 Untrusted input concatenated into a command sink MTC-SRC-009 injection

2. Client adoption risk — 94 − 7 = 87. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 21

high Tool "run_tests" exposes command/code executionMTC-CAP-001

Tool "run_tests" appears to run shell commands or evaluate code (parameter "script"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool run_tests

high Tool "map_dependencies" exposes command/code executionMTC-CAP-001

Tool "map_dependencies" appears to run shell commands or evaluate code (parameter "script"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool map_dependencies

high Tool "find_variable_leaks" exposes command/code executionMTC-CAP-001

Tool "find_variable_leaks" appears to run shell commands or evaluate code (parameter "script"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool find_variable_leaks

high Tool "insert_comments" exposes command/code executionMTC-CAP-001

Tool "insert_comments" appears to run shell commands or evaluate code (parameter "script"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool insert_comments

high Tool "generate_script" exposes command/code executionMTC-CAP-001

Tool "generate_script" appears to run shell commands or evaluate code (parameter "script"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool generate_script

high Tool "build_context" exposes command/code executionMTC-CAP-001

Tool "build_context" appears to run shell commands or evaluate code (parameter "script"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool build_context

high Shell/command execution in server code (dist/index.js)MTC-SRC-002

In the server's implementation (`dist/index.js:7`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ; import { exec } from "child_process"; import path3 from "path"; import { fileURLToPath as fileURLToPath3 } from "url";

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/index.js

medium Hardcoded egress to an external endpoint (dist/index.js)MTC-SRC-003

In the server's implementation (`dist/index.js:3671`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const csrfRes = await fetch("https://auth.roblox.com/v2/logout", { method: "POST", headers: { "Cookie": `.

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/index.js

medium Untrusted input concatenated into a command sink (dist/index.js)MTC-SRC-009

In the server's implementation (`dist/index.js:6401`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: en" : "xdg-open"; exec(`${startCmd} "" "${dashboardUrl}"`, (err) => { if (err) console.error("Fa

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/index.js

medium Unconstrained command parameter "script_path" on "run_tests"MTC-CAP-006

Tool "run_tests" takes a command-shaped parameter "script_path" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool run_tests · inputSchema.properties.script_path

medium Unconstrained command parameter "script_path" on "map_dependencies"MTC-CAP-006

Tool "map_dependencies" takes a command-shaped parameter "script_path" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool map_dependencies · inputSchema.properties.script_path

medium Unconstrained command parameter "script_path" on "find_variable_leaks"MTC-CAP-006

Tool "find_variable_leaks" takes a command-shaped parameter "script_path" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool find_variable_leaks · inputSchema.properties.script_path

medium Unconstrained command parameter "script_path" on "insert_comments"MTC-CAP-006

Tool "insert_comments" takes a command-shaped parameter "script_path" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool insert_comments · inputSchema.properties.script_path

medium Unconstrained command parameter "script_name" on "generate_script"MTC-CAP-006

Tool "generate_script" takes a command-shaped parameter "script_name" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool generate_script · inputSchema.properties.script_name

medium Unconstrained command parameter "script_path" on "build_context"MTC-CAP-006

Tool "build_context" takes a command-shaped parameter "script_path" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool build_context · inputSchema.properties.script_path

low Mutating tool "run_tests" declares no destructiveHintMTC-CAP-005

Tool "run_tests" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool run_tests

low Mutating tool "map_dependencies" declares no destructiveHintMTC-CAP-005

Tool "map_dependencies" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool map_dependencies

low Mutating tool "find_variable_leaks" declares no destructiveHintMTC-CAP-005

Tool "find_variable_leaks" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool find_variable_leaks

low Mutating tool "insert_comments" declares no destructiveHintMTC-CAP-005

Tool "insert_comments" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool insert_comments

low Mutating tool "generate_script" declares no destructiveHintMTC-CAP-005

Tool "generate_script" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool generate_script

low Mutating tool "build_context" declares no destructiveHintMTC-CAP-005

Tool "build_context" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool build_context

Tools 96

Each tool and what it can reach — statically extracted from the published source.

  • build_contextruns code / shell
  • find_variable_leaksruns code / shell
  • generate_scriptruns code / shell
  • insert_commentsruns code / shell
  • map_dependenciesruns code / shell
  • run_testsruns code / shell
  • add_tagno sensitive capability
  • analyze_performanceno sensitive capability
  • auto_placeno sensitive capability
  • batch_executeno sensitive capability
Show 86 more tools ↓
  • build_cutsceneno sensitive capability
  • build_libraryno sensitive capability
  • build_uino sensitive capability
  • bulk_get_scriptsno sensitive capability
  • bulk_set_propertiesno sensitive capability
  • capture_screenshotno sensitive capability
  • capture_uino sensitive capability
  • capture_viewportno sensitive capability
  • check_collisionsno sensitive capability
  • check_ui_designno sensitive capability
  • control_audio_animationno sensitive capability
  • control_lightingno sensitive capability
  • control_selectionno sensitive capability
  • create_buildno sensitive capability
  • create_objectno sensitive capability
  • delete_attributeno sensitive capability
  • delete_objectno sensitive capability
  • delete_script_linesno sensitive capability
  • diff_instancesno sensitive capability
  • edit_script_linesno sensitive capability
  • execute_luauno sensitive capability
  • export_buildno sensitive capability
  • fix_namingno sensitive capability
  • generate_buildno sensitive capability
  • generate_terrainno sensitive capability
  • generate_test_reportno sensitive capability
  • get_asset_detailsno sensitive capability
  • get_asset_thumbnailno sensitive capability
  • get_attributeno sensitive capability
  • get_attributesno sensitive capability
  • get_buildno sensitive capability
  • get_class_infono sensitive capability
  • get_file_treeno sensitive capability
  • get_instance_childrenno sensitive capability
  • get_instance_children_pathno sensitive capability
  • get_instance_propertiesno sensitive capability
  • get_place_infono sensitive capability
  • get_playtest_outputno sensitive capability
  • get_project_structureno sensitive capability
  • get_script_sourceno sensitive capability
  • get_selectionno sensitive capability
  • get_servicesno sensitive capability
  • get_taggedno sensitive capability
  • get_tagsno sensitive capability
  • get_tree_pathno sensitive capability
  • get_ui_templatesno sensitive capability
  • grep_scriptsno sensitive capability
  • history_controlno sensitive capability
  • import_buildno sensitive capability
  • import_sceneno sensitive capability
  • insert_assetno sensitive capability
  • insert_script_linesno sensitive capability
  • list_libraryno sensitive capability
  • manage_backupsno sensitive capability
  • manage_datastoreno sensitive capability
  • manage_placesno sensitive capability
  • mass_create_objectsno sensitive capability
  • mass_duplicateno sensitive capability
  • mass_get_propertyno sensitive capability
  • mass_set_propertyno sensitive capability
  • mirror_instancesno sensitive capability
  • monitor_remotesno sensitive capability
  • paint_surfacesno sensitive capability
  • preview_assetno sensitive capability
  • redono sensitive capability
  • remove_tagno sensitive capability
  • roblox_studio_workflowno sensitive capability
  • scan_anticheatno sensitive capability
  • search_assetsno sensitive capability
  • search_by_propertyno sensitive capability
  • search_filesno sensitive capability
  • search_materialsno sensitive capability
  • search_objectsno sensitive capability
  • set_attributeno sensitive capability
  • set_propertyno sensitive capability
  • set_script_sourceno sensitive capability
  • simulate_physicsno sensitive capability
  • smart_duplicateno sensitive capability
  • snap_to_gridno sensitive capability
  • start_playtestno sensitive capability
  • stop_playtestno sensitive capability
  • sync_projectno sensitive capability
  • sync_project_enhancedno sensitive capability
  • track_changesno sensitive capability
  • undono sensitive capability
  • validate_pathfindingno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.1.4 latest B 87/100 21 1.9.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: B · 87/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/robloxstudio-mcp-remake/badge.svg)](https://mcptrustchecker.com/registry/robloxstudio-mcp-remake)
HTML
<a href="https://mcptrustchecker.com/registry/robloxstudio-mcp-remake"><img src="https://mcptrustchecker.com/registry/robloxstudio-mcp-remake/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/robloxstudio-mcp-remake/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan robloxstudio-mcp-remake --online

Use the free API → How scoring works

More in Gaming & Entertainment