Weavatrix Quality MCP server
Revision-bound quality planning, execution, evidence, proof, and Playwright authoring.
0 stars147 downloads/wk
Reviews
Write oneNobody has reviewed Weavatrix Quality yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Weavatrix Quality tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it
- Code scansource not scanned: tarball over 25MB25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 14 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
How Weavatrix Quality compares
Against every graded Scraping and browsing MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 91/100
- higher than 80% of 866 Scraping and browsing servers
- Downloads a week
- 147
- more than 64% of 309 Scraping and browsing servers with a package
Release history: 2 versions in the registry since 2026-09-06, latest 2026-09-19, typically one every 13 days.
Install Weavatrix Quality in Claude Code, Cursor or VS Code
Runs npx -y @weavatrix/wvq on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add weavatrix-quality -- npx -y @weavatrix/wvq
What the publisher says
From the Weavatrix Quality repository's README, as published. We do not edit it. Read it on GitHub
Weavatrix Quality (wvq)
Know what your change can break — and whether it is still protected.
Weavatrix Quality (WVQ) turns OpenSpec intent + a Git change into revision-bound proof using your existing runners. The ordinary green path spends 0 runtime LLM tokens. Rust owns policy, selection, evidence, and proof; npm/JS is a typed boundary around the same binaries.
OpenSpec → what must remain true
Weavatrix → what changed and what it can affect
Runners → smallest safe protection set
WVQ → same-revision Proof + composite verdictAlpha 0.1.0-alpha.5. Useful first product loop (one plan → one execution → one report). Not the full v1 DoD — see CHANGELOG and ADR 0003.
Install
# primary distribution (ships wvq + wvq-mcp + wvq-bench for 6 platforms)
npm install --save-dev @weavatrix/wvq@0.1.0-alpha.5
# one-shot without adding a dependency
npx @weavatrix/wvq@0.1.0-alpha.5 --help
# Rust binaries (alpha crates; API unstable)
cargo install wvq-cli --version 0.1.0-alpha.5
cargo install wvq-mcp --version 0.1.0-alpha.5
cargo install wvq-bench --version 0.1.0-alpha.5Unscoped wvq is blocked by npm name-similarity rules — always use @weavatrix/wvq.
5-minute quickstart
cd your-repo
# 1) read-only discovery (never writes, never seals)
npx @weavatrix/wvq@0.1.0-alpha.5 doctor
# 2) write fail-closed policy (first time only)
npx @weavatrix/wvq@0.1.0-alpha.5 init
# 3) compile OpenSpec obligations for a change folder
npx @weavatrix/wvq@0.1.0-alpha.5 spec validate --change current
# 4) run the smallest safe protection set (also builds measured coverage)
npx @weavatrix/wvq@0.1.0-alpha.5 run \
--change current \
--base origin/main \
--head HEAD \
--scope impacted \
--evidence-policy minimal
# After a successful native coverage runner, Weavatrix `coverage_map` reads:
# .weavatrix/coverage/lcov.info
# Quality does not invent a second stack. Playwright is last-resort JS only.
# 5) read-only composite verdict from stored evidence
npx @weavatrix/wvq@0.1.0-alpha.5 verify --change currentNeed bindings before proofs can seal? Start from .weavatrix-quality/config.yaml and the examples.
CLI cookbook
All commands take --repo (default: .). Prefer absolute paths in CI.
Day-to-day cycle
alias wvq='npx @weavatrix/wvq@0.1.0-alpha.5'
wvq doctor
wvq plan --change checkout-fix
wvq select --change checkout-fix --base origin/main --head WORKTREE
wvq run --change checkout-fix --base origin/main --head WORKTREE --scope impacted
wvq status
wvq verify --change checkout-fix
wvq explain <proof-or-finding-id>Spec / seal / debt
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Weavatrix Quality: common questions
- Is Weavatrix Quality MCP server safe?
- Yes, by our scan: it is graded A (91/100). Read the Weavatrix Quality safety report
- How do I install Weavatrix Quality?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Weavatrix Quality need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Weavatrix Quality maintained?
- The last commit was 46 days ago (2026-09-19). The latest release is v0.1.0-alpha.5.
- What can I use instead of Weavatrix Quality?
- Servers from other publishers that do the same job: Playwright MCP server, invisible_playwright_mcp MCP server and CloakBrowser MCP server.
- How does Weavatrix Quality compare with other Scraping and browsing MCP servers?
- safety score 91/100 (higher than 80% of 866 Scraping and browsing servers); downloads a week 147 (more than 64% of 309 Scraping and browsing servers with a package). Full comparison.
Alternatives to Weavatrix Quality
Same job from other publishers: the closest match first, then the best rated.
- PlaywrightPlaywright Tools for MCPnot reviewedWidely usedA
- invisible_playwright_mcpAI browser agent: browses, clicks, types, and reads real web pages from plain-English instructions.not reviewedEstablishedA
- CloakBrowser MCPPlaywright MCP-compatible browser automation bridge for CloakBrowser Chromium.not reviewedEstablishedB
- Flyto CoreExecution engine for AI agents. 412 modules: browser, file, Docker, data, crypto.not reviewedEstablishedB
Behavior Runtime MCPIn-browser ~60Hz behavior tree execution engine with reactive triggers and blackboard projection.not reviewedEstablishedA