Stitch Wand
NPM · @STITCHWAND/MCP-SERVER
Design token tools for Google Stitch: convert, validate, diff, lint, generate, and export.
Available components
Last scanned (20 hours ago)
Scores higher than 58% of npm servers
Category Design and Media
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 42 of 131 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 199 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 230 tokens (~38/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 −1
- Stability: pass → 0.97 functional
- 19 Oct 26 +1
- Stability: 0.97 → pass security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 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.
- 13 Oct 26 −3
- Stability: pass → 0.80 functional
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 Nov 2026 · Analysed npm/@stitchwand/mcp-server@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 →
Dependencies 131 packages
| Packages resolved | 131 |
|---|---|
| Deprecated | 1 |
| Stale | 42 |
| 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 →
convert-tokens ~61
Convert design tokens from various formats to DESIGN.md
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | The input token format |
| input | string | yes | The design token source content (JSON, CSS, or JS) |
| name | string | – | Name for the design system |
No output schema declared.
No examples provided.
diff-systems ~39
Compare two DESIGN.md versions
| Name | Type | Req | Description |
|---|---|---|---|
| versionA | string | yes | First DESIGN.md version |
| versionB | string | yes | Second DESIGN.md version |
No output schema declared.
No examples provided.
export-figma ~30
Generate Figma Plugin API code from HTML
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | The HTML to export |
No output schema declared.
No examples provided.
generate-component ~34
Generate framework components from HTML
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | – | Target framework |
| html | string | yes | The HTML to convert |
No output schema declared.
No examples provided.
lint-accessibility ~27
Run accessibility linter on HTML
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | The HTML to lint |
No output schema declared.
No examples provided.
validate-html ~39
Validate HTML against a DESIGN.md specification
| Name | Type | Req | Description |
|---|---|---|---|
| designMd | string | yes | The DESIGN.md specification |
| html | string | yes | The HTML to validate |
No output schema declared.
No examples provided.
How do I install the Stitch Wand MCP server?
Stitch Wand runs locally as an npm package, launched with npx -y @stitchwand/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @stitchwand/mcp-server
claude mcp add dilshaus-stitch-wand -- npx -y @stitchwand/mcp-server
What is the Stitch Wand MCP server?
Stitch Wand is an MCP server listed in the public MCP registry as io.github.dilshaus/stitch-wand. Design token tools for Google Stitch: convert, validate, diff, lint, generate, and export. This page covers its npm package (@stitchwand/mcp-server).
Is the Stitch Wand MCP server safe to use?
Stitch Wand scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 Stitch Wand MCP server expose?
Stitch Wand exposes 6 tools: convert-tokens, validate-html, diff-systems, lint-accessibility, generate-component, export-figma. Their descriptions and schemas cost roughly 230 tokens of context every time the server is loaded.
Is the Stitch Wand MCP server still maintained?
Stitch Wand is still listed as active in the MCP registry. We last reached this channel on 4 November 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 Stitch Wand MCP server under?
Stitch Wand declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.