ego-webqa
Related Servers
Alternatives to ego-webqa
No user-submitted related servers found.
Related Servers
- 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.4426 PyPI2Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI coding agents to open and exercise web applications in an isolated Chromium browser, capture screenshots and runtime/network diagnostics, and run deterministic page checks with linked evidence.121MIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to see, measure, and verify web pages through a real Chrome browser, including screenshots, responsive layout and accessibility audits, pixel diffing against baselines, secure logins, and deployed-fix verification.271MIT

QualityMax QA MCPofficial
AlicenseAqualityAmaintenanceEnables coding agents to independently verify web changes by scanning pages, inspecting UI structure, generating Playwright reproductions, and executing tests with structured QA evidence.4130 npm4MIT- AlicenseAqualityCmaintenanceEnables AI-driven UI inspection and optimization by scanning websites with configurable viewports, capturing screenshots, running deterministic accessibility and layout checks, and generating prioritized reports with fix prompts.2MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to open live, URL-synced mobile and desktop browser sessions of a web or responsive UI and measure them directly — returning contrast ratios, undersized touch targets, overflow, and theme drift as precise text findings tied to selectors, rather than guesses from screenshots. Also lets agents drive the page, capture the exact frame a human is viewing, and read the notes a person pinned to that moment.98 npmMIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of selecting the wrong tool or confusing overlapping purposes. The single tool's intent is explicit and self-contained.
The lone name `audit_web_page` follows a clear verb_noun snake_case convention. There are no competing names to create inconsistency.
A single tool is thin, but it matches the server's narrow, focused purpose of auditing a generated web page in a real browser. It is slightly under-scoped rather than bloated.
The audit operation itself is well-covered and explicitly bounded (delivery usability, not security/WCAG/visual regression/Safari parity). However, there are no supporting operations such as listing past audits, batch auditing multiple pages, or managing the referenced JSON config, leaving some workflow dead ends.