C
Limited view
67/100
15 days ago

vred-mcp

A local MCP server that enables MCP-compatible AI clients to inspect and control the currently open scene in a running Autodesk VRED Professional 2027 instance via a secure bridge, supporting read-only inspection and gated mutations like selection, visibility, transforms, and screenshots.

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

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

krngrover6

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

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.
🔐
You'll be asked for 1 credential: VRED_BRIDGE_TOKEN
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.
configVRED_BRIDGE_PORT
🔐 secretVRED_BRIDGE_TOKEN.env -> =<token>
configVRED_MAX_REQUEST_BYTESRequest bodies over are rejected without being
configVRED_MAX_RESPONSE_BYTES
configVRED_MAX_SCENE_NODES
configVRED_MAX_TREE_DEPTH
configVRED_REQUEST_TIMEOUT_SECONDS
configVRED_ALLOW_MUTATIONSswitch camera, capture screenshot), all gated behind
configVRED_ALLOW_SAVEbehind VRED_ALLOW_MUTATIONS / , both false by
configVRED_ALLOWED_OUTPUT_DIRcapture_screenshot Write a PNG/JPG/BMP of the current render view to a path inside .
configVRED_ALLOWED_SAVE_DIRon both sides.
// 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

68/68 tools missing one or more hints — get_current_frame (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); set_current_frame (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_animations (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +65 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.

Tool inputs are validated

54/68 tool handlers declare input schemas (79%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 0/68 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

License file

No license file

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

Tests exist

No test files found

Add tests that exercise each declared tool.

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 6 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 Score](https://m8ven.ai/badge/mcp/krngrover6-autodesk-vred-mcp-sk09tj)](https://m8ven.ai/mcp/krngrover6-autodesk-vred-mcp-sk09tj)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: b7e794cf4b5d7570e590ac5c7487543ab86c32d4
code hash: 7407b028056607f8083c520835b71d3e46ea691faa57366337df9820d16664aa
verified: 8/7/2026, 7:45:15 AM
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