touchdesigner-mcp
MCP server that lets Claude drive a running TouchDesigner instance to create operators, wire them, set parameters, run arbitrary Python, and introspect the td API.
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
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
mrinalghosh
Source: Glama
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.
TD_INSTANCESMulti-instance map: name=host:port[/path],... (overrides the single-instance vars)TD_HOSTSingle-instance hostTD_PORTSingle-instance portTD_PATHHTTP path the Web Server DAT answers onTD_DEFAULT_INSTANCEWhich instance unqualified tool calls targetTD_TIMEOUTHTTP timeout in secondsTool 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
27/27 tools missing one or more hints — list_instances (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ping_all (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); exec_python (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +24 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.
Descriptions match behaviour
2 tools describe read intent but their handlers mutate — get_parameter (line 419: code = f"_result = getattr(op({_lit(path)}).par, {_lit(param)}).eval()"); list_parameters (line 429: f" try: return p.eval()\n")
Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.
Tool test coverage
Only 3/27 tools referenced in tests (11%)
Write tests that reference each tool by name so every tool has at least one test.
Tool description accuracy
3 tools have description/behavior mismatches: get_parameter: description implies read-only but handler writes/deletes/executes; list_parameters: description implies read-only but handler writes/deletes/executes; get_module_help: 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.
[](https://m8ven.ai/mcp/mrinalghosh/touchdesigner-mcp)?variant=verified from the URL.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