3dsmax MCP Server

3dsmax-mcp PyPI v1.5.1

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

MCP server for AI agents to control Autodesk 3ds Max

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/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 − 7 = 93. 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 5

high Sensitive-source and external-sink co-existMTC-FLOW-004

Tools that read sensitive data ([inspect_object, get_object_properties]) and tools that can send data out ([create_shell_material]) are exposed together. An agent can move private data to the sink.

Evidence: sources [inspect_object, get_object_properties] → sinks [create_shell_material]

Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.

Location: flow inspect_object → create_shell_material

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

Tool "create_shell_material" appears to run shell commands or evaluate code (keyword "shell" in tool name). 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 create_shell_material

high Shell/command execution in server code (install.py)MTC-SRC-002

In the server's implementation (`install.py:157`): 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: l /F "{path}"' subprocess.run( ["powershell", "-Command", f'Start-Process -FilePath

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 install.py

high Shell/command execution in server code (uninstall.py)MTC-SRC-002

In the server's implementation (`uninstall.py:43`): 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: l /F "{path}"' subprocess.run( ["powershell", "-Command", f'Start-Process -FilePath

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 uninstall.py

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

Tool "create_shell_material" 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 create_shell_material

Tools 141

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

  • create_shell_materialruns code / shell
  • get_object_propertiesreads sensitive data
  • inspect_objectreads sensitive data
  • add_controller_targetno sensitive capability
  • add_data_channelno sensitive capability
  • add_dc_script_operatorno sensitive capability
  • add_modifierno sensitive capability
  • add_tyflow_collisionno sensitive capability
  • add_tyflow_eventno sensitive capability
  • analyze_node_orientationno sensitive capability
Show 131 more tools ↓
  • assign_controllerno sensitive capability
  • assign_materialno sensitive capability
  • backup_material_libraryno sensitive capability
  • batch_file_infono sensitive capability
  • batch_rename_objectsno sensitive capability
  • batch_replace_materialsno sensitive capability
  • boolean_operationno sensitive capability
  • build_floor_planno sensitive capability
  • capture_multi_viewno sensitive capability
  • capture_screenno sensitive capability
  • capture_tyflow_editorno sensitive capability
  • capture_viewportno sensitive capability
  • chat_clearno sensitive capability
  • chat_reloadno sensitive capability
  • chat_statusno sensitive capability
  • clone_objectsno sensitive capability
  • collapse_modifier_stackno sensitive capability
  • connect_tyflow_eventsno sensitive capability
  • connect_tyflow_operatorno sensitive capability
  • create_material_from_texturesno sensitive capability
  • create_objectno sensitive capability
  • create_texture_mapno sensitive capability
  • create_tyflowno sensitive capability
  • create_tyflow_presetno sensitive capability
  • delete_effectno sensitive capability
  • delete_objectsno sensitive capability
  • disconnect_tyflow_operatorno sensitive capability
  • discover_plugin_classesno sensitive capability
  • discover_plugin_surfaceno sensitive capability
  • draw_splineno sensitive capability
  • edit_verticesno sensitive capability
  • execute_maxscriptno sensitive capability
  • get_bridge_statusno sensitive capability
  • get_camera_sequenceno sensitive capability
  • get_dependenciesno sensitive capability
  • get_effectsno sensitive capability
  • get_hierarchyno sensitive capability
  • get_instancesno sensitive capability
  • get_material_libraryno sensitive capability
  • get_material_slotsno sensitive capability
  • get_materialsno sensitive capability
  • get_plugin_capabilitiesno sensitive capability
  • get_plugin_manifestno sensitive capability
  • get_railclone_style_graphno sensitive capability
  • get_session_contextno sensitive capability
  • get_state_setsno sensitive capability
  • get_tyflow_graphno sensitive capability
  • get_tyflow_infono sensitive capability
  • get_tyflow_particle_countno sensitive capability
  • get_tyflow_particlesno sensitive capability
  • get_wired_paramsno sensitive capability
  • harvest_tyflow_manifestno sensitive capability
  • inspect_controllerno sensitive capability
  • inspect_data_channelno sensitive capability
  • inspect_material_networkno sensitive capability
  • inspect_max_fileno sensitive capability
  • inspect_modifier_propertiesno sensitive capability
  • inspect_plugin_classno sensitive capability
  • inspect_plugin_constructorno sensitive capability
  • inspect_plugin_instanceno sensitive capability
  • inspect_propertiesno sensitive capability
  • inspect_track_viewno sensitive capability
  • introspect_classno sensitive capability
  • introspect_instanceno sensitive capability
  • introspect_oslno sensitive capability
  • invoke_toolno sensitive capability
  • isolate_and_capture_selectedno sensitive capability
  • keyframe_tracksno sensitive capability
  • learn_scene_patternsno sensitive capability
  • list_dc_operatorsno sensitive capability
  • list_dc_presetsno sensitive capability
  • list_plugin_classesno sensitive capability
  • list_tyflow_operator_typesno sensitive capability
  • list_tyflow_operatorsno sensitive capability
  • list_wireable_paramsno sensitive capability
  • load_dc_presetno sensitive capability
  • main_threadno sensitive capability
  • make_modifier_uniqueno sensitive capability
  • manage_data_channel_stackno sensitive capability
  • manage_groupsno sensitive capability
  • manage_layersno sensitive capability
  • manage_sceneno sensitive capability
  • manage_selection_setsno sensitive capability
  • map_class_relationshipsno sensitive capability
  • mcg_get_contextno sensitive capability
  • mcg_inspect_graphno sensitive capability
  • mcg_list_graphsno sensitive capability
  • mcg_search_operatorsno sensitive capability
  • merge_from_fileno sensitive capability
  • modify_tyflow_operatorno sensitive capability
  • my_toolno sensitive capability
  • palette_laydownno sensitive capability
  • query_sceneno sensitive capability
  • refresh_plugin_manifestno sensitive capability
  • remove_modifierno sensitive capability
  • remove_tyflow_elementno sensitive capability
  • render_automationsno sensitive capability
  • render_sceneno sensitive capability
  • replace_materialno sensitive capability
  • replicate_materialno sensitive capability
  • reset_tyflow_simulationno sensitive capability
  • run_tool_smokeno sensitive capability
  • scatter_forest_packno sensitive capability
  • search_max_filesno sensitive capability
  • select_objectsno sensitive capability
  • send_to_chatno sensitive capability
  • set_controller_propsno sensitive capability
  • set_data_channel_operatorno sensitive capability
  • set_material_propertiesno sensitive capability
  • set_material_propertyno sensitive capability
  • set_modifier_propertyno sensitive capability
  • set_modifier_stateno sensitive capability
  • set_object_propertyno sensitive capability
  • set_parentno sensitive capability
  • set_sub_materialno sensitive capability
  • set_texture_map_propertiesno sensitive capability
  • set_tyflow_physxno sensitive capability
  • set_tyflow_shapeno sensitive capability
  • set_tyflow_wiring_ledgerno sensitive capability
  • set_visibilityno sensitive capability
  • smart_importno sensitive capability
  • toggle_effectno sensitive capability
  • transform_objectno sensitive capability
  • tyflow_apply_patchno sensitive capability
  • tyflow_event_censusno sensitive capability
  • undo_lastno sensitive capability
  • unwire_paramsno sensitive capability
  • walk_referencesno sensitive capability
  • watch_sceneno sensitive capability
  • wire_paramsno sensitive capability
  • write_osl_shaderno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

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.5.1 latest A 93/100 5 1.13.0 2026-08-25

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

Use the free API → How scoring works

More in Productivity & Workflow