io.github.saiffmirza/kiyas
NPM · KIYAS-CLI
AI design fidelity — compare Figma designs or screenshots against rendered UI. No API keys.
Available components
Last scanned (5 hours ago)
Scores higher than 90% 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 Security92
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- 38 of 115 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to saiffmirza/kiyas). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 108 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 805 tokens (~268/item across 3 items; 3 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 Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 −5
- Stability: pass → 0.63 functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 21 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
- 16 Oct 26 +41
- Injection markers: unverified → pass ▲ security
- Stability: unverified → 0.80 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 13 Oct 26 0
- Security disclosure: unverified → 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/kiyas-cli@1.4.0
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 | saiffmirza/kiyas |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/saiffmirza/kiyas/.github/workflows/release.yml@refs/tags/v1.4.0 |
| Rekor log index | 2203481902 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a73e0fc48eb2569f58116ac7e29d26955254573d342e969afeac5a48e6f1131a0d5c251d5f2d4207e951399fd72e0ab3bd53ba1fa74ac3f178ae19eb7 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | unreviewed | node scripts/postinstall.js |
Background: Why install scripts are a supply-chain risk →
Dependencies 115 packages
| Packages resolved | 115 |
|---|---|
| Stale | 38 |
| 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 →
compare ~621
Compare a design against a rendered implementation and return discrepancies (measured on kiyas's golden eval set: 90% mutation recall, zero false positives on identical pairs). Provide `figma` (frame URL) or `designImage` (local path or URL of a design screenshot), plus either `target` (a URL) or `component` (natural-language description; kiyas finds it in the codebase). No Figma token needed for `designImage` — if a Figma MCP server is connected, export the frame as an image with its screenshot tool and pass that here. Returns a reportId you can pass to get_diff_report or list_issues.
| Name | Type | Req | Description |
|---|---|---|---|
| authState | string | – | Path to a Playwright storageState JSON file (cookies + localStorage). Lets kiyas screenshot authenticated views the same way your tests do. Generate with `npx playwright codegen --save-storage=auth.j… |
| colorScheme | string | – | Force prefers-color-scheme for the capture. Default: auto — kiyas detects the design's brightness and retries in the matching scheme. |
| component | string | – | Natural-language description of the component to find in the codebase, e.g. "primary button on the login page". |
| designImage | string | – | Local path, http(s) URL, or base64 data: URI of a design image (e.g. a screenshot) to compare against, instead of a Figma URL. Useful when no Figma token is configured — e.g. export the frame with a… |
| devServer | string | – | Dev server base URL (default: auto-detect a listening server on ports 3000/5173/8080/4200, else http://localhost:3000) |
| figma | string | – | Figma frame/component URL. Provide either `figma` OR `designImage`. |
| fullPage | boolean | – | Capture the full scrollable page when no selector is given (default: true) |
| model | string | – | AI provider (default: claude) |
| name | string | – | Friendly name for the comparison, used in the report header |
| runs | integer | – | Run the comparison N times and keep majority-vote findings — higher consistency at N× cost (default: 1) |
| scale | number | – | Render scale applied to both the Figma export and the screenshot (default: adaptive — 2 for component-sized captures, 1 for large ones) |
| selector | string | – | CSS selector to screenshot a specific element |
| target | string | – | Direct URL of the rendered component. Provide either `target` OR `component`. |
| threshold | string | – | Severity threshold for the rendered HTML report (default: all) |
| viewport | string | – | Viewport for the screenshot, format WIDTHxHEIGHT (default: 1280x720) |
| wait | integer | – | Time in ms to wait after page load before screenshotting |
No output schema declared.
No examples provided.
get_diff_report ~117
Fetch a stored kiyas report by reportId. Defaults to JSON; pass format=html to fetch the rendered report. Returns the artifact path and (by default for JSON) inline content.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Which artifact to return (default: json) |
| includeContent | boolean | – | When true, return the raw file content inline. When false, return only the path. Default: true for json, false for html (HTML is large). |
| reportId | string | yes | Report ID returned from a prior compare call |
No output schema declared.
No examples provided.
list_issues ~67
List discrepancies from a stored kiyas report by reportId, optionally filtered by severity (all | high | medium | low).
| Name | Type | Req | Description |
|---|---|---|---|
| reportId | string | yes | Report ID returned from a prior compare call |
| severity | string | – | Filter to a single severity level (default: all) |
No output schema declared.
No examples provided.
How do I install the io.github.saiffmirza/kiyas MCP server?
io.github.saiffmirza/kiyas runs locally as an npm package, launched with npx -y kiyas-cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · kiyas-cli
claude mcp add saiffmirza-kiyas -- npx -y kiyas-cli
What is the io.github.saiffmirza/kiyas MCP server?
io.github.saiffmirza/kiyas is an MCP server listed in the public MCP registry as io.github.saiffmirza/kiyas. AI design fidelity, compare Figma designs or screenshots against rendered UI. No API keys. This page covers its npm package (kiyas-cli).
Is the io.github.saiffmirza/kiyas MCP server safe to use?
io.github.saiffmirza/kiyas scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 io.github.saiffmirza/kiyas MCP server expose?
io.github.saiffmirza/kiyas exposes 3 tools: compare, get_diff_report, list_issues. Their descriptions and schemas cost roughly 805 tokens of context every time the server is loaded.
Is the io.github.saiffmirza/kiyas MCP server still maintained?
io.github.saiffmirza/kiyas 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 io.github.saiffmirza/kiyas MCP server under?
io.github.saiffmirza/kiyas declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.