# CSS SOTA (remote · css-sota-mcp.lusrodri.workers.dev)

What CSS you can actually ship today, from live Baseline data and MDN browser-compat-data.

- Trust score: 56/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `css-sota-mcp.lusrodri.workers.dev`: 56/100 (this document), [markdown](https://verifymcp.io/servers/lusrodri-css-sota-mcp/css-sota-mcp.md), [page](https://verifymcp.io/servers/lusrodri-css-sota-mcp/css-sota-mcp)

## Channel facts

- Endpoint: `https://css-sota-mcp.lusrodri.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## 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-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 60/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1749 tokens (~291/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### Claude

```bash
claude mcp add --transport http lusrodri-css-sota-mcp https://css-sota-mcp.lusrodri.workers.dev/mcp
```

### Codex

```toml
[mcp_servers.lusrodri-css-sota-mcp]
url = "https://css-sota-mcp.lusrodri.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lusrodri-css-sota-mcp": {
      "type": "remote",
      "url": "https://css-sota-mcp.lusrodri.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lusrodri-css-sota-mcp --url https://css-sota-mcp.lusrodri.workers.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lusrodri-css-sota-mcp:
    url: "https://css-sota-mcp.lusrodri.workers.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "lusrodri-css-sota-mcp": {
      "type": "http",
      "url": "https://css-sota-mcp.lusrodri.workers.dev/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-08-03 (score 56, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-02 (score 55)

First indexed and scored.

## MCP tools (6)

### `search_css_features` (~268 tokens)

Search CSS features

Search CSS features on the Web Platform Dashboard (webstatus.dev) by keyword, Baseline status, and the date range in which they reached Baseline. Use this to answer questions like "which CSS features for scroll animations are Baseline yet?" or "what limited-support CSS is there for anchoring?". Returns live Baseline data. For the browser versions a specific property shipped in, use check_support instead.

Input parameters:

- `baseline` (string): Filter by Baseline status: "widely" (interoperable for 30+ months, safe to use), "newly" (interoperable across all major engines recently), or "limited" (not yet available across all major engines).
- `limit` (integer): Maximum number of features to return.
- `query` (string): Free-text search over feature names and descriptions, e.g. "container queries", "anchor", "scroll". Omit to list all CSS features matching the other filters.
- `since` (string): Only features that became Baseline Newly available on or after this date (YYYY-MM-DD). Combined with `baseline`, this means "went Newly in this range AND is status X today".
- `until` (string): Only features that became Baseline Newly available on or before this date (YYYY-MM-DD).

Output parameters:

- `features` (array)
- `query` (string): The dashboard query that was executed.
- `total` (integer): Total matches upstream, across all pages.
- `truncated` (boolean): Whether more matches exist than were returned.

### `whats_new` (~200 tokens)

What's new in CSS

List CSS features that crossed a Baseline threshold within a date range, newest first. Use this to answer "what CSS can I start using now?", to write release notes, or to catch up after time away. Defaults to the last 180 days. The date is when a feature became interoperable across browsers, which is usually well after it first shipped in one.

Input parameters:

- `limit` (integer): Maximum number of features to return.
- `since` (string): Start of the window (YYYY-MM-DD), inclusive. Defaults to 180 days before today.
- `transition` (string): Which threshold was crossed in the window: "newly" for features that became interoperable across all major engines (the usual meaning of new), "widely" for those that reached the 30-month Widely avai…
- `until` (string): End of the window (YYYY-MM-DD), inclusive. Defaults to today.

Output parameters:

- `count` (integer)
- `features` (array)
- `since` (string)
- `truncated` (boolean)
- `until` (string)

### `get_feature` (~150 tokens)

Get CSS feature details

Get everything known about one CSS feature: Baseline status and dates, the browser versions it shipped in, its description, spec links, Web Platform Tests scores, usage, and MDN reference prose. Accepts a web-features id ("container-queries") or a display name ("Container queries"). Use search_css_features first if you do not know the id.

Input parameters:

- `feature_id` (string, required): The web-features id, e.g. "anchor-positioning", "container-queries", "subgrid". A display name such as "Anchor positioning" also works.
- `include_mdn` (boolean): Fetch MDN reference prose for the feature. Set false for a faster, terser answer.

Output parameters:

- `baseline`
- `baselineHighDate`
- `baselineLowDate`
- `bcdKeys` (array)
- `browsers` (object)
- `caniuse` (array)
- `description`
- `found` (boolean)
- `id` (string)
- `mdnUrl`
- `name` (string)
- `spec` (array)
- `suggestions` (array)

### `check_support` (~242 tokens)

Check CSS browser support

Look up which browser versions support a CSS property, value, selector, at-rule or function, from MDN browser-compat-data bundled with this server (no network call). Give either a BCD key ("css.properties.anchor-name") or a property with an optional value ("display" + "grid"). Also reports vendor prefixes, partial implementations and the Baseline status of the feature the key belongs to.

Input parameters:

- `all_browsers` (boolean): Include every browser in the dataset (Opera, Samsung Internet, WebView, IE) rather than only the seven that determine Baseline.
- `bcd_key` (string): A browser-compat-data key, e.g. "css.properties.text-wrap-style", "css.selectors.has", "css.at-rules.container", "css.types.color.color-mix". Takes precedence over property/value.
- `property` (string): A CSS property name, e.g. "display", "anchor-name". Used when bcd_key is absent.
- `value` (string): A value for that property, e.g. "grid" for display. Falls back to the property's own support when the value is not tracked separately.

Output parameters:

- `baseline`
- `deprecated` (boolean)
- `experimental` (boolean)
- `featureId`
- `key`
- `mdnUrl`
- `resolved` (boolean)
- `spec`
- `suggestions` (array)
- `support` (object)

### `audit_css` (~369 tokens)

Audit CSS against browser targets

Scan CSS source and report every feature in it that does not meet a browser support target. Targets are either a Baseline level ("baseline-widely", "baseline-newly") or an explicit browser list ("chrome 120, safari 17.4, firefox 128"). Reports the offending line, what is wrong (unsupported, too old, prefix-only, partial), and the minimum version that would work. Browserslist queries like "last 2 versions" are not supported. IMPORTANT when reading Baseline-level results: Baseline describes a whole feature, and a feature can be "Limited" because one part of it is not interoperable while the exact declaration you wrote works everywhere. "Cursor styles" is Limited, so `cursor: pointer` is reported — yet it only lacks iOS Safari, where a cursor is meaningless rather than broken. Each finding therefore also names the browsers missing that specific key, or says that the key ships everywhere and the status comes from elsewhere in the feature. Read that line before removing anything: a key that ships everywhere is still not proof the code works, since it may be inert without the parts that do not.

Input parameters:

- `include_passing` (boolean): Also list the features that meet the target, not just the ones that fail.
- `source` (string, required): The CSS source to audit. Malformed CSS is tolerated and scanned best-effort.
- `target` (string): Support target. Either a Baseline level ("baseline-widely", "baseline-newly") or a comma-separated browser list ("chrome 120, safari 17.4, firefox 128"). Known browsers: chrome, chrome_android, edge,…

Output parameters:

- `failing` (integer)
- `featuresChecked` (integer)
- `findings` (array)
- `target` (string)
- `unknown` (integer)

### `dont_make_me_think` (~294 tokens)

Don't Make Me Think

UI/UX guidelines and a review of a page against them. mode="guidelines" returns the principles — Nielsen's 10 heuristics, Hick's and Fitts's laws, WCAG 2.2, neurodiversity-inclusive design, motion and microinteractions (including when Lottie or Rive are worth their bundle cost), SVG craft and animation, light-first theming, lightness and responsiveness — optionally filtered by topic. Read them BEFORE designing or building UI. mode="review" statically reviews supplied HTML and CSS, or a URL, and reports what violates which principle. The review reads source and does not render it, so it cannot measure computed contrast, real target sizes, or where focus lands — it catches what is visible in the markup, which is most of what actually goes wrong.

Input parameters:

- `css` (string): CSS source to review.
- `html` (string): HTML source to review.
- `mode` (string): guidelines: return the principles to design against. review: check HTML/CSS or a URL against them.
- `topic` (string): Restrict guidelines to one area. Omit for all of them. Ignored when mode is "review".
- `url` (string): Page to fetch and review. Only the HTML and its inline styles are read — linked stylesheets are not followed, so pass `css` as well for a full review.

Output parameters:

- `counts` (object)
- `findings` (array)
- `mode` (string)
- `principles` (array)
- `reviewed` (array)
- `version` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lusrodri-css-sota-mcp/css-sota-mcp#diagnostics

## Score history

- 2026-08-03: 56
- 2026-08-02: 55

## Links

- Remote endpoint: https://css-sota-mcp.lusrodri.workers.dev/mcp
- Repository: https://github.com/LuSrodri/css-sota-mcp
- Website: https://css-sota-mcp.pages.dev/
- Changelog RSS feed: https://verifymcp.io/servers/lusrodri-css-sota-mcp/css-sota-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/lusrodri-css-sota-mcp/css-sota-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/lusrodri-css-sota-mcp/css-sota-mcp