io.github.whats2000/isaacsim-mcp-server

What we checked

Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.

• Injection surface

  pass25% of grade

  Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

  Scanned 192 text field(s); no instruction-injection patterns found. PASS = no static red flag. A server can serve different tool descriptions at runtime (the rug-pull class), which static scanning cannot see.

• Supply chain

  pass25% of grade

  Package provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.

  repository linkage verified

• Credential hygiene

  pass15% of grade

  How the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.

  No hardcoded secrets, secret-shaped tool parameters, or leaked keys found. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

• Permission scope

  unscannable15% of grade

  Declared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.

  No source files, package.json, or pyproject were fetched; cannot infer capability scope.

• Version behavior

  fail10% of grade

  Diff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).

  vs prior 0.6.0 (patch bump): new tool "get_scene_info" appeared; new tool "create_physics_scene" appeared; new tool "clear_scene" appeared; new tool "list_prims" appeared; new tool "get_prim_info" appeared; new tool "list_environments" appeared; new tool "load_environment" touches a sensitive surface (email/exec/net/fs); new tool "create_object" appeared; new tool "delete_object" touches a sensitive surface (email/exec/net/fs); new tool "transform_object" appeared; new tool "clone_object" appeared; new tool "create_light" appeared; new tool "modify_light" appeared; new tool "create_robot" touches a sensitive surface (email/exec/net/fs); new tool "list_available_robots" appeared; new tool "refresh_robot_library" appeared; new tool "get_robot_info" appeared; new tool "set_joint_positions" appeared; new tool "get_joint_positions" touches a sensitive surface (email/exec/net/fs); new tool "create_camera" appeared; new tool "capture_image" touches a sensitive surface (email/exec/net/fs); new tool "create_lidar" appeared; new tool "get_lidar_point_cloud" touches a sensitive surface (email/exec/net/fs); new tool "create_material" appeared; new tool "apply_material" appeared; new tool "import_urdf" touches a sensitive surface (email/exec/net/fs); new tool "load_usd" touches a sensitive surface (email/exec/net/fs); new tool "search_usd" appeared; new tool "generate_3d" touches a sensitive surface (email/exec/net/fs); new tool "play_simulation" appeared; new tool "pause_simulation" appeared; new tool "stop_simulation" touches a sensitive surface (email/exec/net/fs); new tool "step_simulation" touches a sensitive surface (email/exec/net/fs); new tool "set_physics_params" appeared; new tool "get_isaac_logs" touches a sensitive surface (email/exec/net/fs); new tool "get_simulation_state" appeared; new tool "get_physics_state" appeared; new tool "get_joint_config" appeared; new tool "execute_script" touches a sensitive surface (email/exec/net/fs); new tool "reload_script" touches a sensitive surface (email/exec/net/fs); new tool "create_action_graph" touches a sensitive surface (email/exec/net/fs); new tool "edit_action_graph" touches a sensitive surface (email/exec/net/fs).

• Transport config

  unscannable10% of grade

  Remote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.

  local stdio server: no remote transport or auth surface, and no phone-home/telemetry signal found in source. Absence of transport findings is NOT a safety guarantee — phone-home hosts can be constructed at runtime and defeat static analysis.