Skip to main content
Glama
RileyHall99

Argus QA MCP

by RileyHall99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Argus QA MCP

No user-submitted related servers found.

    Related Servers

    • QualityMax QA MCP by Quality-Max

      QualityMax QA MCPofficial

      Quality-Max
      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
      222 npm
      4
      MIT

    • browser-guard-mcp

      egoring
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to automate browsers through Playwright behind multi-layer safety guards, restricting navigation to allowed domains, defaulting to read-only actions, and recording all behavior in audit logs.
      7
      MIT

    • vouch

      hamza-paracha
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to verify application changes by running browser workflows, executing independent state assertions, and producing replayable evidence.
      0
      MIT
    • ProdPoke MCP Server by prodpoke

      ProdPoke MCP Serverofficial

      prodpoke
      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
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A3.9/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes across navigation, interaction, assertions, diagnostics, mocking, and recording. Minor overlap exists between wait_for and the assert_* tools, and between get_console_errors and get_network_requests since both surface failed network activity, but descriptions clarify the intended use.

    Naming Consistency5/5

    All tool names consistently use snake_case with a verb-led pattern such as navigate_url, click_element, assert_visible, mock_route, and start_recording. There are no mixed naming conventions or confusing style deviations.

    Tool Count4/5

    The 18 tools cover a broad browser-automation and QA workflow, and each has a distinct role. The count is slightly above the typical 3-15 range but remains reasonable for a server combining page interaction, assertions, diagnostics, mocking, and recording.

    Completeness4/5

    The surface covers essential browser automation and QA lifecycle operations: navigation, snapshots, interactions, assertions, console/network diagnostics, mocking, and recording with suggested fixes. Some gaps remain, such as file upload, drag-and-drop, and explicit tab/window or storage management, but agents can work around most of these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources