io.github.Erebuzzz/pixasso
NPM · PIXASSO-MCP
End-to-end frontend engineering and design orchestrator across 16 foundational pillars.
Available components
Last scanned (22 hours ago)
Scores higher than 69% of npm servers
Category Developer Tools
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 41 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1269 tokens (~34/item across 37 items; 6 tools + 31 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 Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
- Stability: 0.97 → pass security
- 19 Nov 26 −1
- Stability: pass → 0.97 functional
- 13 Nov 26 +1
- Stability: 0.97 → pass security
- 12 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 +1
- Stability: 0.97 → pass security
- 4 Nov 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.
- 3 Nov 26 −2
- Stability: pass → 0.90 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
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 21 Nov 2026 · Analysed npm/pixasso-mcp@1.0.4
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 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| 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 →
pixasso_audit_design ~62
Audit HTML, JSX, or CSS against generic AI clichés, accessibility guidelines, and the 5-pillar rubric.
| Name | Type | Req | Description |
|---|---|---|---|
| componentMarkup | string | yes | HTML, JSX, or CSS to evaluate. |
| contextDescription | string | – | Contextual design intent. |
No output schema declared.
No examples provided.
pixasso_discover_intent ~79
Initiate adaptive intent discovery for a frontend project across the 16 pillars and generate tailored popup questions.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Initial brief or description of the project. |
| projectArchetype | string | yes | The primary archetype of the frontend project. |
| targetAudience | string | – | Target audience or user persona if known. |
No output schema declared.
No examples provided.
pixasso_generate_brain ~61
Build a Graphify-style Mermaid visualization mapping design decisions and Task DAG execution state.
| Name | Type | Req | Description |
|---|---|---|---|
| decisions | array | yes | List of key design decisions. |
| projectName | string | yes | Name of the project. |
| tasks | array | – | Task DAG nodes. |
No output schema declared.
No examples provided.
pixasso_generate_genome ~120
Validate design decisions and compile a machine-readable design-genome.yaml specification.
| Name | Type | Req | Description |
|---|---|---|---|
| colorTokens | object | yes | – |
| dimensionality | string | – | Visual dimensionality. |
| groundTone | string | yes | Hex ground tone (e.g. #fbfaf7, #0a0f0d, #000000). |
| motionFeel | string | – | Motion pacing and easing description. |
| projectName | string | yes | Name of the project or app. |
| themeMode | string | yes | Visual theme mode. |
| typography | object | yes | – |
No output schema declared.
No examples provided.
pixasso_generate_test_plan ~96
Generate an automated multi-viewport testing matrix (390px, 768px, 1024px, 1440px) and overflow detection script.
| Name | Type | Req | Description |
|---|---|---|---|
| projectName | string | yes | Application or website name. |
| testUrl | string | – | Target URL to test. |
| testedViewports | array | – | Viewport widths to test (defaults to 390, 768, 1024, 1440). |
No output schema declared.
No examples provided.
pixasso_search_references ~84
Search across all 20 Pixasso design reference catalogs, 11 templates, and the 16 frontend pillars.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter category. |
| query | string | yes | Keywords to search across design references and templates. |
| tag | string | – | Filter by tag (e.g. typography, motion, a11y, 3d, components). |
No output schema declared.
No examples provided.
How do I install the io.github.Erebuzzz/pixasso MCP server?
io.github.Erebuzzz/pixasso runs locally as an npm package, launched with npx -y pixasso-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 · pixasso-mcp
claude mcp add erebuzzz-pixasso -- npx -y pixasso-mcp
What is the io.github.Erebuzzz/pixasso MCP server?
io.github.Erebuzzz/pixasso is an MCP server listed in the public MCP registry as io.github.Erebuzzz/pixasso. End-to-end frontend engineering and design orchestrator across 16 foundational pillars. This page covers its npm package (pixasso-mcp).
Is the io.github.Erebuzzz/pixasso MCP server safe to use?
io.github.Erebuzzz/pixasso scores 81 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 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 io.github.Erebuzzz/pixasso MCP server expose?
io.github.Erebuzzz/pixasso exposes 6 tools: pixasso_discover_intent, pixasso_search_references, pixasso_generate_genome, pixasso_generate_brain, pixasso_audit_design, pixasso_generate_test_plan. Their descriptions and schemas cost roughly 502 tokens of context every time the server is loaded.
Is the io.github.Erebuzzz/pixasso MCP server still maintained?
io.github.Erebuzzz/pixasso is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.Erebuzzz/pixasso MCP server under?
io.github.Erebuzzz/pixasso declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.Erebuzzz/pixasso MCP server?
VerifyMCP ran 16 checks on io.github.Erebuzzz/pixasso, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.