.vscode — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited .vscode (MCP Server) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
An MCP (Model Context Protocol) server that analyzes website UIs and provides precise fix instructions for AI coding assistants. Designed to solve the problem of "messy UI updates" when using agentic code IDEs like GitHub Copilot or Cursor.
When using AI coding assistants to build or update website UIs, the results can sometimes be messy:
Users often struggle to describe exactly what's wrong, saying things like "the navbar is broken" or "the hero section looks weird" - vague descriptions that don't help the AI understand what specific CSS or HTML changes are needed.
This MCP server bridges that gap by:
# Clone the repository
git clone https://github.com/0x-Professor/UIAnalyzerMCP.git
cd UIAnalyzerMCP
# Install dependencies
uv sync
# Install Playwright browsers
uv run playwright install chromium# Run directly
uv run python server.py
# Or use the MCP CLI
uv run mcp run server.py
# For development with inspector
uv run mcp dev server.pyAdd to your VS Code settings.json or MCP configuration:
{
"mcpServers": {
"ui-analyzer": {
"command": "uv",
"args": ["run", "python", "server.py"],
"cwd": "/path/to/UIAnalyzerMCP"
}
}
}Add to your Cursor MCP settings (~/.cursor/mcp.json or project .cursor/mcp.json):
{
"mcpServers": {
"ui-analyzer": {
"command": "uv",
"args": ["run", "python", "server.py"],
"cwd": "/path/to/UIAnalyzerMCP"
}
}
}Add to your Claude Desktop config file:
Windows: %APPDATA%\Claude\claude_desktop_config.json macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"ui-analyzer": {
"command": "uv",
"args": ["run", "python", "server.py"],
"cwd": "C:\\path\\to\\UIAnalyzerMCP"
}
}
}| Tool | Description |
|---|---|
analyze_page | Full UI analysis with elements, issues, and screenshot |
get_fix_instructions | Generate precise fix instructions from vague complaints |
get_screenshot | Capture screenshots with optional element highlighting |
get_element_details | Get detailed info about specific element types |
get_accessibility_snapshot | Extract accessibility tree in YAML format |
get_dom_overview | Get simplified DOM structure overview |
compare_viewports | Compare UI at mobile, tablet, and desktop sizes |
get_tech_stack | Detect frameworks, libraries, and CSS approach |
Full UI analysis of a webpage. Returns elements, issues, accessibility tree, DOM structure, and screenshot.
analyze_page(url="http://localhost:3000", query="the navbar is broken")The main tool for fixing messy UIs. Interprets vague user complaints and generates precise fix instructions.
get_fix_instructions(
url="http://localhost:3000",
user_complaint="the hero section looks weird and buttons are not aligned"
)Returns:
Capture a screenshot with optional element highlighting.
get_screenshot(url="http://localhost:3000", element_type="navbar")
get_screenshot(url="http://localhost:3000", highlight_selector=".hero-section")Get detailed information about specific UI element types.
get_element_details(url="http://localhost:3000", element_type="button")Get the accessibility tree in YAML format for understanding semantic structure.
get_accessibility_snapshot(url="http://localhost:3000")Get a simplified DOM structure overview.
get_dom_overview(url="http://localhost:3000", max_depth=5)Compare the UI at different screen sizes to identify responsive issues.
compare_viewports(url="http://localhost:3000")Detect the technology stack (frameworks, libraries, CSS approach) used on a webpage. Returns framework-specific fix guidance.
get_tech_stack(url="http://localhost:3000")Returns:
npm run devget_fix_instructions:get_fix_instructions(
url="http://localhost:3000",
user_complaint="The navbar is messed up and the hero section has weird spacing"
)Interpreted Problem: User is reporting alignment, spacing issues with the navbar, hero
Affected Elements:
- nav.navbar (selector: nav.navbar)
- section.hero (selector: .hero-section)
Fix Instructions:
1. Fix spacing on navbar
Selector: nav.navbar
CSS Changes:
- padding: 1rem 2rem
- gap: 1rem
- align-items: center
2. Fix spacing on hero
Selector: .hero-section
CSS Changes:
- padding: 4rem 2rem
- margin: 0 auto
- max-width: 1200pxThe analyzer can identify and analyze:
# Run with MCP inspector for debugging
uv run mcp dev server.py
# Run the test suite
uv run python test_mcp_server.pyTest Coverage:
Test artifacts are saved to test_output/ directory:
MIT License - see LICENSE file for details.
Contributions are welcome! Please open an issue or submit a pull request.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.