Skills/npm/musea-mcp-server

musea-mcp-server@0.726.0

VERIFIED· not started

Publisher claims: "MCP server for building Vue.js design systems - component analysis, documentation, variant generation, and design tokens" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher vizejs · publishing for 282 daysInstalls 55,583Last detonated 5d ago
$claude mcp add musea-mcp-server -- npx -y @vizejs/musea-mcp-server
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
MUSEA_TOKENS_PATHConfiguration, not credentials: MUSEA_PROJECT_ROOT
Where it talks to
no vendor host named in the code
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard. It asks for MUSEA_TOKENS_PATH and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --net declared -- npx -y @vizejs/musea-mcp-server

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-09 and scored it 91/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 7 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
7.0sprocessdependency install exit 1 · (Use `node --trace-warnings ...` to show where the warning was created) npm error Cannot read properties of null (reading 'edgesOut') npm error A complete log of this run can be found in: /tmp/ks-detonate-u1vf4x/task/home/.npm/_logs/2026-11-09T22_22_43_339Z-debug-0.log
7.0sclaimednot started: dependency install failed (exit 1); the server itself was not observed
7.0sprocessscript backend runs setup only
7.0sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsdist/src-CEkbLkmL.mjs:27 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files* `Evil.vue` → `.env` symlink would otherwise be read by generate/analyzeFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

No other findings across 2,366 lines in 7 files.

Cost to the agent

Instructions loaded
≈71 tok
1 file · 7 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for @vizejs/musea-mcp-server@0.726.0 as of 5d ago. This is the package itself, not its dependencies.

musea-mcp-server@0.726.0 safety verdict: Verified (not started) — KillerSkills