Layout Debug
NPM · LAYOUT-DEBUG-MCP
Select a layout layer on a live web or Android UI, move it, and hand the edit to any MCP agent.
Available components
Last scanned (1 hour ago)
Scores higher than 65% of npm servers
Category Browser Automation
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 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 15 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 652 tokens (~108/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 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 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 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 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 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 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.
- 26 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 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ 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/layout-debug-mcp@0.3.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 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
layout_snapshot Layout tree ~44
Tree of the latest snapshot of the live UI: nodes, sizes, anchors for finding them in code. Truncated by depth.
| Name | Type | Req | Description |
|---|---|---|---|
| maxDepth | integer | – | Tree depth |
No output schema declared.
No examples provided.
open_window Open the layout-debug window ~70
Start the layout-debug server if it is not running and open its window in the browser. The window shows the live UI (a web page or an Android device); the user selects elements, moves them and writes requests there. Returns the window URL and how to listen for the user's messages (wait_for_message).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pending_requests Edit queue ~112
Edits the user sent from the layout-debug window that no agent has taken yet: comment + element facts + drag measurements. Each edit starts with its requestId. In listen mode use wait_for_message instead. Once you have handled an edit, report back via reply_in_window with that requestId: the user is watching the window, and the id marks that edit as done there.
| Name | Type | Req | Description |
|---|---|---|---|
| includeConsumed | boolean | – | Also show already read edits |
| markConsumed | boolean | – | Mark the returned edits as read |
No output schema declared.
No examples provided.
reply_in_window Reply in the layout-debug window ~204
Write into the chat of the layout-debug window. Call it after handling a message from wait_for_message or pending_requests: the user is watching the window, and without this they will not know what you did. Keep it short: what you changed, in which files, what is left. If the edit could not be made, say why and pass status "error". Write in the same language as the user's comment.
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | – | The requestId of the message you are answering (from wait_for_message or pending_requests). The window ties the reply to that edit and closes it. Omit it for a general note (no edit changes status). |
| role | string | – | assistant — a reply to the user, system — a service note |
| status | string | – | With requestId: "done" when the edit is made, "error" when it could not be made |
| text | string | yes | Text for the window chat |
No output schema declared.
No examples provided.
selected_element Selected element ~36
What the user has selected in the layout-debug window right now: box, anchors for finding it in code, ancestor chain, live edits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wait_for_message Wait for the next message from the window ~89
Wait until the user sends a message or an edit from the layout-debug window, then return it: the comment, the element (anchors for finding it in code) and the live-edit measurements. Returns before common tool timeouts; a timeout result is normal, call it again. Call open_window first.
| Name | Type | Req | Description |
|---|---|---|---|
| timeoutSec | integer | – | How long to wait, in seconds (default 40) |
No output schema declared.
No examples provided.
How do I install the Layout Debug MCP server?
Layout Debug runs locally as an npm package, launched with npx -y layout-debug-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · layout-debug-mcp
claude mcp add antonchuraev99-layout-debug-mcp -- npx -y layout-debug-mcp
What is the Layout Debug MCP server?
Layout Debug is an MCP server listed in the public MCP registry as io.github.AntonChuraev99/layout-debug-mcp. Select a layout layer on a live web or Android UI, move it, and hand the edit to any MCP agent. This page covers its npm package (layout-debug-mcp).
Is the Layout Debug MCP server safe to use?
Layout Debug scores 80 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 Layout Debug MCP server expose?
Layout Debug exposes 6 tools: open_window, wait_for_message, layout_snapshot, selected_element, pending_requests, reply_in_window. Their descriptions and schemas cost roughly 555 tokens of context every time the server is loaded.
Is the Layout Debug MCP server still maintained?
Layout Debug 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 Layout Debug MCP server under?
Layout Debug declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.