com.uxfront/open-components

Est-ce que com.uxfront/open-components est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.uxfront/open-components » 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

• get-contract≈ 328 tokens

  Returns the contract of a component or a foundation, as YAML: its API (props, slots and events), its DOM contract (element, role, states, keyboard and parts), its tokens, and every rule in its checklist, each with a stable ID (like button/keep-focus), a level (must or should), a scope (component, usage or both) and how to check it. It holds every requirement in a fraction of the page's length, and it's the same file as https://opencomponents.dev/raw/docs/<path>.yaml. WHEN TO USE: first, before you build, review or explain a component or its tokens. WHEN NOT TO USE: for some of the rules only (by scope, layer, level or check), use list-rules. For the reasoning or the examples behind a rule, use get-page with its sections.

  Paramètres, retour & exemple (1)

  Paramètres

  • component · string · requis · design-tokens | radio-group | button | card | checkbox-group | checkbox | dialog | input
    The component or foundation, like button or design-tokens.

  Exemple d'appel

  {"name": "get-contract", "arguments": {"component": "design-tokens"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get-page≈ 494 tokens

  Reads a docs page as markdown, whole or just the sections you name. Component pages explain why each rule exists, with examples in React, Vue, Svelte, Angular, Solid, Astro and Vanilla: pass a framework to keep only its examples. WHEN TO USE: for the reasoning, an example or the details behind a rule (like the sections ["Loading"] of the button's page), or for a page without a contract, like the introduction or the roadmap. WHEN NOT TO USE: for the requirements alone, use get-contract or list-rules, which are much shorter. To find which page or section covers a topic, use search-docs. A page longer than about 8,000 tokens, like the button's, returns its outline instead: every heading with its anchor and length, so you can ask for the sections you need. So do sections that are too long to return together.

  Paramètres, retour & exemple (3)

  Paramètres

  • path · string · requis
    The page: its name (introduction, roadmap, mcp-server, agent-plugin, design-tokens, radio-group, button, card, checkbox-group, checkbox, dialog, input, spinner, switch, textarea, tooltip), or its path, like /docs/components/button. A URL's #anchor, like the ones search-docs returns, reads that section.
  • sections · array · optionnel
    The sections to read, by heading or anchor, like ["Loading"] or ["#ux-rules"]. Each comes with its sub-sections. Name a parent to tell apart headings that repeat, as in "Every state > Loading".
  • framework · string · optionnel · react | vue | svelte | angular | solid | astro | vanilla
    Your framework, to keep only its examples.

  Exemple d'appel

  {"name": "get-page", "arguments": {"path": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get-reference-implementation≈ 337 tokens

  Returns a shipped component's reference implementation: a Vue 3 component that meets every rule in its checklist, the tests that prove it, the helpers it shares with other components and its theme tokens. The live examples on the site run on this code. WHEN TO USE: to build a component that meets the standard, in Vue or by porting it and its tests to another framework, or to see how a rule is met in code. WHEN NOT TO USE: for the requirements, use get-contract. For how the component is used in another framework, use get-page with that framework.

  Paramètres, retour & exemple (2)

  Paramètres

  • files · array · optionnel
    Only these files, like ["Button.vue"] or ["Button.test.ts"]. Leave it out for every file.
  • component · string · requis · button | card | checkbox | checkbox-group | dialog | input | radio-group | spinner
    A component with a reference implementation, like button.

  Exemple d'appel

  {"name": "get-reference-implementation", "arguments": {"component": "button"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list-components≈ 562 tokens

  Lists what the Open Components standard covers: the components that have shipped (like Button), the foundations every component follows (like Design Tokens), and the components planned on the Roadmap. WHEN TO USE: to check whether a component has a standard yet, to get the name the other tools take for it, or to see what's planned. WHEN NOT TO USE: if you already know the component, call get-contract directly. To find a topic in the docs, use search-docs. Shipped entries come with their page, their contract and how many rules they have. Planned ones have no page, contract or rules yet: hold them to the three layers and Design Tokens, following the Button's structure, as the build-component prompt does.

  Paramètres, retour & exemple (1)

  Paramètres

  • status · string · optionnel · shipped | planned | all
    Which components to list.

  Exemple d'appel

  {"name": "list-components", "arguments": {"status": "shipped"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"total": 1, "components": []}}

• list-rules≈ 1174 tokens

  Lists checklist rules as records, filtered by component, ID, scope, layer, level or check. Each rule has a stable ID to cite in reviews and commits, its level (must or should), its scope, its requirement, how to check it (like a unit test, a review or axe's button-name rule) and a link to it. WHEN TO USE: to review code rule by rule, to get only the rules that apply to a task, to look rules up by ID, or to find the ones a tool can check. Pass scope ["component", "both"] to build or review a component, and ["usage", "both"] to review a screen that uses it. WHEN NOT TO USE: for a component's API, DOM contract and tokens, use get-contract, which has every rule too. It returns up to 50 rules at a time, and total counts every rule that matches. When there are more, pass nextOffset as offset, with the same filters, to get the next page. A component meets the standard when it meets every must rule. Each should rule is expected unless there's a good reason not to follow it.

  Paramètres, retour & exemple (9)

  Paramètres

  • ids · array · optionnel
    The IDs of the rules to look up, like ["button/keep-focus"].
  • check · array · optionnel
    How the rule is checked.
  • layer · array · optionnel
    ui (how it looks), ux (user experience), dx (developer experience) or ax (agentic experience).
  • level · array · optionnel
  • limit · integer · optionnel
    How many rules to return, at most.
  • scope · array · optionnel
    Who meets the rule: component (the component itself), usage (the code that uses it) or both. Rules without a scope, like the Design Tokens', match any scope.
  • offset · integer · optionnel
    Where the page starts: 0, or the nextOffset of the page before.
  • automated · boolean · optionnel
    true for the rules tools check all of (unit tests, axe, a type check, a linter or a visual regression test), false for the ones a person checks, at least in part.
  • component · string · optionnel · design-tokens | radio-group | button | card | checkbox-group | checkbox | dialog | input
    The component or foundation, like button or design-tokens.

  Exemple d'appel

  {"name": "list-rules", "arguments": {"ids": [], "check": [], "layer": [], "level": [], "limit": 1, "scope": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"rules": [], "total": 1, "unknown": [], "nextOffset": 1}}

• search-docs≈ 706 tokens

  Searches the whole standard, every section of every page and every checklist rule, and returns the best matches: where each one is, a short excerpt, and for rules, their ID, level and scope. WHEN TO USE: to find where a topic is covered when you don't know the page or the section, like "focus after delete", "spinner", "aria-pressed" or "dark mode". Then read a section with get-page, or rules with list-rules. WHEN NOT TO USE: to list a component's rules, use list-rules. To see which components there are, use list-components. Search for a few specific words rather than a whole question.

  Paramètres, retour & exemple (4)

  Paramètres

  • type · string · optionnel · section | rule
    Only search sections, or only rules.
  • limit · integer · optionnel
    How many results to return, at most.
  • query · string · requis
    A few words, like "focus after delete" or "aria-pressed".
  • component · string · optionnel · introduction | roadmap | mcp-server | agent-plugin | design-tokens | radio-group | button | card
    Only search this page and its rules, like button or design-tokens.

  Exemple d'appel

  {"name": "search-docs", "arguments": {"query": "texte"}}

  Exemple de retour

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

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://mcp.opencomponents.dev/mcp