MCP.Market

lo-eyes MCP server

by sophiacave·io.github.sophiacave/lo-eyes·v1.1.0
No reviews yet

Visual accessibility inspector. WCAG contrast, touch targets, heading audits, screenshots.

B82/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
New

0 stars21 downloads/wk

Reviews

Write one

Nobody has reviewed lo-eyes yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

lo-eyes tools (5, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • eyes_auditwrite action

    Run responsive + accessibility audit across viewports.

  • eyes_compare

    Visual regression: pixel-diff a page against its saved baseline.

  • eyes_devices

    List available device presets with their viewport dimensions.

  • eyes_scan

    Auto-chunk a full page into viewport-sized readable screenshots.

  • eyes_screenshot

    Take a viewport-sized screenshot of a page.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan6 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 109 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How lo-eyes compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 63% of 48,255 servers
Tools
5
the typical server has 7
Tools that change things
20%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
21
more than 8% of 12,191 servers with a package

What its tools let an agent do: 4 read · 1 change

Install lo-eyes in Claude Code, Cursor or VS Code

claude mcp add lo-eyes -- uvx lo-eyes
Add to Cursor

What the publisher says

From the lo-eyes repository's README, as published. We do not edit it. Read it on GitHub

lo-eyes

<!-- mcp-name: io.github.sophiacave/lo-eyes -->

Visual frontend accessibility inspector MCP server. WCAG contrast checking, touch target validation, heading hierarchy audits, responsive screenshots, and S+ grading across mobile and desktop viewports.

Built by Like One Foundation (501(c)(3) nonprofit). Works with any site by changing BASE_URL.

Tools

Device Presets

Audit Checks

  • Overflow: Elements exceeding viewport width (respects scroll parents)
  • Font size: Text below 12px minimum
  • Touch targets: Interactive elements below Apple HIG 44px minimum
  • Heading hierarchy: Skipped heading levels (h1 -> h3)

Grading

Setup

cd lo-eyes
python3 -m venv .venv
source .venv/bin/activate
pip install playwright mcp
python3 -m playwright install chromium

Usage

As MCP Server (Claude Code)

Add to .mcp.json:

{
  "mcpServers": {
    "lo-eyes": {
      "command": "/path/to/lo-eyes/.venv/bin/python3",
      "args": ["/path/to/lo-eyes/server.py"]
    }
  }
}

As CLI

./lo-eyes audit /                           # Audit homepage
./lo-eyes screenshot /blog/ --device ipad   # iPad screenshot
./lo-eyes scan / --device iphone-14         # Full-page chunked scan
./lo-eyes responsive /academy/              # All 5 viewports

Stack

  • Python 3
  • Playwright (headless Chromium)
  • MCP SDK (FastMCP, stdio transport)

License

MIT

Built with love by Like One.

Nothing above is checked by us. What we check is on the safety report.

lo-eyes: common questions

Is lo-eyes MCP server safe?
Mostly: it is graded B (82/100). Read the lo-eyes safety report
How do I install lo-eyes?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does lo-eyes need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is lo-eyes maintained?
The last commit was 147 days ago (2026-06-10). The latest release is v1.1.0.
How does lo-eyes compare with other MCP servers?
safety score 82/100 (higher than 63% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from sophiacave →