Facet
NPM · @CHANDRA14/FACET-CHECK
Check web pages for responsive design problems and screenshot them on phone, tablet and desktop.
Available components
Last scanned (10 hours ago)
Scores higher than 61% 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 Security98
- 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
- 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 21 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 723 tokens (~144/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 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.
- 23 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
- 15 Oct 26 +31
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Tool coverage: 92 functional
- First check of Schema quality: fail functional
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/@chandra14/facet-check@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| 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 →
audit_accessibility ~100
Run an axe-core accessibility audit of a web page on one device and return the WCAG violations with their impact, the affected elements and how to fix them.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | – | Device id, name or size; defaults to an iPhone |
| url | string | yes | Page to load: a full URL, a bare host such as example.com, localhost:3000 for a local dev server, or a path to an HTML file |
No output schema declared.
No examples provided.
check_responsive ~229
Check a web page for responsive design problems on real phone, tablet, laptop and desktop viewports (with each device's pixel ratio, touch support and user agent). Returns the problems found on each device: horizontal scrolling and the elements causing it, tap targets under 24px, text under 12px, form fields that make iOS zoom, viewport meta mistakes, clipped text, oversized or blurry images, fixed headers covering the screen, plus console errors per device. Defaults to the six most common screen sizes. Works with localhost. Use it after changing layout or CSS, or when asked whether a site is mobile friendly.
| Name | Type | Req | Description |
|---|---|---|---|
| devices | array | – | Device ids or names from list_devices ("iphone-17", "Galaxy S26"), free-form sizes ("1024x768"), or a preset: default, popular, phones, latest, tablets, desktops, apple, foldables, extremes. |
| url | string | yes | Page to load: a full URL, a bare host such as example.com, localhost:3000 for a local dev server, or a path to an HTML file |
No output schema declared.
No examples provided.
compare_element ~150
Measure one element of a page on every device: size, position, visibility, font size, display, flex and grid settings. Shows how a component changes across breakpoints.
| Name | Type | Req | Description |
|---|---|---|---|
| devices | array | – | Device ids or names from list_devices ("iphone-17", "Galaxy S26"), free-form sizes ("1024x768"), or a preset: default, popular, phones, latest, tablets, desktops, apple, foldables, extremes. |
| selector | string | yes | CSS selector of the element |
| url | string | yes | Page to load: a full URL, a bare host such as example.com, localhost:3000 for a local dev server, or a path to an HTML file |
No output schema declared.
No examples provided.
list_devices ~71
List the 290+ device profiles (phones, foldables, tablets, laptops, desktops, watches, TVs) with viewport size and pixel ratio, and the named presets.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| query | string | – | Filter by name, e.g. "iphone" or "galaxy" |
No output schema declared.
No examples provided.
screenshot ~173
Screenshot a web page on several devices at once to see how its layout responds. Returns one labelled image per device. Defaults to a phone, a tablet and a laptop. Set fullPage to capture the whole page (cut off at 6000px).
| Name | Type | Req | Description |
|---|---|---|---|
| devices | array | – | Device ids or names from list_devices ("iphone-17", "Galaxy S26"), free-form sizes ("1024x768"), or a preset: default, popular, phones, latest, tablets, desktops, apple, foldables, extremes. |
| fullPage | boolean | – | Capture the whole scrollable page, not only the first screen |
| url | string | yes | Page to load: a full URL, a bare host such as example.com, localhost:3000 for a local dev server, or a path to an HTML file |
No output schema declared.
No examples provided.
How do I install the Facet MCP server?
Facet runs locally as an npm package, launched with npx -y @chandra14/facet-check. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @chandra14/facet-check
claude mcp add chndr-prksh-facet -- npx -y @chandra14/facet-check
What is the Facet MCP server?
Facet is an MCP server listed in the public MCP registry as io.github.chndr-prksh/facet. Check web pages for responsive design problems and screenshot them on phone, tablet and desktop. This page covers its npm package (@chandra14/facet-check).
Is the Facet MCP server safe to use?
Facet scores 79 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. 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 Facet MCP server expose?
Facet exposes 5 tools: check_responsive, screenshot, audit_accessibility, compare_element, list_devices. Their descriptions and schemas cost roughly 723 tokens of context every time the server is loaded.
Is the Facet MCP server still maintained?
Facet 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 Facet MCP server under?
Facet declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.