Standards by Applied Form
NPM · @APPLIEDFORM/STANDARDS
Lint rendered pages against a design system in a real browser, across six widths, with the fix.
Available components
Last scanned (4 hours ago)
Scores higher than 76% of npm servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 2 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Applied-Form/standards). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 11 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 815 tokens (~90/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 68% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 24 Oct 26 +11
- Malware scan: unverified → pass ▲ security
- Provenance: fail → pass ▲ security
- The attested source repository moved: Applied-Form/standards security
- Stability: unverified → 0.03 ▲ functional
- Package version: 4.0.0 → 4.0.1 functional
- 23 Oct 26 51
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@appliedform/standards@4.0.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Applied-Form/standards |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Applied-Form/standards/.github/workflows/release.yml@refs/tags/v4.0.1 |
| Rekor log index | 3436919452 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7faf401bf2964660575932d7b0054eea8b9a55ec616409c8d5d7c730d0f049b9cf7e714314103f28cf4b920ee833bf9bff4d5a450509119f798e8e32c |
Background: How many MCP packages publish verified provenance →
Dependencies 2 packages
| Packages resolved | 2 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
standards_brand ~56
Derive a complete palette from a hue and a paper colour, measured against every floor, or refuse it with the reasons. Use this instead of inventing a palette.
| Name | Type | Req | Description |
|---|---|---|---|
| hue | number | yes | – |
| paper | string | yes | – |
No output schema declared.
No examples provided.
standards_contrast ~74
Measure a foreground against a background: the WCAG 2 ratio, the floor required at that size and weight, whether it passes, and the APCA reading as an advisory.
| Name | Type | Req | Description |
|---|---|---|---|
| background | string | yes | – |
| foreground | string | yes | – |
| sizePx | number | – | – |
| weight | number | – | – |
No output schema declared.
No examples provided.
standards_drift ~160
Measure what a design system actually is on pages that were not built to this one, and how far they have drifted from it: the palette, spacing step and type scale in use, plus how many values are indistinguishable duplicates. Use this to learn somebody else's system before working in it, rather than guessing from a screenshot.
| Name | Type | Req | Description |
|---|---|---|---|
| declared | array | – | Hex colours the organisation publishes, to report where the guideline and the site disagree. |
| html | array | – | Complete HTML documents to measure. |
| urls | array | – | file:// or https:// pages to measure instead. More pages give a truer system; one page gives one page's habits. |
| viewports | array | – | Widths to measure. Defaults to 1280. |
No output schema declared.
No examples provided.
standards_fix ~143
Apply the fixes Standards can make on its own to a draft, measured in a real browser, and return the fixed HTML with a report: rules fixed, patches applied and refused, and what still fails, by element. No model is called, and a fix that makes any rule worse is not applied. Pass html; what remains needs a change to the markup.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | A complete HTML document to fix. |
| register | string | – | Which register the page is in, if the document does not declare it. |
| viewports | array | – | Widths to measure and fix at. Defaults to the system's four plus two sampled from between them. |
No output schema declared.
No examples provided.
standards_lint ~133
Measure a page against the design system in a real browser and return every violation with the fix. Pass html for a draft, or url for something already served. This is the loop: draft, lint, apply the fixes, lint again.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | – | A complete HTML document to measure. |
| register | string | – | Which register the page is in, if the document does not declare it. |
| url | string | – | A file:// or https:// page to measure instead. |
| viewports | array | – | Widths to measure. Defaults to the system's four plus two sampled from between them. |
No output schema declared.
No examples provided.
standards_move ~62
The recipe for a named compositional move: its cells, layers, voices and ground. One move is active per artefact; ask for the one you need rather than reading all of them.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Omit to list the moves that exist. |
No output schema declared.
No examples provided.
standards_rules ~66
Every rule the gate enforces: what it requires, why, how to fix it, and which WCAG criteria it touches. Filter by group to keep the answer small.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | – |
| wcag | boolean | – | Only rules that touch a WCAG criterion. |
No output schema declared.
No examples provided.
standards_system ~58
Read a design system authored elsewhere (a Standards pack tokens.json) into this one, reporting what it stated, what had to be derived, and what could not be carried across.
| Name | Type | Req | Description |
|---|---|---|---|
| pack | object | yes | The pack's token contract, parsed. |
No output schema declared.
No examples provided.
standards_tokens ~63
The values the system permits: colours, spacing scale, type scale, voices, floors, ratios, and what it declares absent. Ask for this instead of guessing a value.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | colour, spacing, type, floors, absent — omit for all. |
No output schema declared.
No examples provided.
How do I install the Standards by Applied Form MCP server?
Standards by Applied Form runs locally as an npm package, launched with npx -y @appliedform/standards. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @appliedform/standards
claude mcp add applied-form-standards -- npx -y @appliedform/standards
What is the Standards by Applied Form MCP server?
Standards by Applied Form is an MCP server listed in the public MCP registry as io.github.Applied-Form/standards. Lint rendered pages against a design system in a real browser, across six widths, with the fix. This page covers its npm package (@appliedform/standards).
Is the Standards by Applied Form MCP server safe to use?
Standards by Applied Form scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Standards by Applied Form MCP server expose?
Standards by Applied Form exposes 9 tools: standards_lint, standards_fix, standards_rules, standards_tokens, standards_contrast, and 4 more. Their descriptions and schemas cost roughly 815 tokens of context every time the server is loaded.
Is the Standards by Applied Form MCP server still maintained?
Standards by Applied Form is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Standards by Applied Form MCP server under?
Standards by Applied Form declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.