Back to MCP Trust Indexm8ven
B
Caution
89/100
3 days ago

Blender

BlenderMCP connects Blender to Claude AI through the Model Context Protocol (MCP), allowing Claude to directly interact with and control Blender. This integration enables prompt assisted 3D modeling, scene creation, and manipulation.

→ ahujasid/blender-mcp· listed on mcp_so

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

ahujasid

Source: mcp.so · also listed on PulseMCP, modelscope, github_topic

Maintenance & responsiveness
as of 2026-08-19
Issue response: median 2d
Issues closed (90d): 69 · 11 open
Releases (90d): none
Contributor retention: 1/6 stayed · 14 active
Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

mcp.soPulseMCPmodelscopeGitHub

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: SUPABASE_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configBLENDER_HOSTlocalhost Host address for Blender socket server
configBLENDER_PORT9876 Port number for Blender socket server
configSUPABASE_URL
🔐 secretSUPABASE_KEY
configBLENDER_USER_ADDONS
configBLENDERMCP_ADDONS_DIROptional: uvx blender-mcp addon-paths lists detected Blender addons folders. Override the destination with =/path/to/scripts/addons.
configXDG_CONFIG_HOME
configXDG_DATA_HOME
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

44/44 tools missing one or more hints — get_addon_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); disable_telemetry (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_scene_info (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +41 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — get_viewport_screenshot deletes at line 491 (os.remove(temp_path))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tests exist

No test files found

Add tests that exercise each declared tool.

Shell command execution

2 child_process/subprocess calls in production code — runs shell commands (addon.py:1156, src/blender_mcp/bundled/addon.py:1156)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/ahujasid-blender-mcp-12keew?variant=verified)](https://m8ven.ai/mcp/ahujasid-blender-mcp-12keew)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 2997140088e98bcf1e858f94bf9550c05757b7f6
code hash: 44bb6c0e43aaf80fd4dfc3541645ce0deec39cf7ce0e52f359b2cd748951add1
verified: 8/16/2026, 1:06:42 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client