Node.js/TypeScript MCP server for Atlassian Confluence. Provides tools enabling AI systems (LLMs) to list/get spaces & pages (content
Nothing to run from here
CSS SOTA is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
6
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
What CSS you can actually ship today, from live Baseline data and MDN browser-compat-data.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http css-sota-mcp https://css-sota-mcp.lusrodri.workers.dev/mcp
# 2 — ask your agent for something these tools do
# search_css_features, whats_new, get_feature and 3 more
CSS SOTA costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LUAll 2 servers
LuSrodri2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http css-sota-mcp https://css-sota-mcp.lusrodri.workers.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Free-text search over feature names and descriptions, e.g. "container queries", "anchor", "scroll". Omit to list all CSS features matching the other filters. |
| baseline | string | no | 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). |
| since | string | no | 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 | no | Only features that became Baseline Newly available on or before this date (YYYY-MM-DD). |
| limit | integer | no | Maximum number of features to return. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | no | Start of the window (YYYY-MM-DD), inclusive. Defaults to 180 days before today. |
| until | string | no | End of the window (YYYY-MM-DD), inclusive. Defaults to today. |
| transition | string | no | 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 avail |
| limit | integer | no | Maximum number of features to return. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feature_id | string | yes | The web-features id, e.g. "anchor-positioning", "container-queries", "subgrid". A display name such as "Anchor positioning" also works. |
| include_mdn | boolean | no | Fetch MDN reference prose for the feature. Set false for a faster, terser answer. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bcd_key | string | no | 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 | no | A CSS property name, e.g. "display", "anchor-name". Used when bcd_key is absent. |
| value | string | no | 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. |
| all_browsers | boolean | no | Include every browser in the dataset (Opera, Samsung Internet, WebView, IE) rather than only the seven that determine Baseline. |
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 v
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source | string | yes | The CSS source to audit. Malformed CSS is tolerated and scanned best-effort. |
| target | string | no | 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, |
| include_passing | boolean | no | Also list the features that meet the target, not just the ones that fail. |
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 BEF
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mode | string | no | guidelines: return the principles to design against. review: check HTML/CSS or a URL against them. |
| topic | string | no | Restrict guidelines to one area. Omit for all of them. Ignored when mode is "review". |
| html | string | no | HTML source to review. |
| css | string | no | CSS source to review. |
| url | string | no | 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. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install CSS SOTA or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish CSS SOTA can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.