io.github.vola-trebla/playwright-spatial-layout-mcp
NPM · PLAYWRIGHT-SPATIAL-LAYOUT-MCP · SCANNED AUG 3
MCP server that gives AI agents geometric spatial awareness of web page layouts using Playwright
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- 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 76 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 655 tokens (~109/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 Management23
- Stability observed for 7 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · playwright-spatial-layout-mcp
claude mcp add vola-trebla-playwright-spatial-layout-mcp -- npx -y playwright-spatial-layout-mcp
codex mcp add vola-trebla-playwright-spatial-layout-mcp -- npx -y playwright-spatial-layout-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vola-trebla-playwright-spatial-layout-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"playwright-spatial-layout-mcp"
],
"enabled": true
}
}
} openclaw mcp add vola-trebla-playwright-spatial-layout-mcp --command npx --arg -y --arg playwright-spatial-layout-mcp
mcp_servers:
vola-trebla-playwright-spatial-layout-mcp:
command: "npx"
args: ["-y", "playwright-spatial-layout-mcp"] {
"mcpServers": {
"vola-trebla-playwright-spatial-layout-mcp": {
"command": "npx",
"args": [
"-y",
"playwright-spatial-layout-mcp"
]
}
}
} 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.
- 3 Aug 26 +4
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +45
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: unverified functional
- Licence: MIT functional
- 1 Aug 26 −5
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- 31 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 46
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 97 packages
97 packages in the resolved dependency tree · 95 deprecated · 30 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
calculate_perceptual_contrast ~128
Measures color contrast between a text element and its background using both WCAG 2.x and APCA (WCAG 3.0 draft) formulas simultaneously. Use to answer: does this text pass accessibility contrast requirements? Is it actually readable even if it technically passes the legacy formula?
| Name | Type | Req | Description |
|---|---|---|---|
| background_selector | string | yes | CSS selector for the background element |
| text_selector | string | yes | CSS selector for the text element |
| url | string | yes | URL of the page to analyze |
| viewport | object | — | Viewport size (default: 1280×720) |
No output schema declared.
No examples provided.
compute_viewport_reflow ~100
Measures how element positions and sizes change across multiple viewport sizes. Use to answer: does the layout break on mobile? Which elements shift most when resizing?
| Name | Type | Req | Description |
|---|---|---|---|
| selectors | array | yes | CSS selectors to track across viewports |
| url | string | yes | URL of the page to analyze |
| viewports | array | yes | Viewport sizes to compare — e.g. [{width:375,height:812},{width:1280,height:720}] |
No output schema declared.
No examples provided.
detect_visual_occlusion ~121
Checks if one element physically overlaps another by computing the intersection of their bounding boxes. Use to answer: is this button hidden under a sticky header? Does the cookie banner block the CTA?
| Name | Type | Req | Description |
|---|---|---|---|
| overlay_selector | string | yes | The element that might be on top (e.g., the sticky header) |
| target_selector | string | yes | The element that might be occluded (e.g., the button) |
| url | string | yes | URL of the page to analyze |
| viewport | object | — | Viewport size (default: 1280×720) |
No output schema declared.
No examples provided.
extract_bounding_boxes ~96
Returns the geometric position, size, z-index, and viewport visibility for one or more DOM elements. Use to answer: where exactly on screen is this element? Is it visible? Is it off-screen?
| Name | Type | Req | Description |
|---|---|---|---|
| selectors | array | yes | CSS selectors or Playwright locator strings |
| url | string | yes | URL of the page to analyze |
| viewport | object | — | Viewport size (default: 1280×720) |
No output schema declared.
No examples provided.
verify_spatial_relationships ~107
Validates a set of spatial layout rules — e.g. 'nav must be above hero', 'sidebar must be left of content'. Returns pass/fail per rule with a human-readable reason. Use to answer: does the page layout match the design specification?
| Name | Type | Req | Description |
|---|---|---|---|
| rules | array | yes | List of spatial rules to validate |
| url | string | yes | URL of the page to analyze |
| viewport | object | — | Viewport size (default: 1280×720) |
No output schema declared.
No examples provided.
verify_stacking_context ~103
Reveals the full CSS stacking context chain for an element — which ancestors create new stacking contexts and why. Use to answer: why is my z-index:9999 element still behind a modal? Does this element create its own stacking context?
| Name | Type | Req | Description |
|---|---|---|---|
| selector | string | yes | CSS selector for the element to inspect |
| url | string | yes | URL of the page to analyze |
| viewport | object | — | Viewport size (default: 1280×720) |
No output schema declared.
No examples provided.