# 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.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `layout-debug-mcp`: 80/100 (this document), [markdown](https://verifymcp.io/servers/antonchuraev99-layout-debug-mcp/layout-debug-mcp.md), [page](https://verifymcp.io/servers/antonchuraev99-layout-debug-mcp/layout-debug-mcp)

## Channel facts

- Registry: `npm`
- Package: `layout-debug-mcp`
- Version: `0.3.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 15 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 652 tokens (~108/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add antonchuraev99-layout-debug-mcp -- npx -y layout-debug-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "antonchuraev99-layout-debug-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "layout-debug-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "antonchuraev99-layout-debug-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "layout-debug-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add antonchuraev99-layout-debug-mcp -- npx -y layout-debug-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "antonchuraev99-layout-debug-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "layout-debug-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add antonchuraev99-layout-debug-mcp --command npx --arg -y --arg layout-debug-mcp
```

### Hermes

```yaml
mcp_servers:
  antonchuraev99-layout-debug-mcp:
    command: "npx"
    args: ["-y", "layout-debug-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "antonchuraev99-layout-debug-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "layout-debug-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add antonchuraev99-layout-debug-mcp -t stdio -c npx -a -y layout-debug-mcp
```

### Other

```json
{
  "mcpServers": {
    "antonchuraev99-layout-debug-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "layout-debug-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 80, +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.

### 2026-11-02 (score 79, +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.

### 2026-10-31 (score 78, +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.

### 2026-10-28 (score 77, +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.

### 2026-10-26 (score 76, +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.

### 2026-10-24 (score 75, +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.

### 2026-10-22 (score 74, +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.

### 2026-10-21 (score 73, +26)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85

## MCP tools (6)

### `open_window` (~70 tokens)

Open the layout-debug window

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).

### `wait_for_message` (~89 tokens)

Wait for the next message from the window

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.

Input parameters:

- `timeoutSec` (integer): How long to wait, in seconds (default 40)

### `layout_snapshot` (~44 tokens)

Layout tree

Tree of the latest snapshot of the live UI: nodes, sizes, anchors for finding them in code. Truncated by depth.

Input parameters:

- `maxDepth` (integer): Tree depth

### `selected_element` (~36 tokens)

Selected element

What the user has selected in the layout-debug window right now: box, anchors for finding it in code, ancestor chain, live edits.

### `pending_requests` (~112 tokens)

Edit queue

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.

Input parameters:

- `includeConsumed` (boolean): Also show already read edits
- `markConsumed` (boolean): Mark the returned edits as read

### `reply_in_window` (~204 tokens)

Reply in the layout-debug window

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.

Input parameters:

- `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, required): Text for the window chat

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/antonchuraev99-layout-debug-mcp/layout-debug-mcp#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 77
- 2026-10-29: 77
- 2026-10-28: 77
- 2026-10-27: 76
- 2026-10-26: 76
- 2026-10-25: 75
- 2026-10-24: 75
- 2026-10-23: 74
- 2026-10-22: 74
- 2026-10-21: 73
- 2026-10-20: 47
- 2026-10-19: 70
- 2026-10-18: 70
- 2026-10-17: 70
- 2026-10-16: 70
- 2026-10-15: 70
- 2026-10-14: 70
- 2026-10-13: 39
- 2026-10-12: 39
- 2026-10-11: 39

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/layout-debug-mcp
- Socket report: https://socket.dev/npm/package/layout-debug-mcp
- Repository: https://github.com/AntonChuraev99/Layout-debug-mcp
- Changelog RSS feed: https://verifymcp.io/servers/antonchuraev99-layout-debug-mcp/layout-debug-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/antonchuraev99-layout-debug-mcp/layout-debug-mcp.json
- HTML version of this page: https://verifymcp.io/servers/antonchuraev99-layout-debug-mcp/layout-debug-mcp