Skills/npm/addon-mcp

addon-mcp@10.6.8

VERIFIED· install only

Publisher claims: "Help agents automatically write and test stories for your UI components" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher storybook · publishing for 450 daysInstalls 14.9MLast detonated 27 min ago
$claude mcp add addon-mcp -- npx -y @storybook/addon-mcp
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
1 of 1 bundled script run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

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
no credential variables read in the code
Where it talks to
storybook.local (its own)Also opencollective.com, githubusercontent.com, js.org — not the publisher's domain; check what for before connecting.
What we saw when it ran
no credential files read · no network
What we could not test
use of the skill by an agent

Connect it under the guard. Bundled scripts ran with no arguments; no agent task scenario for this bundle. The code names no credential variable and talks to storybook.local, its own; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- npx -y @storybook/addon-mcp

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

What changed since 10.6.7

vet-skills diff addon-mcp 10.6.7 10.6.8

In the sandbox, this version reached for nothing 10.6.7 did not. Compared from the two recorded runs, not from source.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-20 and scored it 95/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 · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessbundled script run in the sandbox with no arguments
0.1sprocessexited 1: Node.js v22.23.5
0.1sprocess1 of 1 bundled script run with no arguments
0.1sprocessscript backend runs setup only
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

No findings across 2,381 lines in 8 files.

Cost to the agent

Instructions loaded
≈55 tok
1 file · 8 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

No advisories in OSV for @storybook/addon-mcp@10.6.8 as of 1 min ago. This is the package itself, not its dependencies.