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

REMOTE · WWW.STYLEKIT.TOP · 2 COMPONENTS

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

+2 this week 76 Trust /100

Last scanned (13 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Design and Media

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1344 tokens (~268/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 Management50
  • Stability check failed: schema churn in the 30 days we've observed: 5 tool removals, 0 breaking changes, 0 auth/transport breaks, 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 (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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.

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 14 Nov 26 +1

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

  • 12 Nov 26 +1

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

  • 10 Nov 26 +1

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

  • 9 Nov 26 0
    • Tool “stylekit_get_style” rewrote its description, which is the text the model reads security
  • 8 Nov 26 +1

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

  • 7 Nov 26 −6
    • Stability: 0.53 → fail ▼ security
    • Tool “stylekit_get_component_recipe” was removed ▼ security
    • Tool “stylekit_get_implementation_brief” was removed ▼ security
    • Tool “stylekit_get_shadcn_install” was removed ▼ security
    • Tool “stylekit_get_style_tokens” was removed ▼ security
    • Tool “stylekit_repair_code” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “stylekit_get_asset” rewrote its description, which is the text the model reads security
    • Tool “stylekit_get_style” rewrote its description, which is the text the model reads security
    • Tool “stylekit_list_assets” rewrote its description, which is the text the model reads security
    • Tool “stylekit_search_styles” rewrote its description, which is the text the model reads security
    • Schema quality: 2693 → 1369 ▲ functional
    • MCP protocol: Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. functional
    • MCP protocol version: 2026-07-28 → 2025-11-25 functional
    • Server version: 0.5.0 → 0.6.0 functional
    • “stylekit_get_style” added an optional parameter “component” cosmetic
    • “stylekit_get_style” added an optional parameter “include” cosmetic
    • “stylekit_get_asset” dropped the optional parameter “files” cosmetic
    • “stylekit_get_asset” dropped the optional parameter “includeSource” cosmetic
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 · Probed https://www.stylekit.top/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=stylekit.top CN=YR1,O=Let's Encrypt,C=US 22 Oct 2026 20 Jan 2027 RSA 2048 SHA256-RSA 667af395234019a4431c8a1644a06edaaae
SANs: stylekit.top, www.stylekit.top
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.stylekit.top. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
top. DS published 41508 13 Verified
stylekit.top. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.stylekit.top/mcp Verified 200
http (plaintext) http://www.stylekit.top/mcp HTTPS enforced 308 https://www.stylekit.top/mcp
MCP tools · 5 exposed · ~1,344 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 ~329

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 structured JSON with the shape below. When a canonical design.md is available, the human-readable text includes its complete Markdown; the full machine-readable brief remains at its URL. 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 is a hosted endpoint at https://www.stylekit.top/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.stylekit.top

# add to Claude Code
claude mcp add --transport http anxforever-stylekit-mcp 'https://www.stylekit.top/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 hosted endpoint (https://www.stylekit.top/mcp).

Is the StyleKit MCP server safe to use?

StyleKit scores 76 out of 100 on VerifyMCP. 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,344 tokens of context every time the server is loaded.

Does the StyleKit MCP server require authentication?

No. We connected to StyleKit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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 did VerifyMCP test on the StyleKit MCP server?

VerifyMCP ran 13 checks on StyleKit, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.