# layout-debug-mcp

Select a layout layer on a live web or Android UI, move it, and hand the edit to any MCP agent.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.2.0
- **Author:** io.github.AntonChuraev99
- **License:** MIT
- **npm:** layout-debug-mcp
- **Source:** https://github.com/AntonChuraev99/Layout-debug-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 2 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-10T07:01:49.247Z
- **Version scanned:** 0.2.0
- **CVEs:** none found by OSV at scan time

## Tools

6 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `open_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 
- `wait_for_message` — 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 l
- `layout_snapshot` — Tree of the latest snapshot of the live UI: nodes, sizes, anchors for finding them in code. Truncated by depth.
- `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` — 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. 
- `reply_in_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

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"layout-debug\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"layout-debug-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/layout-debug-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/layout-debug-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/layout-debug-mcp
- HTML page: https://forgeregistry.com/registry/layout-debug-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.