io.github.LuSrodri/css-sota-mcp

Est-ce que io.github.LuSrodri/css-sota-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.LuSrodri/css-sota-mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 6 outils

• audit_css≈ 854 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • source · string · requis
    The CSS source to audit. Malformed CSS is tolerated and scanned best-effort.
  • target · string · optionnel
    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, firefox, firefox_android, safari, safari_ios, opera, opera_android, samsunginternet_android, webview_android, ie.
  • include_passing · boolean · optionnel
    Also list the features that meet the target, not just the ones that fail.

  Exemple d'appel

  {"name": "audit_css", "arguments": {"source": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"target": "texte", "failing": 1, "unknown": 1, "findings": [], "featuresChecked": 1}}

• check_support≈ 669 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • value · string · optionnel
    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.
  • bcd_key · string · optionnel
    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 · optionnel
    A CSS property name, e.g. "display", "anchor-name". Used when bcd_key is absent.
  • all_browsers · boolean · optionnel
    Include every browser in the dataset (Opera, Samsung Internet, WebView, IE) rather than only the seven that determine Baseline.

  Exemple d'appel

  {"name": "check_support", "arguments": {"value": "texte", "bcd_key": "texte", "property": "texte", "all_browsers": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"key": "texte", "spec": "texte", "mdnUrl": "texte", "support": {}, "baseline": "texte", "resolved": true, "featureId": "texte", "deprecated": true, "suggestions": [], "experimental": true}}

• dont_make_me_think≈ 926 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • css · string · optionnel
    CSS source to review.
  • url · string · optionnel
    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.
  • html · string · optionnel
    HTML source to review.
  • mode · string · optionnel · guidelines | review
    guidelines: return the principles to design against. review: check HTML/CSS or a URL against them.
  • topic · string · optionnel · heuristics | laws | wcag | neurodiversity | motion | svg | theme | performance
    Restrict guidelines to one area. Omit for all of them. Ignored when mode is "review".

  Exemple d'appel

  {"name": "dont_make_me_think", "arguments": {"css": "texte", "url": "texte", "html": "texte", "mode": "guidelines", "topic": "heuristics"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"mode": "texte", "counts": {}, "version": "texte", "findings": [], "reviewed": [], "principles": []}}

• get_feature≈ 571 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "get_feature", "arguments": {"feature_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "name": "texte", "spec": [], "found": true, "mdnUrl": "texte", "bcdKeys": [], "caniuse": [], "baseline": "texte", "browsers": {}, "description": "texte", "suggestions": [], "baselineLowDate": "texte"}}

• search_css_features≈ 672 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • limit · integer · optionnel
    Maximum number of features to return.
  • query · string · optionnel
    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 · optionnel
    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 · optionnel
    Only features that became Baseline Newly available on or before this date (YYYY-MM-DD).
  • baseline · string · optionnel · limited | newly | widely
    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).

  Exemple d'appel

  {"name": "search_css_features", "arguments": {"limit": 1, "query": "texte", "since": "texte", "until": "texte", "baseline": "limited"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"query": "texte", "total": 1, "features": [], "truncated": true}}

• whats_new≈ 552 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · integer · optionnel
    Maximum number of features to return.
  • since · string · optionnel
    Start of the window (YYYY-MM-DD), inclusive. Defaults to 180 days before today.
  • until · string · optionnel
    End of the window (YYYY-MM-DD), inclusive. Defaults to today.
  • transition · string · optionnel · newly | widely | any
    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 available mark, or "any" for both.

  Exemple d'appel

  {"name": "whats_new", "arguments": {"limit": 1, "since": "texte", "until": "texte", "transition": "newly"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"count": 1, "since": "texte", "until": "texte", "features": [], "truncated": true}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://css-sota-mcp.lusrodri.workers.dev/mcp