Skip to main content
Glama
Sign In
Tester Agent

Tester Agent

by datb2404981
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Tester Agent

No user-submitted related servers found.

    Related Servers

    • QualityMax QA MCP

      QualityMax QA MCPofficial

      Quality-Max
      A
      license
      A
      quality
      B
      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
      85 npm
      4
      MIT

    • uiwalk

      mrigsby
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides browser control and testing tools for AI agents, enabling step-by-step web app testing with user confirmation, bug evidence capture, and report generation.
      1
      MIT

    • Argus QA MCP

      RileyHall99
      A
      license
      A
      quality
      C
      maintenance
      Gives AI agents a real Chromium browser via Playwright to QA-test web apps, with pass/fail assertions, network mocking, recorded traces and reports, and safety guards that block live payment traffic. Test outcomes come back as explained verdicts suitable for review or email delivery.
      18
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 18 tools

    Disambiguation3/5

    Most tools have distinct roles and the descriptions explicitly steer usage (tester_test_web tells the caller to use tester_browser_* for flows), but two pairs genuinely overlap: tester_browser_see vs tester_browser_inspect both return rendered content and JS errors, and tester_browser_layout_audit vs tester_browser_visual_finding both concern layout/visual defects. tester_test_web also partially duplicates the one-shot check path of tester_browser_case kind=check.

    Naming Consistency4/5

    A predictable scheme is used: tester_* for project/report operations and tester_browser_* for the 13-14 session tools, all snake_case with noun or verb tails. Minor deviations exist in verb style (tester_browser_step, tester_browser_case are noun-like rather than imperative), but the prefix grouping makes the set easy to scan.

    Tool Count3/5

    18 tools is on the heavy side for a single-purpose agent and sits in the 16-25 'feels heavy' band. Several audit tools (security/layout/accessibility) could plausibly be one parameterized audit tool, and see/inspect could merge, but each tool still maps to a discrete step of a QA pipeline.

    Completeness5/5

    Coverage is strong end to end: project registration/listing, session start and viewport control, case/step/assert lifecycle, multi-dimension auditing, visual-finding capture, and PASS/FAIL/BLOCKED report persistence plus artifact listing/reading. Only a session-close/cleanup or project-delete operation is absent, which doesn't block the main workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources