# CSS Crème (remote · csscreme.com)

Give your agent a real design system: tokens, measured WCAG contrast, and rules to follow.

- Trust score: 76/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `csscreme.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-csscreme-design-systems/csscreme.md), [page](https://verifymcp.io/servers/com-csscreme-design-systems/csscreme)

## Channel facts

- Endpoint: `https://csscreme.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.6.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1919 tokens (~159/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the CSS Crème MCP server?

CSS Crème is a hosted endpoint at https://csscreme.com/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.

### Claude

```bash
claude mcp add --transport http com-csscreme-design-systems 'https://csscreme.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-csscreme-design-systems": {
      "url": "https://csscreme.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-csscreme-design-systems": {
      "type": "http",
      "url": "https://csscreme.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-csscreme-design-systems]
url = "https://csscreme.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-csscreme-design-systems": {
      "type": "remote",
      "url": "https://csscreme.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-csscreme-design-systems --url 'https://csscreme.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-csscreme-design-systems:
    url: "https://csscreme.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-csscreme-design-systems": {
      "Transport": "http",
      "Url": "https://csscreme.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-csscreme-design-systems -t streamable-http -u 'https://csscreme.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-csscreme-design-systems": {
      "type": "http",
      "url": "https://csscreme.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 76, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-19 (score 73)

First indexed and scored.

## MCP tools (12)

### `search_themes` (~135 tokens)

Search design systems

Find a design system by describing what you are building ("dark developer tool", "calm fintech dashboard", "playful consumer app"). Returns matching themes with their DESIGN.md URL and shadcn install command. Call this first when the user has no design system defined.

Input parameters:

- `kind` (string): Curated palette theme, full page template, or either. Default any.
- `limit` (integer): Max results, 1-25. Default 8.
- `mode` (string): Preferred light or dark. Default any.
- `query` (string, required): Free text: mood, industry, colour, or use case.

### `list_themes` (~47 tokens)

List all design systems

Browse the full catalogue of curated themes and templates. Use when the user wants to see options rather than search for one.

Input parameters:

- `kind` (string)
- `mode` (string)

### `get_design_md` (~110 tokens)

Get a DESIGN.md

Fetch the full DESIGN.md for one theme: semantic colour roles, the complete shadcn token set in light and dark, typography, radius, spacing, MEASURED WCAG contrast ratios, and numbered rules the generated UI must follow. Read this before writing any UI. Save it at the repo root as DESIGN.md so it applies to every session.

Input parameters:

- `id` (string, required): Theme or template id, e.g. "deep-ocean". Get ids from search_themes or list_themes.

### `get_theme_tokens` (~85 tokens)

Get raw theme tokens

Get the shadcn/ui registry item (OKLCH tokens, light and dark) plus the paste-ready CSS variables for one theme, and the one-line command that installs it for real. Use after get_design_md when you are ready to write the tokens into globals.css.

Input parameters:

- `format` (string): Default both.
- `id` (string, required): Theme or template id.

### `how_to_use` (~69 tokens)

How to wire a DESIGN.md into this tool

Explains where a DESIGN.md belongs for a given coding agent (Claude Code, Cursor, v0, Codex, Lovable) so the design rules apply to every session rather than one message.

Input parameters:

- `tool` (string): claude-code | cursor | v0 | codex | lovable

### `get_install_command` (~71 tokens)

Get the one-line install command

Return the exact `npx shadcn@latest add <url>` command that installs one theme into a shadcn/ui project, plus the registry URL it reads. Use when the user says "install it" and you already know the id.

Input parameters:

- `id` (string, required): Theme or template id.

### `get_agent_rules` (~82 tokens)

Get a rules block for CLAUDE.md / AGENTS.md / .cursor/rules

Return a short standing-instructions block that makes every future session read DESIGN.md before touching UI. Paste it whole into CLAUDE.md, AGENTS.md or .cursor/rules/design.mdc. It points at the DESIGN.md rather than restating it, and carries the token fingerprint so drift is detectable.

Input parameters:

- `id` (string, required): Theme or template id.

### `decode_url` (~429 tokens)

Decode any live site into design tokens

Fetch a public site's HTML and stylesheets and return what its CSS declares: named custom properties that look like design tokens, the colours it uses most, its font stacks, border radii, spacing values, and the framework it appears to be built with. Also returns a "drop" report: roughly how many words a web-to-markdown reader would carry away from this page, against the design decisions it would discard, because markdown is defined by throwing the design layer away. It reads CSS and does not render the page, so it reports a confidence ("tokens" when named properties were found, "derived" when only compiled CSS was available) and flags a JavaScript shell rather than pretending every site is equally legible. Use when the user wants to match a site that is not in the catalogue, or has fetched a page as markdown and needs what that markdown lost.

Input parameters:

- `expect` (string): Optional brand hex, like #635BFF. The json response then carries `expect`: the nearest value the site declares (a token when it has any, else a literal), its CIE76 distance, and whether that is withi…
- `format` (string): Default json (the measurement). Or one artefact from the same read: md (DESIGN.md), tokens (W3C DTCG tokens.json with the site's declared names by scope), css (globals.css: shadcn variables, Tailwind…
- `url` (string, required): Absolute public http(s) URL of the page to read.

### `css_feature` (~294 tokens)

Is this CSS feature safe to ship, and who ships it

Answers two questions about a modern CSS feature with data instead of recall. First, its Baseline status (widely available, newly available, or limited availability), the date, and which core browsers lack it, read from the open web-features dataset at build time. Second, how many of CSS Crème's curated, decoded showcase sites ship it, which ones, how many of them guard it with @supports, and the exact @supports conditions they test. Also returns a fallback note where we have one, any name the feature has shipped under before (an agent that learned the old name will otherwise write it), and the documented limits that catch people out, each cited to the page it was read on. Call it before writing CSS that uses container queries, :has(), anchor positioning, @scope, view transitions, oklch(), color-mix(), light-dark(), subgrid, scroll-driven animations, @property, text-wrap and similar, so the CSS you write is accurate for today rather than for your training date. With no feature given it returns the Ship Gap: features that are safe and mostly ignored, and features that are early and shipped anyway.

Input parameters:

- `feature` (string): A web-features id or a plain name: "container-queries", "has", ":has()", "anchor positioning", "oklch", "subgrid", "@scope". Omit for the whole Ship Gap summary.

### `get_design_md_for_url` (~170 tokens)

Get a complete DESIGN.md for any public URL

Read the stylesheets of a public site and return a full DESIGN.md: semantic roles with the token each came from, measured WCAG contrast pairs, the tokens the site itself declares (framework internals counted separately), font families, the type scale with the ratio between steps, colour frequency, gradients, corner radii, spacing, an elevation ladder of shadows, breakpoints, the z-index ladder, interaction-state rule counts, motion, and whether a dark theme is declared. This is the artefact to hand a coding agent before it writes UI that should match a site. It reads declared CSS and does not execute JavaScript, so it reports what the stylesheets say rather than what the page renders.

Input parameters:

- `url` (string, required): Absolute public http(s) URL of the page to read.

### `decode_site` (~170 tokens)

Measure a design system across a whole site, not one page

Read a sample of pages from one site (from its sitemap.xml, or the homepage links when there is no sitemap) and report what is CONSISTENT across them: which declared tokens, colours, font stacks, radii and spacing values appear on every page read, and which appear on only some. One page shows what a page uses; a design system is a claim about consistency, and only a sample can test it. Returns counts and the pages actually read, never a score. Use when the user asks whether a site is really on a system, or wants the system rather than one page of it.

Input parameters:

- `pages` (integer): How many pages to read, 2 to 8. Default 5.
- `url` (string, required): Absolute public http(s) URL anywhere on the site.

### `verify_design_md` (~127 tokens)

Check whether a DESIGN.md copy is still current

Every DESIGN.md carries a Fingerprint line. Pass the id and that fingerprint; the server answers whether the copy matches the current token set, and if not, returns the current tokens so the agent can update the file instead of following a stale one. Call this at the start of a session when a DESIGN.md is already in the repo.

Input parameters:

- `fingerprint` (string, required): The value from the DESIGN.md Fingerprint line, e.g. "fnv1a-9c2a41d7".
- `id` (string, required): Theme or template id from the DESIGN.md Source line.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-csscreme-design-systems/csscreme#diagnostics

## Score history

- 2026-09-25: 76
- 2026-09-24: 75
- 2026-09-23: 75
- 2026-09-22: 74
- 2026-09-21: 74
- 2026-09-20: 73
- 2026-09-19: 73

## Common questions

### What is the CSS Crème MCP server?

CSS Crème is an MCP server listed in the public MCP registry as com.csscreme/design-systems. Give your agent a real design system: tokens, measured WCAG contrast, and rules to follow. This page covers its hosted endpoint (https://csscreme.com/mcp).

### Is the CSS Crème MCP server safe to use?

CSS Crème 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 CSS Crème MCP server expose?

CSS Crème exposes 12 tools: search_themes, list_themes, get_design_md, get_theme_tokens, how_to_use, and 7 more. Their descriptions and schemas cost roughly 1,789 tokens of context every time the server is loaded.

### Does the CSS Crème MCP server require authentication?

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

### Is the CSS Crème MCP server still maintained?

CSS Crème is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://csscreme.com/mcp
- Repository: https://github.com/damnepic/csscreme-skill
- Website: https://csscreme.com/ai/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-csscreme-design-systems/csscreme.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-csscreme-design-systems/csscreme.json
- HTML version of this page: https://verifymcp.io/servers/com-csscreme-design-systems/csscreme