uxlint
OfficialRelated Servers
Alternatives to uxlint
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAudit any website for privacy, security, accessibility, and performance issues — with scores, grades, and actionable fix instructions. No account required.34 npmMIT
- AlicenseNot gradedqualityCmaintenanceDesign review for UI code, inside your coding agent. Reviews React, Vue, Svelte, CSS and SwiftUI against 313 rules and returns scored findings with file:line fixes your agent can apply and verify.MIT
- AlicenseAqualityCmaintenancePoint your coding agent at a URL and get a real-browser QA audit: broken signup/login/checkout flows, JS console errors, missing analytics, consent + security headers, mobile tap targets, and accessibility — returned as machine-verified findings graded A-F.442Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to conduct UX reviews of web applications, detecting and fixing AI-generated design and usability issues while preserving the original style.182MIT
- AlicenseAqualityBmaintenanceScans live web pages and single-page apps across multiple viewports to detect WCAG 2.1 AA accessibility violations and returns concrete, browser-verified fixes grounded in WCAG success criteria and techniques.5364 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables automated WCAG 2.2 AA accessibility audits of Figma designs and webpages. Generates detailed markdown reports with severity-grouped violations, specific criterion references, and concrete fix recommendations.-
TDQS
Scored across 5 tools
Each tool targets a distinct phase of the UX lint workflow: guidance, audit creation, report retrieval, screenshot viewing, and fix verification. Even though audit_url and get_report both return findings, one kicks off a new audit while the other reads an existing report, so there is no realistic confusion.
Audit_url, get_shot, get_report, and verify_fix all follow a clear verb_noun pattern. ux_guidance breaks that pattern as a noun_noun name, but it is still readable and does not undermine the overall consistency of the set.
Five tools is a well-scoped size for a UX auditing tool: guidance, audit, report, screenshot, and verify each earn their place. There is no redundancy or bloat.
The tool surface covers the full loop: read guidance, audit a page, retrieve an existing report, view visual evidence, and verify fixes. The optional lint_feedback tool is explicitly conditional and therefore not a real gap.