phyll
Related Servers
Alternatives to phyll
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables AI agents to detect, classify, explain, and ethically redesign dark patterns in websites and UI flows.77-
- AlicenseNot gradedqualityBmaintenanceMCP-first UI/UX review layer for AI-generated frontends. Enables reviewing web pages via URL, capturing screenshots, extracting layout metrics, and generating structured repair plans for agents.22 npmApache 2.0
- AlicenseAqualityDmaintenanceLets AI agents visually inspect web elements, test CSS edits in real-time, and iterate until pixel-perfect, functioning like browser DevTools for debugging UI issues.16 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to inspect live web and responsive UIs across mobile and desktop sessions, returning measured text findings on contrast ratios, touch-target sizes, overflow, and theme drift instead of screenshot guesses. It also lets a human and the agent share one live panel, so the agent can navigate, tap, and type while reading the user's pinned notes and frames.177 npmMIT

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.459 npm4MIT- AlicenseNot gradedqualityDmaintenanceEnables designing, modifying, and bug reporting in web apps, sending changes to coding agents via MCP.18 npm46MIT
TDQS
Scored across 18 tools
Most tools map cleanly to distinct phases of the review workflow, such as starting, interacting, capturing evidence, and finishing. The only mild overlap is among capture, screenshot, and probe, but their descriptions clarify when each should be used.
The majority of tools use short lowercase imperative verbs like click, fill, open, and resize, which is readable and predictable. There are minor deviations such as account as a noun and the underscored compounds start_review and finish_review, but the overall style remains consistent.
Eighteen tools is slightly above the ideal range, but the count is justified by the breadth of browser interactions and review steps the server supports. Each tool covers a distinct capability and none feel redundant.
The tool set covers the full review lifecycle: start, navigate, interact, capture evidence, measure, and finish, plus account and upgrade support. Minor gaps like no explicit cancel-review or previous-report listing exist, but they do not block the core workflow.