Maya (Jeffreytsai1004) MCP Server
maya-mcp-server
npm
v1.3.8
Published by jeffreytsai1004 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Maya integration through the Model Context Protocol - Node.js wrapper for Python MCP server
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 − 7.5 = 93. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −6.3 | Untrusted input concatenated into a command sink MTC-SRC-009 | injection |
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 93 − 7 = 86. 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:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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 4
high Shell/command execution in server code (bin/maya-mcp.js)MTC-SRC-002
In the server's implementation (`bin/maya-mcp.js:8`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: , execSync } = require('child_process'); const path = require('path'); const fs = require('fs'); // Get project roo
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server bin/maya-mcp.js
high Shell/command execution in server code (plug-ins/maya_mcp.py)MTC-SRC-002
In the server's implementation (`plug-ins/maya_mcp.py:436`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: exec(code, exec_globals, exec_locals) execution_result['success'] = Tru
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server plug-ins/maya_mcp.py
medium Untrusted input concatenated into a command sink (bin/maya-mcp.js)MTC-SRC-009
In the server's implementation (`bin/maya-mcp.js:21`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: try { execSync(`${cmd} --version`, { stdio: 'pipe' }); return cmd; } catch (e) {
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server bin/maya-mcp.js
low Package runs install-time scripts (postinstall)MTC-SUP-010
"maya-mcp-server" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: echo "Maya MCP Server installed successfully. Use: npx maya-mcp"
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package maya-mcp-server
Tools 10
Each tool and what it can reach — statically extracted from the published source.
create_primitiveno sensitive capabilitydelete_objectno sensitive capabilityexecute_maya_codeno sensitive capabilityget_console_outputno sensitive capabilityget_object_infono sensitive capabilityget_scene_infono sensitive capabilityget_scene_summaryno sensitive capabilityset_materialno sensitive capabilitysmart_selectno sensitive capabilitytransform_objectno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (10 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.3.8 latest |
B 86/100 | 4 | 1.13.0 | 2026-09-07 |
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.
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 maya-mcp-server --onlineOther implementations of Maya 2
Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →
MCP server for interacting with Autodesk Maya sessions
MCP server for controlling Autodesk Maya via commandPort
More in Design & Media
Turn designs into shipped parts: quote 3D printing, CNC, and decals, then check out.
Aleph's official SiliconFlow media-generation MCP server (image / video / TTS)
MCP server for image generation using Google Gemini AI
Ambience AI MCP Server - Generate images, videos, and audio through Model Context Protocol
MCP server exposing every endpoint of the AstroWay Calculation API as tools — natal, synastry, transits, Vedic dashas, Tarot, Numerology, Human Design, AI horoscopes — for Claude Desktop, Cursor and any MCP-compatible AI agent.
Audio-guide and trip-planning tools for 1,100+ cities from Audiala. Free, no API key.