Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ViperMesh for Blender

MCPB · VIPERMESH-BLENDER-1.3.0.MCPB

Free Blender MCP addon for faster AI scene edits, fewer tokens and built-in scene checks.

+28 this week 38 Trust /100

Last scanned (7 hours ago)

Scores higher than 75% of MCPB servers

Category Design and Media

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 10 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 634 tokens (~57/item across 11 items; 9 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 2 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 14 Oct 26 +28
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Tool coverage: 0 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: fair functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: pass functional
  • 9 Oct 26 10

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 17 Oct 2026 · Analysed mcpb/https://github.com/Ker102/vipermesh-blender/releases/download/v1.3.0/vipermesh-blender-1.3.0.mcpb

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 9 exposed · ~476 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
bootstrap_vipermesh_session ~36

Call once at session start. Checks Blender and returns compact operating context plus the recommended next calls for one persistent MCP session.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

call_blender_tool ~36

Call one approved ViperMesh Blender command with structured parameters.

NameTypeReqDescription
namestringyes–
paramsobject––

No output schema declared.

No examples provided.

call_blender_tool_batch ~58

Run an ordered bounded sequence of approved ViperMesh Blender commands through one persistent session. Use only when intermediate observations are not needed to choose the next command.

NameTypeReqDescription
commandsarrayyes–
stopOnErrorboolean––

No output schema declared.

No examples provided.

check_blender_connection ~28

Check whether the local ViperMesh Blender addon is responding on its configured loopback socket.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_3d_guidance_document ~35

Read one approved Markdown reference from the checked-in ViperMesh agent skill.

NameTypeReqDescription
filenamestringyes–

No output schema declared.

No examples provided.

get_blender_agent_context ~26

Load the public compact ViperMesh operating rules for persistent Blender MCP sessions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_blender_tools ~42

List Blender commands available through the trusted local portable gateway, including execute_code for fallback measurement.

NameTypeReqDescription
categorystring––
querystring––

No output schema declared.

No examples provided.

run_blender_scene_stage ~155

Run one compact scene-workflow stage over the persistent Blender session. Use build, inspect_preview, and finalize as separate decision points; standalone tools remain available for repairs and unusual work.

NameTypeReqDescription
blendPathstring––
cameraNamestring––
commandsarray––
groundingTolerancenumber––
preservePresentationboolean––
presetstring––
previewPathstring––
renderPathstring––
resolutionXinteger––
resolutionYinteger––
samplesinteger––
spatialRelationsarray––
stagestringyes–
targetNamesarray––

No output schema declared.

No examples provided.

search_3d_guidance ~60

Search checked-in ViperMesh 3D tool skills and optionally the configured semantic guidance store.

NameTypeReqDescription
limitinteger––
minSimilaritynumber––
querystringyes–
sourcestring––

No output schema declared.

No examples provided.

Install

How do I install the ViperMesh for Blender MCP server?

ViperMesh for Blender ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 45f8cee90540e9f906b8e817efb6fa0a1302f8dba515522dc3682d328a90206c; the commands to do that are on this page. If it does not match, do not open it.

mcpb · vipermesh-blender-1.3.0.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

45f8cee90540e9f906b8e817efb6fa0a1302f8dba515522dc3682d328a90206c

macOS / Linux

echo "45f8cee90540e9f906b8e817efb6fa0a1302f8dba515522dc3682d328a90206c  vipermesh-blender-1.3.0.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\vipermesh-blender-1.3.0.mcpb).Hash -eq "45f8cee90540e9f906b8e817efb6fa0a1302f8dba515522dc3682d328a90206c"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

What is the ViperMesh for Blender MCP server?

ViperMesh for Blender is an MCP server listed in the public MCP registry as io.github.Ker102/vipermesh-blender. Free Blender MCP addon for faster AI scene edits, fewer tokens and built-in scene checks. This page covers its MCPB bundle (https://github.com/Ker102/vipermesh-blender/releases/download/v1.3.0/vipermesh-blender-1.3.0.mcpb).

Is the ViperMesh for Blender MCP server safe to use?

ViperMesh for Blender scores 38 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ViperMesh for Blender MCP server expose?

ViperMesh for Blender exposes 9 tools: bootstrap_vipermesh_session, check_blender_connection, list_blender_tools, call_blender_tool, call_blender_tool_batch, and 4 more. Their descriptions and schemas cost roughly 476 tokens of context every time the server is loaded.

What licence is the ViperMesh for Blender MCP server under?

ViperMesh for Blender declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.