Argus
Related Servers
Alternatives to Argus
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceBrowser-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).-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to drive a real browser like a person — crawling every page and role, running real user journeys, and auditing controls a DOM-based test misses — so UI, accessibility and permission bugs are found and only the screens affected by recent changes are re-tested. Runs are script-driven and read-only by default, so testing costs no model tokens and nothing about the app is sent to an AI.MIT

QAJev MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to crawl websites, run plain-language goal-based checks, read reports and screenshots, and follow or stop runs through MCP.3MIT- AlicenseAqualityAmaintenanceAI-powered QA testing platform — catches JS errors, accessibility failures, visual regressions, API loops, security issues, and more via Chrome DevTools MCP955 npm5MIT

ProdPoke MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceEnables AI to perform real-browser QA testing on websites via Playwright, finding bugs, accessibility, SEO, and performance issues through natural language conversations.1MIT- AlicenseAqualityCmaintenancePoint 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.4438 PyPI2Apache 2.0
TDQS
Scored across 18 tools
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.
All tools follow a consistent snake_case verb_noun pattern (e.g., click_what, upload_file, verify_persistence). The naming is predictable and informative.
With 18 tools, the set is well-scoped for a testing framework. Each tool provides essential functionality without unnecessary redundancy or clutter.
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.