Give a coding agent independent QA evidence before it declares a web change done: scan the page, inspect the UI, generate a focused Playwright repro, then review the execution result.
npx -y @qualitymax/qmax-mcpThe four local tools require no QualityMax account, API key, or hosted service.
Ask an MCP-enabled agent to scan the URL it changed, or run the local CLI:
npx -y @qualitymax/qmax-mcp scan https://example.com --format markdownThe report includes a graded summary, findings, concrete reproduction steps, and suggested fixes. One command exercises all four tools against a checked-in, dependency-free fixture — see the reproducible demo.
All nine checks run off a single page load. Pass checks to run a subset.
| Check | What it reports |
|---|---|
console |
JavaScript errors, warnings, and failed requests |
links |
Broken and redirecting links, up to maxLinks |
accessibility |
Missing alt text, unlabelled controls, nameless interactive elements, heading structure |
performance |
Core Web Vitals: LCP, CLS, TTFB, FCP |
seo |
Title and meta description |
security_headers |
CSP, HSTS, X-Content-Type-Options, Referrer-Policy |
cookies |
Missing Secure/HttpOnly/SameSite, third-party cookies, known trackers, tracking before consent |
mixed_content |
HTTP subresources and form actions on an HTTPS page, split into browser-blocked active and passive |
weight |
Transfer bytes, request count, render-blocking resources, oversized and uncompressed assets, third-party cost |
scan_url also returns a metrics block with the measured vitals and the page-weight breakdown, including the slowest requests. Two limits are stated in that block rather than hidden: INP is not measured, because it needs real user interaction, and vitals come from one cold load on the scanning machine, not from field data. Set weightBudget to scan against your own performance budget.
--format markdown opens with the shape of the result, so a human or an agent can see where the problems are before reading a single finding:
Grade: 🔴 F (0 / 100) · 17 issues found
░░░░░░░░░░░░░░░░░░░░░░░░0 / 100
Category Issues Worst Console errors ██░░░░░░░░1🔴 high Accessibility ████████░░3🔴 high Security headers ██████████4🟠 medium Cookies and trackers █████░░░░░2🟠 medium Page weight ██████████4🟠 medium
Each bar is scaled to the noisiest category in that run, so the tallest bar is the thing to fix first. When weight runs, the measurements section also attributes the bytes:
script ████████████████ 18 kB
document ██░░░░░░░░░░░░░░ 3 kB
stylesheet ██░░░░░░░░░░░░░░ 1 kB
image ░░░░░░░░░░░░░░░░ 417 B
Then every finding follows with its severity, a copy-pasteable reproduction, and a suggested fix. Use --format json for the same data as structured output.
| Tool | Local capability | Boundary to review |
|---|---|---|
scan_url |
Scan a URL for console, network, link, accessibility, SEO, security-header, cookie/tracker, mixed-content, page-weight, and Core Web Vitals findings. | It makes outbound requests and can write a screenshot. |
inspect_page |
Return page structure and role/name locator candidates. | It makes outbound requests. |
generate_playwright_repro |
Write a deterministic, workspace-contained Playwright repro. | It writes below .qmax-mcp/repros; overwrites are explicit. |
run_playwright_test |
Execute one local Playwright test and return structured status. | It executes code and writes controlled artifacts; requires an accepted, digest-bound MCP human-approval elicitation. |
The local server does not require an account. Hosted proxy mode is a separate, opt-in connection for account-backed QualityMax capabilities; do not add it unless that capability is needed.
Copy a ready-made, no-credential configuration and the accompanying instruction file for your client:
| Claude Code | Cursor | Codex | VS Code |
|---|---|---|---|
claude/.mcp.json |
cursor/.cursor |
codex/.codex/config.toml |
vscode/.vscode/mcp.json |
The agent setup guide explains the expected approval surfaces and has a generic stdio configuration. The root AGENTS.md is the portable instruction: collect evidence, report unresolved failures, and request approval before mutating files or executing supplied code.
- Local scanning is networked. Private targets are denied by default;
allowPrivateNetwork: trueis only deliberate caller-side consent for a narrow loopback target. - Generated repros stay in a controlled workspace directory. Test runs use a minimal environment and controlled artifact directory.
run_playwright_testuses MCP form elicitation before execution. The server displays the target, side effects, and a SHA-256 digest to the client, and runs only after the client returns an accepted human approval for that exact digest. Clients without form-elicitation support fail closed; a bare caller-supplied boolean is not accepted as proof.- Read the full MCP safety contract and security threat model before publishing or enabling hosted capabilities.
The launch comparison records dated, first-party capability references for TestSprite, BrowserStack, mabl, and Momentic. It is a factual boundary comparison, not a ranking.
The local tools are the open, local-first layer. Hosted QualityMax is an explicit proxy for workspace-backed project, test-case, script, and observability workflows:
QUALITYMAX_API_KEY="<your-api-key>" npx -y @qualitymax/qmax-mcp proxyOnly configure the proxy when a hosted-only capability is needed. The bearer credential is sent only to the pinned https://app.qualitymax.io/api/mcp endpoint; endpoint overrides and redirects are refused.
Use GitHub Issues for non-sensitive usage and documentation support. Do not report vulnerabilities in a public issue; follow the repository security policy. The launch checklist includes the owner checks required before any public announcement.
The runtime requires Node 22.13.0 or newer.
npm install
npx playwright install chromium
npm run check
npm run demonpm run demo starts a dependency-free local fixture, prints a Markdown quality receipt by default, and leaves its generated repro and Playwright artifacts under .qmax-mcp/ for inspection. Use npm run demo -- --format json for a machine-readable receipt.
server.json is the canonical MCP Registry manifest. npm run validate:registry checks it against the official schema without publishing anything. Use npm run version:sync -- <semver> to move every public metadata surface — package.json, package-lock.json, server.json, smithery.yaml and src/metadata.ts — together; npm run check verifies they agree and fails on drift, and npm publish is restricted to the provenance-backed release workflow. The release workflow and rollback procedure are documented in the release runbook.
MIT — Copyright (c) 2026 QualityMax.