io.github.Patrizzos/stylespeak
NPM · @PATRIZZOS/STYLESPEAK · SCANNED AUG 4
MCP server and CLI that makes CSS legible to AI agents — explains what applies and why.
Available components
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 →
Supply Chain Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- 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 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 879 tokens (~175/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @patrizzos/stylespeak
claude mcp add patrizzos-stylespeak -- npx -y @patrizzos/stylespeak
codex mcp add patrizzos-stylespeak -- npx -y @patrizzos/stylespeak
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"patrizzos-stylespeak": {
"type": "local",
"command": [
"npx",
"-y",
"@patrizzos/stylespeak"
],
"enabled": true
}
}
} openclaw mcp add patrizzos-stylespeak --command npx --arg -y --arg @patrizzos/stylespeak
mcp_servers:
patrizzos-stylespeak:
command: "npx"
args: ["-y", "@patrizzos/stylespeak"] {
"mcpServers": {
"patrizzos-stylespeak": {
"command": "npx",
"args": [
"-y",
"@patrizzos/stylespeak"
]
}
}
} 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.
- 4 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +29
- Schema quality: 489 → 879 ▼ functional
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.20 ▲ functional
- 1 Aug 26 −8
- Stability: 0.13 → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Source repository: fail → pass ▲ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Package version: 1.0.0 → 1.2.0 functional
- Package version: 1.0.0 → 1.1.0 functional
- 31 Jul 26 −10
- Schema quality: 314 → 489 ▼ functional
- First check of Stability: 0.13 functional
- First check of MCP protocol: fail functional
- Package version: 0.3.0 → 1.0.0 functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 +34
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 26 Jul 26 41
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 Aug 2026 · Analysed npm/@patrizzos/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 0 packages
0 packages in the resolved dependency tree.
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.
impact_preview ~221
Predicts the blast radius of a proposed CSS change before it is made. Given a selector, property, and optional new value, returns every competing rule in the codebase that would be affected — showing which selectors will see a different value, which are shielded by higher specificity, which cascade relationships are uncertain, and which downstream rules are affected through CSS variable chains or inheritance. Works without a browser. Use this before making any CSS change to understand the full impact.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | — | Absolute paths to CSS/SCSS files to analyze. |
| newValue | string | — | Optional: the new value you plan to set. Enables before/after comparison in variable chain impacts. |
| projectRoot | string | — | Optional: path to a project root. All CSS/SCSS files will be discovered recursively. |
| property | string | yes | The CSS property you are about to change, e.g. "background-color", "--color-primary" |
| selector | string | yes | The CSS selector you are about to change, e.g. ".btn", ":root" |
No output schema declared.
No examples provided.
live_resolve ~175
Resolves CSS for a selector by querying a live running browser via Chrome DevTools Protocol (CDP). Returns exact computed styles and every matched rule in cascade order — no static analysis, no heuristics, confidence is always exact. Requires Chrome or any Chromium browser (Edge, Brave, Arc) running with --remote-debugging-port=9222. Use this when you need ground truth. Fall back to resolve_styles when no browser is running.
| Name | Type | Req | Description |
|---|---|---|---|
| port | number | — | CDP port (default: 9222). Change if you started Chrome with a different port. |
| selector | string | yes | CSS selector to resolve against the live DOM, e.g. ".btn.primary", "#header a" |
| tabUrl | string | — | Optional URL substring to target a specific tab. If omitted, uses the first available tab. |
No output schema declared.
No examples provided.
resolve_styles ~178
Resolves what CSS actually applies to a given selector. Returns every property the selector would receive, which rule wins for each property, and which rules were overridden — with confidence levels (certain/likely/possible) since no real DOM is available. Call this before modifying styles for an element to understand the full cascade context first.
| Name | Type | Req | Description |
|---|---|---|---|
| componentFiles | array | — | Optional: absolute paths to JSX/TSX files. When provided, builds an AST component graph to upgrade selector confidence from possible to likely where ancestry is confirmed. |
| files | array | — | Absolute paths to CSS/SCSS files to analyze. |
| projectRoot | string | — | Optional: path to a project root. All CSS/SCSS files will be discovered recursively. |
| selector | string | yes | CSS selector to resolve, e.g. ".btn.primary", "#header a:hover" |
No output schema declared.
No examples provided.
style_manifest ~169
Builds a compressed, structured summary of a project's entire CSS knowledge — selectors, properties, variables, competition groups, and risk hotspots — that an agent can load ONCE at the start of a session and keep in context. Use this at the beginning of any CSS editing task to understand the landscape before querying individual selectors. Much faster than running resolve_styles on every selector. Follow up with resolve_styles, trace_property, or impact_preview for deep analysis of specific selectors surfaced in the manifest.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | — | Absolute paths to CSS/SCSS files to analyze. |
| maxSelectors | number | — | Maximum selectors to include (default: 200). Hotspot selectors are prioritised when truncating. |
| projectRoot | string | — | Path to project root. All CSS/SCSS files discovered recursively. |
No output schema declared.
No examples provided.
trace_property ~136
Traces a CSS property across all provided files — finding every rule that sets it, grouping competing rules that target overlapping selectors, and showing who wins in each group. Use this to understand the blast radius of a property before changing it, or to find out why a property value isn't applying as expected.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | — | Absolute paths to CSS/SCSS files to analyze. |
| projectRoot | string | — | Optional: path to a project root. All CSS/SCSS files will be discovered recursively. |
| property | string | yes | CSS property name to trace, e.g. "color", "background-color", "padding" |
No output schema declared.
No examples provided.