What it does
Standards renders a page in Chromium at four fixed widths and two sampled widths, under reduced motion and in print. It checks every computed value against the rules of a design system and reports what the browser drew rather than what the stylesheet declares. The `standards fix` command reports whether the fixed page passes every checked rule and lists what it could not fix, by rule and element. The `standards audit` command writes a self-contained HTML report, with findings by rule and by page, the related WCAG criteria, and the checks that were not run.
Without a loaded system, `standards lint` checks a page against rules that apply to any page: contrast, focus, target size, overflow, alt text, heading order and motion. Developers who want a design-system gate can set rules to error, warn or off in a config file, although a set of mandatory rules cannot be lowered. For agents, `npx standards mcp-config` prints the server block for Claude Code or Cursor, and the MCP tools `standards_lint` and `standards_fix` are available to them.
Running it requires Chromium, either downloaded by Playwright or set through `STANDARDS_CHROMIUM`. The bundled Reference token file is for testing only; replace it with your own DTCG file or import a Standards pack with `standards system import`. Tests use `node:test`. Published comparisons and evaluation records can be rerun from a clone of the repository, not from the npm package.
Limitations and requirements
Requires Chromium, via Playwright or STANDARDS_CHROMIUM. The bundled token file is a test system, not a design to ship. Mandatory rules cannot be set to warn or off; a config or system that does so is refused with exit status 2. Some systems are refused, including a pack declared without register.pack and a register whose background is not a colour. Known gaps are listed in the publisher's documentation, including unmeasured mandatory rules on undefined registers. The MCP tools measure only the widths a caller names, so horizontal-overflow at 320px is not checked unless 320 is named. Old names (af, af-mcp, AF_BRAND, af.config.json and others) are not read. Uninstall @appliedform/engine before installing @appliedform/standards to avoid EEXIST. Evaluation reruns need a clone and, for model runs, API keys.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
Standards by Applied Form
Lint rendered pages against a design system in a real browser, across six widths, with the fix.
v5.0.0As shown on registry.modelcontextprotocol.io when we last read it