io.github.dwarehouse1/vrm-toolkit-mcp
NPM · VRM-TOOLKIT-MCP · SCANNED OCT 4
Inspect, validate and preview VRM / VRMA files from an AI agent (5 tools, local stdio server).
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security90
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects basic-ftp 5.3.1, reached via puppeteer-core > @puppeteer/browsers > proxy-agent > pac-proxy-agent > get-uri > basic-ftp. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 50 of 186 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 60 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 520 tokens (~104/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.dwarehouse1/vrm-toolkit-mcp server?
io.github.dwarehouse1/vrm-toolkit-mcp runs locally as an npm package, launched with npx -y vrm-toolkit-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · vrm-toolkit-mcp
claude mcp add dwarehouse1-vrm-toolkit-mcp -- npx -y vrm-toolkit-mcp
{
"mcpServers": {
"dwarehouse1-vrm-toolkit-mcp": {
"command": "npx",
"args": [
"-y",
"vrm-toolkit-mcp"
]
}
}
} {
"servers": {
"dwarehouse1-vrm-toolkit-mcp": {
"command": "npx",
"args": [
"-y",
"vrm-toolkit-mcp"
]
}
}
} codex mcp add dwarehouse1-vrm-toolkit-mcp -- npx -y vrm-toolkit-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dwarehouse1-vrm-toolkit-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"vrm-toolkit-mcp"
],
"enabled": true
}
}
} openclaw mcp add dwarehouse1-vrm-toolkit-mcp --command npx --arg -y --arg vrm-toolkit-mcp
mcp_servers:
dwarehouse1-vrm-toolkit-mcp:
command: "npx"
args: ["-y", "vrm-toolkit-mcp"] {
"McpServers": {
"dwarehouse1-vrm-toolkit-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"vrm-toolkit-mcp"
]
}
}
} assistant mcp add dwarehouse1-vrm-toolkit-mcp -t stdio -c npx -a -y vrm-toolkit-mcp
{
"mcpServers": {
"dwarehouse1-vrm-toolkit-mcp": {
"command": "npx",
"args": [
"-y",
"vrm-toolkit-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Oct 26 −3
- Stability: pass → 0.80 functional
- 2 Oct 26 −2
- CVE-2026-102990 affects this package: high ▼ security
- Known CVEs: partial → fail ▼ security
- CVE-2026-19693 no longer affects this package ▲ security
- CVE-2026-56876 no longer affects this package ▲ security
- Stability: 0.97 → pass security
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 −2
- Stability: pass → 0.80 functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Analysed npm/vrm-toolkit-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 3 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-c475-qrg2-pj4r | CVE-2026-102990 | high | yes | |
| GHSA-7pqw-9j4j-h8q3 | CVE-2026-19693 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H | no |
| GHSA-jmr9-qjv8-65gv | CVE-2026-56876 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N | no |
Background: What a vulnerability scan can and cannot prove →
Dependencies 186 packages
| Packages resolved | 186 |
|---|---|
| Stale | 50 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
vrm_inspect ~70
Inspect a local VRM file (0.x or 1.0): meta including license/permission fields, humanoid bone map, expressions/blendshapes, polygon and texture statistics. Structured JSON output; no rendering.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Local path to a .vrm file |
No output schema declared.
No examples provided.
vrm_snapshot ~126
Render a still PNG of a VRM in its rest pose through a local headless Chrome/Edge, with optional expression weights (e.g. {"happy": 1}) and view presets including a face close-up.
| Name | Type | Req | Description |
|---|---|---|---|
| expression | object | – | – |
| height | integer | – | – |
| output_path | string | yes | Where to write the PNG output |
| path | string | yes | Local path to the .vrm avatar |
| pose | string | – | v0.1 supports the rest pose only |
| view | string | – | – |
| width | integer | – | – |
No output schema declared.
No examples provided.
vrm_validate ~77
Validate a local VRM file and return a finding list: missing required humanoid bones, broken node references, missing meta/license fields, unrecognized required extensions, and configurable size/triangle/texture/material budget checks.
| Name | Type | Req | Description |
|---|---|---|---|
| limits | object | – | Optional budget overrides |
| path | string | yes | Local path to a .vrm file |
No output schema declared.
No examples provided.
vrma_inspect ~66
Inspect a local VRMA (VRM animation) file: spec version, targeted humanoid bones, expression tracks, channel counts, duration, and an estimated frame rate. Structured JSON output; no rendering.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Local path to a .vrma file |
No output schema declared.
No examples provided.
vrma_preview ~181
Render a VRMA animation applied to a VRM through a local headless Chrome/Edge. mode=image writes a PNG at time_sec; mode=video records a short WebM clip (max 10 seconds).
| Name | Type | Req | Description |
|---|---|---|---|
| duration_sec | number | – | Video mode: recording length |
| fps | integer | – | Video mode: capture rate (default 30) |
| height | integer | – | – |
| mode | string | – | Default image |
| output_path | string | yes | Where to write the PNG/WebM output |
| time_sec | number | – | Image mode: clip time to render (default mid-clip) |
| view | string | – | – |
| vrm_path | string | yes | Local path to the .vrm avatar |
| vrma_path | string | yes | Local path to the .vrma animation |
| width | integer | – | – |
No output schema declared.
No examples provided.
What is the io.github.dwarehouse1/vrm-toolkit-mcp server?
io.github.dwarehouse1/vrm-toolkit-mcp is listed in the public MCP registry as io.github.dwarehouse1/vrm-toolkit-mcp. Inspect, validate and preview VRM / VRMA files from an AI agent (5 tools, local stdio server). This page covers its npm package (vrm-toolkit-mcp).
Is the io.github.dwarehouse1/vrm-toolkit-mcp server safe to use?
io.github.dwarehouse1/vrm-toolkit-mcp scores 78 out of 100 on VerifyMCP. We recorded 3 known advisories against it as of 4 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.dwarehouse1/vrm-toolkit-mcp server expose?
io.github.dwarehouse1/vrm-toolkit-mcp exposes 5 tools: vrm_inspect, vrm_validate, vrma_inspect, vrma_preview, vrm_snapshot. Their descriptions and schemas cost roughly 520 tokens of context every time the server is loaded.
Is the io.github.dwarehouse1/vrm-toolkit-mcp server still maintained?
io.github.dwarehouse1/vrm-toolkit-mcp is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.dwarehouse1/vrm-toolkit-mcp server under?
io.github.dwarehouse1/vrm-toolkit-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.