Storybook (stefanoamorelli) MCP Server
storybook-mcp-server
npm
v0.1.3
Source verified
Published by stefanoamorelli — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
MCP server for Storybook - provides AI assistants access to components, stories, properties and screenshots
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
high Shell/command execution in server code (dist/storybook-detector.js)MTC-SRC-002
In the server's implementation (`dist/storybook-detector.js:9`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: require("path")); const child_process_1 = require("child_process"); const axios_1 = __importDefault(require("axios")); c
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/storybook-detector.js
Tools 6
Each tool and what it can reach — statically extracted from the published source.
storybook_capture_all_screenshotsno sensitive capabilitystorybook_capture_screenshotno sensitive capabilitystorybook_get_component_propsno sensitive capabilitystorybook_get_story_detailsno sensitive capabilitystorybook_list_componentsno sensitive capabilitystorybook_list_storiesno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (6 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.3 latest |
A 94/100 | 1 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan storybook-mcp-server --onlineOther implementations of Storybook 5
Independent packages implementing the same tool, scanned with the same engine. Compare all 6 side by side →
MCP server that serves knowledge about your components based on your Storybook stories and documentation
MCP server for Storybook integration – browse, inspect, and scaffold components
MCP server that connects to any Storybook. Browse components, fetch docs and examples, search stories, and capture screenshots.
이 서버는 **Model Context Protocol (MCP)** 을 통해 AI 에이전트(**Cline, Roo Code, Claude Desktop** 등)가 로컬 **Storybook 컴포넌트 명세를 직접 읽고 분석**할 수 있도록 돕는 도구입니다.
A Model Context Protocol (MCP) server for Storybook.
More in Data Science & ML
MCP server for 2s.io — 575+ pay-per-call tools for AI agents — ground-truth data, AI gateway, and agent infra (storage, locks, queues, watchers). x402 USDC on Base/Solana, no API keys, upto usage billing, free trials.
ArXiv preprints + Google Scholar papers, with citation counts in one query.
Add MCP servers to your favorite coding agents with a single command.
Help agents automatically write and test stories for your UI components
Model Context Protocol server for AI-Archive platform - enables AI agents to discover, submit, and review research papers
MCP server for Semantic Scholar research workflows with stdio and Streamable HTTP transports.