Skip to main content
Glama

Related Servers

Alternatives to Argus

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Browser-based QA testing for AI-built software. Agents open real browsers (via Selenium), navigate pages, fill forms, click buttons, and report findings. Two modes: targeted tests (30-90s) and full-site discovery scans (3-15min).
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI to perform real-browser QA testing on websites via Playwright, finding bugs, accessibility, SEO, and performance issues through natural language conversations.
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Point 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.
      44
      2
      Apache 2.0
    • F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to perform comprehensive web application testing including visual, functional, performance, accessibility, and SEO analysis using browser automation without requiring API keys.
      7
      -
    • A
      license
      A
      quality
      A
      maintenance
      Enables coding agents to independently verify web changes by scanning pages, inspecting UI structure, generating Playwright reproductions, and executing tests with structured QA evidence.
      4
      66 npm
      2
      MIT

    TDQS

    A4.4/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose covering different aspects of testing: session management, interactions, observation, verification, and bug recording. No two tools overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (e.g., click_what, upload_file, verify_persistence). The naming is predictable and informative.

    Tool Count5/5

    With 18 tools, the set is well-scoped for a testing framework. Each tool provides essential functionality without unnecessary redundancy or clutter.

    Completeness4/5

    The tool surface covers the full testing lifecycle from session start to end, including interaction, observation, verification, and bug reporting. Minor gaps like explicit scroll or reload tools are absent but can be worked around.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues