QualityMax QA MCP
NPM · @QUALITYMAX/QMAX-MCP
Final release; the checks moved to 9lives (9l mcp). Local QA MCP: scan, inspect, repro, run tests.
Available components
Last scanned (17 hours ago)
Scores higher than 90% of npm servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Quality-Max/qmax-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability52
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1514 tokens (~378/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Oct 26 +38
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.90 ▲ functional
- 13 Oct 26 0
- Package version: 0.9.1 → 0.9.2 functional
- Package version: 0.9.0 → 0.9.1 functional
- 12 Oct 26 −39
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.9.0 → 0.9.1 functional
- 4 Oct 26 0
- Stability: 0.97 → pass security
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Analysed npm/@qualitymax/qmax-mcp@0.9.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Quality-Max/qmax-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Quality-Max/qmax-mcp/.github/workflows/release.yml@refs/tags/v0.9.2 |
| Rekor log index | 3243780882 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:55a5a6a698c0208f0031bf59a14ffd577019dba610b49a85939e9bc87dea31e977bf0303d808e915ed1117d23dfa36909310ebe1da9c8503a65c5ca5e |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
generate_playwright_repro Generate Playwright Repro ~111
Generate a minimal Playwright test from a scan finding, URL, or plain-English goal and write it below the approved workspace directory .qmax-mcp/repros. outputPath must be relative; existing files require overwrite:true after review. No outbound network request is made by generation.
| Name | Type | Req | Description |
|---|---|---|---|
| finding | object | – | – |
| goal | string | – | – |
| outputPath | string | – | – |
| overwrite | boolean | – | – |
| testName | string | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
inspect_page Inspect Page ~170
Read page structure through outbound browser network requests and return headings, forms, buttons, links, inputs, role/name selectors, and data-testid candidates. storageStatePath may name a workspace-relative Playwright storage-state file for authenticated pages; its credentials are loaded into the throwaway browser context and never returned. Because returned page content may be private, authenticated inspection also requires acknowledgePrivateContent:true as explicit caller consent. Does not intentionally modify the target or local filesystem. allowPrivateNetwork:true is limited to deliberate loopback development targets.
| Name | Type | Req | Description |
|---|---|---|---|
| acknowledgePrivateContent | boolean | – | – |
| allowPrivateNetwork | boolean | – | – |
| includeAccessibilityTree | boolean | – | – |
| includeForms | boolean | – | – |
| storageStatePath | string | – | – |
| url | string | yes | – |
| viewport | object | – | – |
No output schema declared.
No examples provided.
run_playwright_test Run Playwright Test ~128
Execute supplied local Playwright code or a local test file. This is a code-execution and artifact-writing boundary: qmax-mcp first requires an MCP human-approval elicitation bound to the exact test digest. The runner may make outbound network requests requested by the test.
| Name | Type | Req | Description |
|---|---|---|---|
| allowedEnv | object | – | – |
| baseUrl | string | – | – |
| browser | string | – | – |
| code | string | – | – |
| headed | boolean | – | – |
| testPath | string | – | – |
| timeoutMs | integer | – | – |
| wallClockTimeoutMs | integer | – | – |
No output schema declared.
No examples provided.
scan_url Scan URL ~319
Inspect a URL with outbound browser and HTTP network requests for console errors, links, accessibility, Core Web Vitals, SEO, security headers, cookie and tracker privacy, mixed content, and page weight. storageStatePath may name a workspace-relative Playwright storage-state file so the checks can run on an authenticated page; its credentials are loaded into the throwaway browser context and never returned. Because returned findings may reflect private content, authenticated scans also require acknowledgePrivateContent:true as explicit caller consent. This may write a local screenshot artifact when screenshot:true. Set format:"markdown" for a shareable graded report, or format:"issue" to render each finding as a self-contained ticket block (summary, steps, expected, actual, environment) ready to paste into a tracker; minSeverity filters that export. baseline takes a previous scan result, or a workspace-relative path to one, and adds a delta reporting which findings are new, fixed, and unchanged — use it to answer whether a change introduced anything rather than comparing two results by eye. allowPrivateNetwork:true is limited to deliberate loopback development targets.
| Name | Type | Req | Description |
|---|---|---|---|
| acknowledgePrivateContent | boolean | – | – |
| allowPrivateNetwork | boolean | – | – |
| baseline | – | – | – |
| checks | array | – | – |
| format | string | – | – |
| maxLinks | integer | – | – |
| minSeverity | string | – | – |
| screenshot | boolean | – | – |
| storageStatePath | string | – | – |
| url | string | yes | – |
| viewport | object | – | – |
| weightBudget | object | – | – |
No output schema declared.
No examples provided.
How do I install the QualityMax QA MCP server?
QualityMax QA MCP runs locally as an npm package, launched with npx -y @qualitymax/qmax-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @qualitymax/qmax-mcp
claude mcp add quality-max-qmax-mcp -- npx -y @qualitymax/qmax-mcp
What is the QualityMax QA MCP server?
QualityMax QA MCP is listed in the public MCP registry as io.github.Quality-Max/qmax-mcp. Final release; the checks moved to 9lives (9l mcp). Local QA MCP: scan, inspect, repro, run tests. This page covers its npm package (@qualitymax/qmax-mcp).
Is the QualityMax QA MCP server safe to use?
QualityMax QA MCP scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the QualityMax QA MCP server expose?
QualityMax QA MCP exposes 4 tools: scan_url, inspect_page, generate_playwright_repro, run_playwright_test. Their descriptions and schemas cost roughly 728 tokens of context every time the server is loaded.
Is the QualityMax QA MCP server still maintained?
QualityMax QA MCP is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the QualityMax QA MCP server under?
QualityMax QA MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.