codecheck
Related Servers
Alternatives to codecheck
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).-
- AlicenseAqualityCmaintenanceRenders HTML in a headless browser and detects layout defects numerically, such as text overlaps, placeholder leftovers, and element overflow, without requiring baseline images.1MIT
- FlicenseNot gradedqualityBmaintenanceBrowser-backed QA MCP server that lets coding agents test web apps, collect browser evidence, and return fix-ready reports before shipping.-
- AlicenseBqualityNot gradedmaintenanceProvides comprehensive website validation across performance, accessibility, SEO, and security dimensions using multiple testing services including WebPageTest, Google PageSpeed Insights, Axe DevTools, Mozilla Observatory, and SSL Labs. Enables automated website health assessments through browser automation and API integrations.2123 npm1-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to review Ceramic and ordinary websites with desktop/mobile browser QA, deterministic design and accessibility checks, optional visual judgement, and repeatable fix verification backed by preserved screenshots and reports.MIT
- FlicenseNot gradedqualityDmaintenanceLaunches multiple Browser-Use agents to automatically test websites for UI bugs, broken links, accessibility issues, and other technical problems on both live and localhost sites.833-
TDQS
Scored across 8 tools
full_qa overlaps heavily with the individual test_* tools and quick_security, since it bundles the same checks. audit_project also subsumes most of these checks, making it unclear when to use the broad tools versus the granular ones.
The test_* tools follow a consistent pattern, but full_qa, quick_security, audit_project, and compare_reports break it. The mix of adjective_noun, verb_noun, and test_* styles creates a somewhat inconsistent naming scheme.
8 tools is a reasonable count for a QA/audit server. However, full_qa and audit_project duplicate much of the test_* suite, so the same functionality could be consolidated slightly.
The set covers interactions, layout, fonts, images, security, full audits, and report comparison, forming a solid QA workflow. Minor gaps like dedicated performance or SEO checks exist, but they are not essential to the stated purpose.