CSS Crème
v1.8.1Give your agent a real design system: tokens, measured WCAG contrast, and rules to follow.
Endpoint health
online- Last checked
- 11/20/2026, 6:16:47 AM
- Latency
- 92 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.csscreme%2Fdesign-systems
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.csscreme/design-systems": {
"url": "https://csscreme.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
13 shown · authentication unknown
Is this CSS feature safe to ship, and who ships it
css_feature
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.
Schema valid · SHA-256 d165565fd955…
View input schema
{ "type": "object", "properties": { "feature": { "type": "string", "description": "A web-features id or a plain name: \"container-queries\", \"has\", \":has()\", \"anchor positioning\", \"oklch\", \"subgrid\", \"@scope\". Omit for the whole Ship Gap summary." } } }Measure a design system across a whole site, not one page
decode_site
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.
Connections
streamable-http
https://csscreme.com/mcp