Open Components
REMOTE · MCP.OPENCOMPONENTS.DEV
Guidelines for UI components with a perfect UX, DX and AX, whether humans or AI agents write them.
Available components
Last scanned (10 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Developer Tools
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. How we score → Why this is hard to score →
Endpoint Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 3116 tokens (~79/item across 39 items; 6 tools + 33 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
- Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 0
- Resource “button” now points somewhere else: https://opencomponents.dev/raw/docs/components/button.yaml → https://opencomponents.dev/raw/docs/components/button.md security
- Resource “card” now points somewhere else: https://opencomponents.dev/raw/docs/components/card.yaml → https://opencomponents.dev/raw/docs/components/card.md security
- Resource “checkbox” now points somewhere else: https://opencomponents.dev/raw/docs/components/checkbox.yaml → https://opencomponents.dev/raw/docs/components/checkbox.md security
- Resource “checkbox-group” now points somewhere else: https://opencomponents.dev/raw/docs/components/checkbox-group.yaml → https://opencomponents.dev/raw/docs/components/checkbox-group.md security
- Resource “design-tokens” now points somewhere else: https://opencomponents.dev/raw/docs/foundations/design-tokens.yaml → https://opencomponents.dev/raw/docs/foundations/design-tokens.md security
- Resource “dialog” now points somewhere else: https://opencomponents.dev/raw/docs/components/dialog.yaml → https://opencomponents.dev/raw/docs/components/dialog.md security
- Resource “field” now points somewhere else: https://opencomponents.dev/raw/docs/components/field.yaml → https://opencomponents.dev/raw/docs/components/field.md security
- Resource “input” now points somewhere else: https://opencomponents.dev/raw/docs/components/input.yaml → https://opencomponents.dev/raw/docs/components/input.md security
- Resource “popover” now points somewhere else: https://opencomponents.dev/raw/docs/components/popover.yaml → https://opencomponents.dev/raw/docs/components/popover.md security
- Resource “radio-group” now points somewhere else: https://opencomponents.dev/raw/docs/components/radio-group.yaml → https://opencomponents.dev/raw/docs/components/radio-group.md security
- Resource “spinner” now points somewhere else: https://opencomponents.dev/raw/docs/components/spinner.yaml → https://opencomponents.dev/raw/docs/components/spinner.md security
- Resource “switch” now points somewhere else: https://opencomponents.dev/raw/docs/components/switch.yaml → https://opencomponents.dev/raw/docs/components/switch.md security
- Resource “textarea” now points somewhere else: https://opencomponents.dev/raw/docs/components/textarea.yaml → https://opencomponents.dev/raw/docs/components/textarea.md security
- Resource “tooltip” now points somewhere else: https://opencomponents.dev/raw/docs/components/tooltip.yaml → https://opencomponents.dev/raw/docs/components/tooltip.md security
- 4 Nov 26 +1
- Resource “button” now points somewhere else: https://opencomponents.dev/raw/docs/components/button.yaml → https://opencomponents.dev/raw/docs/components/button.md security
- Resource “card” now points somewhere else: https://opencomponents.dev/raw/docs/components/card.yaml → https://opencomponents.dev/raw/docs/components/card.md security
- Resource “checkbox” now points somewhere else: https://opencomponents.dev/raw/docs/components/checkbox.yaml → https://opencomponents.dev/raw/docs/components/checkbox.md security
- Resource “checkbox-group” now points somewhere else: https://opencomponents.dev/raw/docs/components/checkbox-group.yaml → https://opencomponents.dev/raw/docs/components/checkbox-group.md security
- Resource “design-tokens” now points somewhere else: https://opencomponents.dev/raw/docs/foundations/design-tokens.yaml → https://opencomponents.dev/raw/docs/foundations/design-tokens.md security
- Resource “dialog” now points somewhere else: https://opencomponents.dev/raw/docs/components/dialog.yaml → https://opencomponents.dev/raw/docs/components/dialog.md security
- Resource “field” now points somewhere else: https://opencomponents.dev/raw/docs/components/field.yaml → https://opencomponents.dev/raw/docs/components/field.md security
- Resource “input” now points somewhere else: https://opencomponents.dev/raw/docs/components/input.yaml → https://opencomponents.dev/raw/docs/components/input.md security
- Resource “popover” now points somewhere else: https://opencomponents.dev/raw/docs/components/popover.yaml → https://opencomponents.dev/raw/docs/components/popover.md security
- Resource “radio-group” now points somewhere else: https://opencomponents.dev/raw/docs/components/radio-group.yaml → https://opencomponents.dev/raw/docs/components/radio-group.md security
- Resource “spinner” now points somewhere else: https://opencomponents.dev/raw/docs/components/spinner.yaml → https://opencomponents.dev/raw/docs/components/spinner.md security
- Resource “switch” now points somewhere else: https://opencomponents.dev/raw/docs/components/switch.yaml → https://opencomponents.dev/raw/docs/components/switch.md security
- Resource “textarea” now points somewhere else: https://opencomponents.dev/raw/docs/components/textarea.yaml → https://opencomponents.dev/raw/docs/components/textarea.md security
- Resource “tooltip” now points somewhere else: https://opencomponents.dev/raw/docs/components/tooltip.yaml → https://opencomponents.dev/raw/docs/components/tooltip.md security
- 3 Nov 26 0
- Resource “button” now points somewhere else: https://opencomponents.dev/raw/docs/components/button.yaml → https://opencomponents.dev/raw/docs/components/button.md security
- Resource “card” now points somewhere else: https://opencomponents.dev/raw/docs/components/card.yaml → https://opencomponents.dev/raw/docs/components/card.md security
- Resource “checkbox” now points somewhere else: https://opencomponents.dev/raw/docs/components/checkbox.yaml → https://opencomponents.dev/raw/docs/components/checkbox.md security
- Resource “checkbox-group” now points somewhere else: https://opencomponents.dev/raw/docs/components/checkbox-group.yaml → https://opencomponents.dev/raw/docs/components/checkbox-group.md security
- Resource “design-tokens” now points somewhere else: https://opencomponents.dev/raw/docs/foundations/design-tokens.yaml → https://opencomponents.dev/raw/docs/foundations/design-tokens.md security
- Resource “dialog” now points somewhere else: https://opencomponents.dev/raw/docs/components/dialog.yaml → https://opencomponents.dev/raw/docs/components/dialog.md security
- Resource “field” now points somewhere else: https://opencomponents.dev/raw/docs/components/field.yaml → https://opencomponents.dev/raw/docs/components/field.md security
- Resource “input” now points somewhere else: https://opencomponents.dev/raw/docs/components/input.yaml → https://opencomponents.dev/raw/docs/components/input.md security
- Resource “popover” now points somewhere else: https://opencomponents.dev/raw/docs/components/popover.yaml → https://opencomponents.dev/raw/docs/components/popover.md security
- Resource “radio-group” now points somewhere else: https://opencomponents.dev/raw/docs/components/radio-group.yaml → https://opencomponents.dev/raw/docs/components/radio-group.md security
- Resource “spinner” now points somewhere else: https://opencomponents.dev/raw/docs/components/spinner.yaml → https://opencomponents.dev/raw/docs/components/spinner.md security
- Resource “switch” now points somewhere else: https://opencomponents.dev/raw/docs/components/switch.yaml → https://opencomponents.dev/raw/docs/components/switch.md security
- Resource “textarea” now points somewhere else: https://opencomponents.dev/raw/docs/components/textarea.yaml → https://opencomponents.dev/raw/docs/components/textarea.md security
- Resource “tooltip” now points somewhere else: https://opencomponents.dev/raw/docs/components/tooltip.yaml → https://opencomponents.dev/raw/docs/components/tooltip.md security
- 2 Nov 26 0
- Resource “button” now points somewhere else: https://opencomponents.dev/raw/docs/components/button.yaml → https://opencomponents.dev/raw/docs/components/button.md security
- Resource “card” now points somewhere else: https://opencomponents.dev/raw/docs/components/card.yaml → https://opencomponents.dev/raw/docs/components/card.md security
- Resource “checkbox” now points somewhere else: https://opencomponents.dev/raw/docs/components/checkbox.yaml → https://opencomponents.dev/raw/docs/components/checkbox.md security
- Resource “checkbox-group” now points somewhere else: https://opencomponents.dev/raw/docs/components/checkbox-group.yaml → https://opencomponents.dev/raw/docs/components/checkbox-group.md security
- Resource “design-tokens” now points somewhere else: https://opencomponents.dev/raw/docs/foundations/design-tokens.yaml → https://opencomponents.dev/raw/docs/foundations/design-tokens.md security
- Resource “dialog” now points somewhere else: https://opencomponents.dev/raw/docs/components/dialog.yaml → https://opencomponents.dev/raw/docs/components/dialog.md security
- Resource “field” now points somewhere else: https://opencomponents.dev/raw/docs/components/field.yaml → https://opencomponents.dev/raw/docs/components/field.md security
- Resource “input” now points somewhere else: https://opencomponents.dev/raw/docs/components/input.yaml → https://opencomponents.dev/raw/docs/components/input.md security
- Resource “popover” now points somewhere else: https://opencomponents.dev/raw/docs/components/popover.yaml → https://opencomponents.dev/raw/docs/components/popover.md security
- Resource “radio-group” now points somewhere else: https://opencomponents.dev/raw/docs/components/radio-group.yaml → https://opencomponents.dev/raw/docs/components/radio-group.md security
- Resource “spinner” now points somewhere else: https://opencomponents.dev/raw/docs/components/spinner.yaml → https://opencomponents.dev/raw/docs/components/spinner.md security
- Resource “switch” now points somewhere else: https://opencomponents.dev/raw/docs/components/switch.yaml → https://opencomponents.dev/raw/docs/components/switch.md security
- Resource “textarea” now points somewhere else: https://opencomponents.dev/raw/docs/components/textarea.yaml → https://opencomponents.dev/raw/docs/components/textarea.md security
- Resource “tooltip” now points somewhere else: https://opencomponents.dev/raw/docs/components/tooltip.yaml → https://opencomponents.dev/raw/docs/components/tooltip.md security
- 1 Nov 26 +1
- Resource “button” now points somewhere else: https://opencomponents.dev/raw/docs/components/button.yaml → https://opencomponents.dev/raw/docs/components/button.md security
- Resource “card” now points somewhere else: https://opencomponents.dev/raw/docs/components/card.yaml → https://opencomponents.dev/raw/docs/components/card.md security
- Resource “checkbox” now points somewhere else: https://opencomponents.dev/raw/docs/components/checkbox.yaml → https://opencomponents.dev/raw/docs/components/checkbox.md security
- Resource “checkbox-group” now points somewhere else: https://opencomponents.dev/raw/docs/components/checkbox-group.yaml → https://opencomponents.dev/raw/docs/components/checkbox-group.md security
- Resource “design-tokens” now points somewhere else: https://opencomponents.dev/raw/docs/foundations/design-tokens.yaml → https://opencomponents.dev/raw/docs/foundations/design-tokens.md security
- Resource “dialog” now points somewhere else: https://opencomponents.dev/raw/docs/components/dialog.yaml → https://opencomponents.dev/raw/docs/components/dialog.md security
- Resource “field” now points somewhere else: https://opencomponents.dev/raw/docs/components/field.yaml → https://opencomponents.dev/raw/docs/components/field.md security
- Resource “input” now points somewhere else: https://opencomponents.dev/raw/docs/components/input.yaml → https://opencomponents.dev/raw/docs/components/input.md security
- Resource “popover” now points somewhere else: https://opencomponents.dev/raw/docs/components/popover.yaml → https://opencomponents.dev/raw/docs/components/popover.md security
- Resource “radio-group” now points somewhere else: https://opencomponents.dev/raw/docs/components/radio-group.yaml → https://opencomponents.dev/raw/docs/components/radio-group.md security
- Resource “spinner” now points somewhere else: https://opencomponents.dev/raw/docs/components/spinner.yaml → https://opencomponents.dev/raw/docs/components/spinner.md security
- Resource “switch” now points somewhere else: https://opencomponents.dev/raw/docs/components/switch.yaml → https://opencomponents.dev/raw/docs/components/switch.md security
- Resource “textarea” now points somewhere else: https://opencomponents.dev/raw/docs/components/textarea.yaml → https://opencomponents.dev/raw/docs/components/textarea.md security
- Resource “tooltip” now points somewhere else: https://opencomponents.dev/raw/docs/components/tooltip.yaml → https://opencomponents.dev/raw/docs/components/tooltip.md security
- 31 Oct 26 0
- Resource “button” now points somewhere else: https://opencomponents.dev/raw/docs/components/button.yaml → https://opencomponents.dev/raw/docs/components/button.md security
- Resource “card” now points somewhere else: https://opencomponents.dev/raw/docs/components/card.yaml → https://opencomponents.dev/raw/docs/components/card.md security
- Resource “checkbox” now points somewhere else: https://opencomponents.dev/raw/docs/components/checkbox.yaml → https://opencomponents.dev/raw/docs/components/checkbox.md security
- Resource “checkbox-group” now points somewhere else: https://opencomponents.dev/raw/docs/components/checkbox-group.yaml → https://opencomponents.dev/raw/docs/components/checkbox-group.md security
- Resource “design-tokens” now points somewhere else: https://opencomponents.dev/raw/docs/foundations/design-tokens.yaml → https://opencomponents.dev/raw/docs/foundations/design-tokens.md security
- Resource “dialog” now points somewhere else: https://opencomponents.dev/raw/docs/components/dialog.yaml → https://opencomponents.dev/raw/docs/components/dialog.md security
- Resource “input” now points somewhere else: https://opencomponents.dev/raw/docs/components/input.yaml → https://opencomponents.dev/raw/docs/components/input.md security
- Resource “popover” now points somewhere else: https://opencomponents.dev/raw/docs/components/popover.yaml → https://opencomponents.dev/raw/docs/components/popover.md security
- Resource “radio-group” now points somewhere else: https://opencomponents.dev/raw/docs/components/radio-group.yaml → https://opencomponents.dev/raw/docs/components/radio-group.md security
- Resource “spinner” now points somewhere else: https://opencomponents.dev/raw/docs/components/spinner.yaml → https://opencomponents.dev/raw/docs/components/spinner.md security
- Resource “switch” now points somewhere else: https://opencomponents.dev/raw/docs/components/switch.yaml → https://opencomponents.dev/raw/docs/components/switch.md security
- Resource “textarea” now points somewhere else: https://opencomponents.dev/raw/docs/components/textarea.yaml → https://opencomponents.dev/raw/docs/components/textarea.md security
- Resource “tooltip” now points somewhere else: https://opencomponents.dev/raw/docs/components/tooltip.yaml → https://opencomponents.dev/raw/docs/components/tooltip.md security
- New resource “field” functional
- “get-page” reworded the description of “path” cosmetic
- 30 Oct 26 +1
- Resource “button” now points somewhere else: https://opencomponents.dev/raw/docs/components/button.yaml → https://opencomponents.dev/raw/docs/components/button.md security
- Resource “card” now points somewhere else: https://opencomponents.dev/raw/docs/components/card.yaml → https://opencomponents.dev/raw/docs/components/card.md security
- Resource “checkbox” now points somewhere else: https://opencomponents.dev/raw/docs/components/checkbox.yaml → https://opencomponents.dev/raw/docs/components/checkbox.md security
- Resource “checkbox-group” now points somewhere else: https://opencomponents.dev/raw/docs/components/checkbox-group.yaml → https://opencomponents.dev/raw/docs/components/checkbox-group.md security
- Resource “design-tokens” now points somewhere else: https://opencomponents.dev/raw/docs/foundations/design-tokens.yaml → https://opencomponents.dev/raw/docs/foundations/design-tokens.md security
- Resource “dialog” now points somewhere else: https://opencomponents.dev/raw/docs/components/dialog.yaml → https://opencomponents.dev/raw/docs/components/dialog.md security
- Resource “input” now points somewhere else: https://opencomponents.dev/raw/docs/components/input.yaml → https://opencomponents.dev/raw/docs/components/input.md security
- Resource “popover” now points somewhere else: https://opencomponents.dev/raw/docs/components/popover.yaml → https://opencomponents.dev/raw/docs/components/popover.md security
- Resource “radio-group” now points somewhere else: https://opencomponents.dev/raw/docs/components/radio-group.yaml → https://opencomponents.dev/raw/docs/components/radio-group.md security
- Resource “spinner” now points somewhere else: https://opencomponents.dev/raw/docs/components/spinner.yaml → https://opencomponents.dev/raw/docs/components/spinner.md security
- Resource “switch” now points somewhere else: https://opencomponents.dev/raw/docs/components/switch.yaml → https://opencomponents.dev/raw/docs/components/switch.md security
- Resource “textarea” now points somewhere else: https://opencomponents.dev/raw/docs/components/textarea.yaml → https://opencomponents.dev/raw/docs/components/textarea.md security
- Resource “tooltip” now points somewhere else: https://opencomponents.dev/raw/docs/components/tooltip.yaml → https://opencomponents.dev/raw/docs/components/tooltip.md security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Probed https://mcp.opencomponents.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=opencomponents.dev | CN=WE1,O=Google Trust Services,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 83e73bc5078dab6413ad81b4dbe13fb8 |
| SANs: opencomponents.dev, mcp.opencomponents.dev, *.mcp.opencomponents.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.opencomponents.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| opencomponents.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.opencomponents.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.opencomponents.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get-contract Get Contract ~199
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.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | The component or foundation, like button or design-tokens. |
No output schema declared.
No examples provided.
get-page Get Page ~343
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.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | – | Your framework, to keep only its examples. |
| path | string | yes | The page: its name (introduction, roadmap, mcp-server, agent-plugin, design-tokens, button, card, checkbox-group, checkbox, dialog, field, input, popover, radio-group, spinner, switch, textarea, tool… |
| sections | array | – | 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". |
No output schema declared.
No examples provided.
get-reference-implementation Get Reference Implementation ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | A component with a reference implementation, like button. |
| files | array | – | Only these files, like ["Button.vue"] or ["Button.test.ts"]. Leave it out for every file. |
No output schema declared.
No examples provided.
list-components List Components ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Which components to list. |
| Name | Type | Req | Description |
|---|---|---|---|
| components | array | yes | – |
| total | number | yes | – |
No examples provided.
list-rules List Rules ~458
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.
| Name | Type | Req | Description |
|---|---|---|---|
| automated | boolean | – | 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. |
| check | array | – | How the rule is checked. |
| component | string | – | The component or foundation, like button or design-tokens. |
| ids | array | – | The IDs of the rules to look up, like ["button/keep-focus"]. |
| layer | array | – | ui (how it looks), ux (user experience), dx (developer experience) or ax (agentic experience). |
| level | array | – | – |
| limit | integer | – | How many rules to return, at most. |
| offset | integer | – | Where the page starts: 0, or the nextOffset of the page before. |
| scope | array | – | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| nextOffset | number | – | The offset of the next page, when there is one. |
| rules | array | yes | – |
| total | number | yes | How many rules match, on every page. |
| unknown | array | – | The IDs asked for that no rule has, with the ones that might have been meant. |
No examples provided.
search-docs Search Docs ~217
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.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | – | Only search this page and its rules, like button or design-tokens. |
| limit | integer | – | How many results to return, at most. |
| query | string | yes | A few words, like "focus after delete" or "aria-pressed". |
| type | string | – | Only search sections, or only rules. |
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| results | array | yes | – |
| total | number | yes | How many sections and rules match, of which the best come first. |
No examples provided.
How do I install the Open Components MCP server?
Open Components is a hosted endpoint at https://mcp.opencomponents.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.opencomponents.dev
claude mcp add --transport http com-uxfront-open-components 'https://mcp.opencomponents.dev/mcp'
What is the Open Components MCP server?
Open Components is an MCP server listed in the public MCP registry as com.uxfront/open-components. Guidelines for UI components with a perfect UX, DX and AX, whether humans or AI agents write them. This page covers its hosted endpoint (https://mcp.opencomponents.dev/mcp).
Is the Open Components MCP server safe to use?
Open Components scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Open Components MCP server expose?
Open Components exposes 6 tools: get-contract, get-page, get-reference-implementation, list-components, list-rules, search-docs. Their descriptions and schemas cost roughly 1,556 tokens of context every time the server is loaded.
Does the Open Components MCP server require authentication?
No. We connected to Open Components without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Open Components MCP server still maintained?
Open Components is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Open Components MCP server?
VerifyMCP ran 12 checks on Open Components, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Open Components: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.