Isaacsim MCP Server

isaacsim-mcp-server PyPI v0.5.2

Published by whats2000 — 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.

Control NVIDIA Isaac Sim robotics simulator through MCP -- 41 tools for scene management, robot control, sensors, and simulation

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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
Minimal
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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/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 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. 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
−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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 42

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

  • apply_materialno sensitive capability
  • capture_imageno sensitive capability
  • clear_sceneno sensitive capability
  • clone_objectno sensitive capability
  • create_action_graphno sensitive capability
  • create_camerano sensitive capability
  • create_lidarno sensitive capability
  • create_lightno sensitive capability
  • create_materialno sensitive capability
  • create_objectno sensitive capability
Show 32 more tools ↓
  • create_physics_sceneno sensitive capability
  • create_robotno sensitive capability
  • delete_objectno sensitive capability
  • edit_action_graphno sensitive capability
  • execute_scriptno sensitive capability
  • generate_3dno sensitive capability
  • get_isaac_logsno sensitive capability
  • get_joint_configno sensitive capability
  • get_joint_positionsno sensitive capability
  • get_lidar_point_cloudno sensitive capability
  • get_physics_stateno sensitive capability
  • get_prim_infono sensitive capability
  • get_robot_infono sensitive capability
  • get_scene_infono sensitive capability
  • get_simulation_stateno sensitive capability
  • import_urdfno sensitive capability
  • list_available_robotsno sensitive capability
  • list_environmentsno sensitive capability
  • list_primsno sensitive capability
  • load_environmentno sensitive capability
  • load_usdno sensitive capability
  • modify_lightno sensitive capability
  • pause_simulationno sensitive capability
  • play_simulationno sensitive capability
  • refresh_robot_libraryno sensitive capability
  • reload_scriptno sensitive capability
  • search_usdno sensitive capability
  • set_joint_positionsno sensitive capability
  • set_physics_paramsno sensitive capability
  • step_simulationno sensitive capability
  • stop_simulationno sensitive capability
  • transform_objectno 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
v0.5.2 latest A 99/100 0 1.12.1 2026-07-27

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: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/isaacsim-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/isaacsim-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/isaacsim-mcp-server"><img src="https://mcptrustchecker.com/registry/isaacsim-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/isaacsim-mcp-server/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 isaacsim-mcp-server --online --registry pypi

Use the free API → How scoring works

More in Data Science & ML