ResoniteLinkSAFE
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
ResoniteLink WebSocket プロトコルを使用して Resonite VR ワールドを操作するための MCP サーバ & CLI ツール。
インストール
npm install npm run build
MCP サーバとして使用
Claude Code 設定
プロジェクトルートの .mcp.json に設定済み。Claude Code を再起動すると自動的にMCPサーバーが利用可能になります。
Claude Desktop 設定
claude_desktop_config.json に以下を追加:
{
"mcpServers": {
"resonitelink": {
"command": "node",
"args": ["C:/Users/neo/GitHub/resolink_mcp/dist/mcp-server.js"],
"env": {
"RESONITE_WS_URL": "ws://localhost:29551"
}
}
}
}利用可能なツール
CLI として使用
WebSocket URL の指定方法
CLI は WebSocket URL を以下の優先順位で決定します:
- コマンドライン引数
--url(最優先) - 環境変数
RESONITELINK_URL - デフォルト値:
ws://localhost:29551
環境変数で設定する例:
# Windows (PowerShell) $env:RESONITELINK_URL = "ws://localhost:29469" # Windows (コマンドプロンプト) set RESONITELINK_URL=ws://localhost:29469 # Linux/Mac export RESONITELINK_URL=ws://localhost:29469
環境変数を設定すれば、毎回 --url オプションを指定する必要がなくなります。
基本的なコマンド
# Rootスロット情報を取得 node dist/cli.js root --depth 1 # 特定のスロット情報を取得 node dist/cli.js get-slot --id --depth 1 # コンポーネント情報も含めて取得 node dist/cli.js get-slot --id --components # 名前でスロットを検索 node dist/cli.js find --name MyObject # スロットを追加 node dist/cli.js add-slot --name NewSlot --position 0,1,0 # 親スロットを指定してスロッ
546177fb7e45OBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add resonitelink-mcp -- npx -y [email protected]
{
"mcpServers": {
"resonitelink-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}Exposed tools (24)
16 read · 6 write · 2 destructive. Blast radius: 2 tools can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
add_component | write | |
add_slot | write | |
connect | read | |
disconnect | read | |
find_slot | read | |
get_camera | read | |
get_component | read | |
get_component_info | read | |
get_component_source | read | |
get_slot | read | |
grep_source | read | |
import_texture_file | write | |
list_categories | read | |
list_children | read | |
list_components | read | |
remove_component | destructive | |
remove_slot | destructive | |
search_by_category | read | |
search_by_member | read | |
search_components | read | |
set_camera | write | |
take_photo | read | |
update_component | write | |
update_slot | write |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- declared (5 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (3)
remove_component, remove_slot
@modelcontextprotocol/sdk, uuid, ws, zod, @types/node, @types/uuid, @types/ws, typescript
Gates applied: no_behavioural_pass, no_license.
546177fb7e45full audit observations/trust-audit/mcp-server/rassi0429__resonitelink.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 546177fb7e45 | SAFE | B | 89 | first audit |
Questions
What tools does ResoniteLink expose?
24 in total: 16 read-only, 6 that write, and 2 that can delete or overwrite (remove_component, remove_slot). Every one is listed on this page with its risk.
Is ResoniteLink safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B. Separately from the audit: 2 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does ResoniteLink need?
No credential environment variables were found in its source, so it appears to need none.
How does ResoniteLink run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as resonitelink-mcp at 1.0.0.
How current is this page?
The grade is for one exact copy of the source (546177fb7e45), read on 2026-10-08. The repository is watched and re-audited when it changes.