# Open Components

> Guidelines for UI components with a perfect UX, DX and AX, whether humans or AI agents write them.

- name: com.uxfront/open-components
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 95/100
- quality: 86/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.uxfront%2Fopen-components
- tools: https://api.protogrid.dev/v1/servers/com.uxfront%2Fopen-components/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "open-components": {
      "type": "http",
      "url": "https://mcp.opencomponents.dev/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 98
- freshness: 100
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-95% +updated-10d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 86/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 6 of 6 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 2,383 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 75 (weight 15)

- warn `stability.changes`: 31 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 6, about 2,383 tokens to load them all
- tool set hash: 8a3ae84e084d9041f5ef0767bc63c77d
- tools last changed: 2026-10-19T11:22:10.575Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.uxfront/open-components.svg)](https://protogrid.dev/servers/com.uxfront/open-components)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-19 `search-docs` changed (inputSchema)
- 2026-10-19 `list-rules` changed (inputSchema)
- 2026-10-19 `get-reference-implementation` changed (inputSchema)
- 2026-10-19 `get-page` changed (inputSchema)
- 2026-10-19 `get-contract` changed (inputSchema)
- 2026-10-18 `search-docs` changed (inputSchema)
- 2026-10-18 `list-rules` changed (inputSchema)
- 2026-10-18 `get-reference-implementation` changed (inputSchema)
- 2026-10-18 `get-page` changed (inputSchema)
- 2026-10-18 `get-contract` changed (inputSchema)

Full history: https://api.protogrid.dev/v1/servers/com.uxfront%2Fopen-components/changes

## Remotes

- https://mcp.opencomponents.dev/mcp (streamable-http, auth none, reachable true, uptime30d 0.9459459)

## Packages

_none_

## Tools (6)

- `get-contract`: 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.
- `get-page`: 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.
- `get-reference-implementation`: 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.
- `list-components`: 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.
- `list-rules`: 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.
- `search-docs`: 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.