Skip to main content
Glama

Related Servers

Alternatives to ViewportIQ

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      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.
      24 PyPI
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server enables AI agents to measure live web and responsive UIs — contrast ratios, touch targets, overflow, and theme drift — returning precise, selector-attached findings as text. It also lets a human and agent share the same live mobile and desktop session, with pinned notes and screenshots readable by the agent.
      95 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables cross-browser mobile-first responsive layout auditing and browser automation, including overflow detection, tap target checks, viewport/media query introspection, and screenshot matrices via MCP.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for rendering responsive screenshots of URLs at multiple viewports. Enables agents to capture screenshots and detect visual issues like overflow, clipped elements, and missing alt text.
      MIT

    TDQS

    B3.2/5.0

    Scored across 17 tools

    Disambiguation2/5

    Six tools (audit_layout, detect_overflow, test_responsiveness, inspect_breakpoints, inspect_element_responsiveness, compare_viewports) all perform responsive/overflow analysis with heavily overlapping findings, and inspect_page vs inspect_page_structure vs inspect_element/inspect_styles also overlap on returning DOM and style data. Descriptions hint at differences in scope and output format, but an agent asking 'does this page overflow?' has no obvious single correct choice.

    Naming Consistency5/5

    All 17 names are snake_case and verb-first (navigate_, inspect_, open_, audit_, test_, detect_, compare_, capture_), which maps cleanly to the resource/action being performed. No camelCase or bare-noun outliers.

    Tool Count3/5

    17 tools is at the heavy end for a browser-inspection server, and the count is inflated by overlapping responsive/overflow tools that could be consolidated into two or three with parameters. The core inspection set (open, navigate, inspect DOM/styles/console/network, screenshot) is justified, but the audit family is redundant.

    Completeness4/5

    For a read-only inspection-and-audit server the lifecycle is well covered: open/navigate/reload, DOM and style introspection, console and network capture, responsive testing across breakpoints, and screenshots. The main gap is any form of page interaction (click, type, scroll) or session teardown, which limits verification of dynamic states but is arguably outside the stated audit purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data