Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

StyleKit

NPM · STYLEKIT-MCP · 2 COMPONENTS

MCP server for StyleKit styles, tokens, recipes, lint and repair over stdio or HTTP.

0 this week 71 Trust /100

Last scanned (19 hours ago)

Scores higher than 42% of npm servers

Category Design and Media

Trust breakdown (7 categories)

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 & Transparency45
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1369 tokens (~273/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 Management56
  • Stability check failed: the tool surface changed between 0.4.1 and 0.6.0: 4 tool removals, 0 breaking changes, 0 additions. See how to fix → Fail
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
What we tested

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 →

Changelog

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.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 52 to 56.

  • 18 Nov 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 56 to 52.

  • 13 Nov 26 −22
    • CVE-2023-54404 affects this package: high ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: pass → fail ▼ security
    • Known CVEs: pass → fail ▼ security
    • Provenance: pass → fail ▼ security
    • The attested source repository moved: AnxForever/stylekit security
    • Dependency health: 1.00 → 0.85 ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 2693 → 1369 ▲ functional
    • First check of Schema quality: unverified functional
    • MCP protocol: Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. functional
    • Package version: 0.5.0 → 0.6.0 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 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.

  • 8 Nov 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.

  • 7 Nov 26 −3
    • Stability: pass → 0.83 functional
  • 27 Oct 26 +1
    • Stability: 0.97 → pass security
Diagnostics

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/stylekit-mcp@0.6.0

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 →

MCP tools · 5 exposed · ~1,369 tokens

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 →

Tool Tokens
stylekit_get_asset ~155

Retrieve one public asset by its exact kind and id. Source is returned only where the asset's contentLevel and license permit it. Remote templates include their actual file set only when the live source is available; if it is down, the tool returns a structured unavailable error with safe metadata and does not treat a download URL as source code. External and restricted assets expose metadata, license, attribution and source links only. Args: - kind: the namespace returned by stylekit_list_assets. - id: the exact identifier within that namespace. Returns complete structured JSON and JSON text, preserving the namespace and provenance.

NameTypeReqDescription
idstringyesExact asset id within the namespace
kindstringyesPublic asset namespace
NameTypeReqDescription
attribution–––
capabilitiesarrayyes–
code–––
codeLanguagestring––
data–––
dependenciesarrayyes–
fallbackReasonstring––
license–––
metadataobjectyes–
schemaVersionstringyes–
sourcestringyes–
sourceUrlsarrayyes–

No examples provided.

stylekit_get_style ~354

Get one style's profile and, optionally, its design tokens, one component recipe, and the full implementation brief. Everything ships through this single tool so the server stays small: pass include: ["tokens"], ["recipe"], ["brief"] or a combination. Style data is read from the live catalogue with a five-minute cache; when live data is unavailable, a bundled snapshot may be returned and marked with origin and fallbackReason. Args: - slug (string): style identifier, e.g. "glassmorphism", "neo-brutalist". - include (array, optional): sections to attach — "tokens", "recipe", "brief". - component (string, optional): recipe id for include: ["recipe"], e.g. "button"; defaults to the style's first recipe. Returns JSON: { slug, name, nameEn, category, tags, description, philosophy, colors, doList, dontList, keywords, hasTokens, hasRecipes, recipeIds, shadcnInstall, url, quality, origin, fallbackReason?, tokens?, recipe?, brief? }. Examples: - "how should I use neo-brutalist?" -> slug: "neo-brutalist" - "give me the glassmorphism button code" -> slug: "glassmorphism", include: ["recipe"], component: "button" - Returns an error with a hint if the slug is unknown.

NameTypeReqDescription
componentstring–Recipe id when include contains 'recipe'; defaults to the first recipe
includearray–Sections to attach: "tokens", "recipe", "brief"
slugstringyesStyle slug, e.g. 'glassmorphism'
NameTypeReqDescription
briefobject––
categorystringyes–
colorsobjectyes–
descriptionstringyes–
doListarrayyes–
dontListarrayyes–
fallbackReasonstring––
hasRecipesbooleanyes–
hasTokensbooleanyes–
keywordsarrayyes–
namestringyes–
nameEnstringyes–
originstringyes–
philosophystringyes–
qualityobjectyes–
recipeobject––
recipeIdsarrayyes–
shadcnInstallstringyes–
slugstringyes–
tagsarrayyes–
tokensobject––
urlstringyes–

No examples provided.

stylekit_lint_code ~414

Check whether code actually follows a style's rules. Use this AFTER generating or editing UI code to verify it matches the style, instead of assuming it does. Reports forbidden classes with the reason they are banned and a concrete replacement. Understands JSX/HTML class attributes, cn()/clsx() calls, and template literals; variant prefixes (dark:, md:, hover:) are resolved before matching. Args: - slug (string): style identifier, e.g. "glassmorphism". - code (string): the source to check. JSX/TSX, HTML, or a bare class string. - checkRequired (array of 'button'|'card'|'input', optional): also report required classes the code is missing. Only pass components the code is supposed to contain. Returns JSON: { slug, ok, violations: [{ className, baseClassName, line, severity, source, rule, reason, fix }], missingRequired, checkedClasses, ruleSources, origin, contentSource, fallbackReason? }. Lint rules come from the same live implementation brief used for generation; its five-minute cache and any bundled fallback are reported separately from content provenance. Examples: - "does this button match neo-brutalist?" -> slug: "neo-brutalist", code: "<button className=...>", checkRequired: ["button"] - strict (boolean, default false): fail missing required classes in a static component snippet. Required checks cover the whole input, not each element. - status is pass, fail, or inconclusive. Runtime class expressions cannot be fully verified. ok is true only for a conclusive static pass; visual quality still needs review.

NameTypeReqDescription
checkRequiredarray–Components to also check for missing required classes
codestringyesSource code or class string to lint
slugstringyesStyle slug, e.g. 'glassmorphism'
strictboolean–Fail missing required classes in a static snippet
NameTypeReqDescription
checkedClassesnumberyes–
contentSourcestringyes–
coverageobjectyes–
fallbackReasonstring––
missingRequiredarrayyes–
okbooleanyes–
originstringyes–
ruleSourcesarrayyes–
slugstringyes–
statusstringyes–
violationsarrayyes–
warningsarrayyes–

No examples provided.

stylekit_list_assets ~188

Browse StyleKit's public asset catalogue by namespace and query. Use the returned kind/id pair with stylekit_get_asset. Args: - kind (optional): one public namespace such as animation, component-pattern, template, or experience-pack. - query (optional): search public names, descriptions and tags. - offset (number >=0, default 0): results to skip. - limit (number 1-100, default 20): page size. Returns the full JSON page, including availability, contentLevel, license, attribution, source provenance, and kind counts. An empty page is a successful result. Private user kits and unpublished submissions are not listed.

NameTypeReqDescription
kindstring–Public asset namespace
limitinteger–Page size
offsetinteger–Results to skip
querystring–Search names, descriptions and tags
NameTypeReqDescription
assetsarrayyes–
fallbackReasonstring––
hasMorebooleanyes–
kindCountsobjectyes–
limitnumberyes–
offsetnumberyes–
schemaVersionstringyes–
sourcestringyes–
totalnumberyes–

No examples provided.

stylekit_search_styles ~258

Search StyleKit design styles by keyword and/or category, with pagination. Exact slug or name matches are ranked first. Args: - query (string, optional): matches slug, name, description, tags, keywords (case-insensitive). - category ('modern'|'retro'|'minimal'|'expressive', optional): restrict to one category. - limit (number 1-50, default 15): page size. - offset (number >=0, default 0): results to skip (for paging). Returns structured JSON with total, count, offset, has_more, source, optional fallbackReason, and results. A valid query with no matches returns an empty results array, not a tool error. Examples: - "find a glassy frosted style" -> query: "glass" - "next page of retro styles" -> category: "retro", offset: 15 - For full tokens of one style, call stylekit_get_style with include: ["tokens"] instead.

NameTypeReqDescription
categorystring–Style category filter
limitinteger–Page size
offsetinteger–Results to skip for pagination
querystring–Keyword to match
NameTypeReqDescription
countnumberyes–
fallbackReasonstring––
has_morebooleanyes–
offsetnumberyes–
rankingstring––
resultsarrayyes–
sourcestringyes–
totalnumberyes–

No examples provided.

Install

How do I install the StyleKit MCP server?

StyleKit runs locally as an npm package, launched with npx -y stylekit-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 · stylekit-mcp

# add to Claude Code
claude mcp add anxforever-stylekit-mcp -- npx -y stylekit-mcp
Common questions

What is the StyleKit MCP server?

StyleKit is an MCP server listed in the public MCP registry as io.github.AnxForever/stylekit-mcp. MCP server for StyleKit styles, tokens, recipes, lint and repair over stdio or HTTP. This page covers its npm package (stylekit-mcp).

Is the StyleKit MCP server safe to use?

StyleKit scores 71 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 StyleKit MCP server expose?

StyleKit exposes 5 tools: stylekit_search_styles, stylekit_list_assets, stylekit_get_asset, stylekit_get_style, stylekit_lint_code. Their descriptions and schemas cost roughly 1,369 tokens of context every time the server is loaded.

Is the StyleKit MCP server still maintained?

StyleKit 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 StyleKit MCP server under?

StyleKit 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 StyleKit MCP server?

VerifyMCP ran 16 checks on StyleKit, 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.