Blender Copilot MCP Server

blender-copilot PyPI v1.0.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/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
Moderate
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.
A Why this grade threat 100 − adoption risk = 95/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 − 5 = 95. 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
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 55

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

  • download_polyhaven_assetingests untrusted input
  • download_sketchfab_modelingests untrusted input
  • analyze_sceneno sensitive capability
  • bake_texturesno sensitive capability
  • build_node_graphno sensitive capability
  • configure_render_settingsno sensitive capability
  • create_objectno sensitive capability
  • delete_objectno sensitive capability
  • duplicate_objectno sensitive capability
  • execute_blender_codeno sensitive capability
Show 45 more tools ↓
  • export_modelno sensitive capability
  • generate_collision_meshno sensitive capability
  • generate_hunyuan3d_modelno sensitive capability
  • generate_hyper3d_model_via_imagesno sensitive capability
  • generate_hyper3d_model_via_textno sensitive capability
  • generate_lod_chainno sensitive capability
  • generate_trellis2_modelno sensitive capability
  • get_hunyuan3d_statusno sensitive capability
  • get_hyper3d_statusno sensitive capability
  • get_node_graphno sensitive capability
  • get_object_infono sensitive capability
  • get_polyhaven_categoriesno sensitive capability
  • get_polyhaven_statusno sensitive capability
  • get_scene_infono sensitive capability
  • get_sketchfab_model_previewno sensitive capability
  • get_sketchfab_statusno sensitive capability
  • get_trellis2_statusno sensitive capability
  • get_viewport_screenshotno sensitive capability
  • import_generated_assetno sensitive capability
  • import_generated_asset_hunyuanno sensitive capability
  • import_modelno sensitive capability
  • list_node_typesno sensitive capability
  • manage_actionsno sensitive capability
  • manage_armatureno sensitive capability
  • manage_collectionsno sensitive capability
  • manage_constraintsno sensitive capability
  • manage_materialsno sensitive capability
  • manage_nlano sensitive capability
  • manage_physicsno sensitive capability
  • manage_shape_keysno sensitive capability
  • manage_weightsno sensitive capability
  • mesh_operationno sensitive capability
  • modify_objectno sensitive capability
  • poll_hunyuan_job_statusno sensitive capability
  • poll_rodin_job_statusno sensitive capability
  • render_sceneno sensitive capability
  • search_polyhaven_assetsno sensitive capability
  • search_sketchfab_modelsno sensitive capability
  • set_camerano sensitive capability
  • set_keyframeno sensitive capability
  • set_textureno sensitive capability
  • set_viewport_shadingno sensitive capability
  • transform_objectno sensitive capability
  • uv_operationno sensitive capability
  • volume_operationno 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.0.0 latest A 95/100 0 1.8.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: A · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/blender-copilot/badge.svg)](https://mcptrustchecker.com/registry/blender-copilot)
HTML
<a href="https://mcptrustchecker.com/registry/blender-copilot"><img src="https://mcptrustchecker.com/registry/blender-copilot/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/blender-copilot/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 blender-copilot --online --registry pypi

Use the free API → How scoring works

More in Developer Tools