Houdini MCP Server (bamboovfx/houdini-mcp-codex) is an MCP server listed on the M8ven Trust Index. It scores 56 out of 100, grade D. It declares 52 tools. No publisher has claimed this listing.

D
Caution
56/100

Houdini MCP Server

Enables AI assistants to control SideFX Houdini 3D software, providing tools for scene management, node operations, rendering, and more through the Model Context Protocol.

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

⚡ 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

bamboovfx

Source: Glama

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 →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: TARGET_SUMMARY_TOKENS. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — get_node_info (line 104: params[parm.name()] = parm.eval())
// 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.
configLOG_LEVELLogging level
configHOUDINI_HOSTHoudini machine IP/hostname
configHOUDINI_PORThrpyc server port
configMCP_PORTMCP server HTTP port
configMCP_TRANSPORTTransport type (http, stdio, sse)
configHOUDINI_MCP_SEMAPHORE_LIMIT
configCLAUDE_PROXY_URL
configSUMMARIZATION_MODEL
configSUMMARIZATION_ENABLED
configAUTO_SUMMARIZE_THRESHOLD
configTARGET_SUMMARY_TOKENS
// 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

52/52 tools missing one or more hints — get_scene_info (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_node (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); execute_code (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +49 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 — execute_code deletes at line 87 (- Dangerous operation detection: Scans for patterns like hou.exit(), os.remove(), subprocess, etc.)

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.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — get_node_info (line 104: params[parm.name()] = parm.eval())

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

39/52 tools referenced in tests (75%)

Write tests that reference each tool by name so every tool has at least one test.

Tool description accuracy

get_node_info: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

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 7 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/bamboovfx/houdini-mcp-codex?variant=verified)](https://m8ven.ai/mcp/bamboovfx/houdini-mcp-codex)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 067ba757f46976ee7bf3ae96dfb83473028975cb
code hash: fa5be0a79dca798dc6d85efd8114900322d1843ccf873c3b8e266c92dde734b2
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