Driftcheck
NUGET · DRIFTCHECK
Compares a mobile app screen (Android or iOS Simulator) with its Figma design and suggests fixes.
Available components
Last scanned (2 hours ago)
Scores higher than 44% of NuGet servers
Category Design and Media
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 Security88
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Build provenance not yet verified. View diagnostics → Unverified
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 786 tokens (~157/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 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 current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 52
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 nuget/Driftcheck@0.1.1
Provenance Inconclusive
We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.
| Result | Inconclusive |
|---|---|
| Ecosystem | nuget |
| Reason | Package not fetched |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
capture_screen ~102
Takes a screenshot of the device (Android or iOS Simulator) and lists the visible elements with their AutomationId (resource-id on Android, accessibilityIdentifier on iOS), text and bounds in dp or pt. On iOS it takes a few more seconds: it reads the accessibility tree with a UI test, which is built the first time.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceSerial | string|null | – | Device serial or UDID (from list_devices). Optional: uses the first one. |
No output schema declared.
No examples provided.
compare_screen ~402
Compares the app's current screen on the device (Android or iOS Simulator) with a Figma frame. Matches Figma layers to app elements by visible text, name = AutomationId or position, and reports differences in position, size, text and background color. Non-text layers (buttons, fields, lines, icons, images) are found in the screenshot by how they look, comparing box, fill, corner radius, border and content. Reports fidelity (% of elements as in Figma, and how much it changed since the previous comparison) and how to fix each difference with the framework's properties. Generates report.html (interactive report to show the user), side_by_side.png and diff.png (in diff.png: green = matches, orange = differs, dotted blue = where Figma says it should be). Open the images for a visual review. If the screenshot doesn't look like the design (a loading screen), it waits and captures again up to 3 times.
| Name | Type | Req | Description |
|---|---|---|---|
| colorTolerance | number | – | Color tolerance (RGB distance 0–441). Default 24. |
| deviceSerial | string|null | – | Device serial or UDID. Optional: uses the first one. |
| figmaUrl | string | yes | Figma frame URL (Copy link to selection), must include ?node-id= |
| framework | string|null | – | App framework, to write the suggestions with its properties: maui, android (XML views), compose, uikit, swiftui or flutter. Optional. |
| projectPath | string|null | – | App project folder. Optional: if it has files newer than the installed app, the report warns that the app needs to be rebuilt and reinstalled. |
| refresh | boolean | – | true to download the Figma frame again instead of using the local cache. Use it only if the design changed: each download uses Figma API quota. |
| tolerance | number | – | Position/size tolerance in dp or pt. Default 2. |
No output schema declared.
No examples provided.
get_design_specs ~159
Returns the measurements of the Figma frame: position, size, colors, texts and typography of every named layer. Use it BEFORE writing a screen's UI code. If deviceWidth is passed, values are scaled to that width in dp or pt.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceWidth | number|null | – | Logical width of the target device in dp or pt (e.g. 412 for Pixel 7, 402 for iPhone 17). Optional. |
| figmaUrl | string | yes | Figma frame URL (Copy link to selection), must include ?node-id= |
| refresh | boolean | – | true to download the Figma frame again instead of using the local cache. Use it only if the design changed: each download uses Figma API quota. |
No output schema declared.
No examples provided.
import_design ~91
Imports a .driftcheck.json file exported with the Driftcheck plugin in Figma, to compare without the Figma API (no token or no quota). Exports in the Downloads folder are picked up on their own; this is for the ones that ended up in another folder. Then compare with the frame link, as usual.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path of the .driftcheck.json file |
No output schema declared.
No examples provided.
list_devices ~32
Lists the Android devices and emulators connected through adb and, on macOS, the booted iOS simulators.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Driftcheck MCP server?
Driftcheck runs locally as a NuGet package, launched with dnx Driftcheck@0.1.1 --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
nuget · Driftcheck
claude mcp add wilsonvargas-driftcheck -- dnx Driftcheck@0.1.1 --yes
What is the Driftcheck MCP server?
Driftcheck is an MCP server listed in the public MCP registry as io.github.wilsonvargas/driftcheck. Compares a mobile app screen (Android or iOS Simulator) with its Figma design and suggests fixes. This page covers its NuGet package (Driftcheck).
Is the Driftcheck MCP server safe to use?
Driftcheck scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 Driftcheck MCP server expose?
Driftcheck exposes 5 tools: compare_screen, capture_screen, list_devices, get_design_specs, import_design. Their descriptions and schemas cost roughly 786 tokens of context every time the server is loaded.
Is the Driftcheck MCP server still maintained?
Driftcheck 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 Driftcheck MCP server under?
Driftcheck declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.