ResoniteLink MCP
Enables control and manipulation of Resonite VR worlds through the ResoniteLink WebSocket protocol. Supports slot management, component operations, and world object creation/modification through natural language.
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
rassi0429
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.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
get_cameraCheck if the camera is available in Resonite
set_cameraSet the camera position and rotation in Resonite
take_photoTake a photo in Resonite and return the uploaded image URL. This may take several seconds.
connectConnect to Resonite via ResoniteLink WebSocket
disconnectDisconnect from Resonite
get_slotGet information about a slot by ID
find_slotFind a slot by name within a parent slot
add_slotAdd a new slot to the world
remove_slotRemove a slot from the world. WARNING: Do not remove system slots like Controllers, Roles, SpawnArea, Light, Skybox, Assets, etc.
update_slotUpdate slot properties (position, rotation, scale, name, active)
list_childrenList child slots (id and name only) - lightweight alternative to get_slot
list_componentsList components on a slot (id and type only) - lightweight
add_componentAdd a component to a slot. Component type format: [FrooxEngine]FrooxEngine.ComponentName
get_componentGet component details by ID
update_componentUpdate component member values
remove_componentRemove a component by ID
import_texture_fileImport a texture from a file on the local file system (Resonite host). Returns assetURL that can be assigned to static asset providers.
search_componentsSearch for Resonite components by name in decompiled source
get_component_infoGet detailed info about a specific Resonite component
list_categoriesList all available component categories
search_by_categorySearch components by category
search_by_memberSearch components that have a specific member name
get_component_sourceGet the full source code of a component
grep_sourceSearch all source files for a text pattern
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse
ws: Memory exhaustion DoS from tiny fragments and data chunks
uuid: Missing buffer bounds check in v3/v5/v6 when buf is provided
ws: Uninitialized memory disclosure
CAMERA_WS_URLRESONITELINK_URL$env: = "ws://localhost:29469"RESONITE_WS_URL"": "ws://localhost:29551"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
24/24 tools missing one or more hints — get_camera (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); set_camera (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); take_photo (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +21 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
20/24 tool handlers declare input schemas (83%)
Declare an inputSchema with zod/joi/yup on every tool definition.
Tool handlers catch errors
Only 3/24 tool handlers wrap calls in try/catch (13%)
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.
Shell command execution
1 child_process call — runs shell commands
Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.
Production dependencies are patched
0 critical, 2 high severity in production deps — @modelcontextprotocol/sdk@1.25.2 (high), ws@8.19.0 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
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/rassi0429/resolink-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