Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Weavatrix Quality

by Weavatrixversion 0.1.0-alpha.5i★ –iRuns on your computer
Registry nameio.github.Weavatrix/weavatrix-quality

Install

Overview

Description from the maker (original English)

Revision-bound quality planning, execution, evidence, proof, and Playwright authoring.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Web & browsers

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "weavatrix-quality": {
      "command": "npx",
      "args": [
        "-y",
        "@weavatrix/wvq",
        "mcp",
        "--repo",
        "."
      ]
    }
  }
}

Run this in your terminal

claude mcp add weavatrix-quality -- npx -y @weavatrix/wvq mcp --repo .

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "weavatrix-quality": {
      "command": "npx",
      "args": [
        "-y",
        "@weavatrix/wvq",
        "mcp",
        "--repo",
        "."
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "weavatrix-quality": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@weavatrix/wvq",
        "mcp",
        "--repo",
        "."
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Weavatrix, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Web & browsersi

  • More stars than 0% of the other 875 servers in this category
  • Published to the registry more recently than 42% of the other 875 servers in this category
  • Basic checks equal to or better than 100% of the other 875 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Weavatrix Quality safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0-alpha.5) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Browser Use

by browser-use

Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.

Computer or cloud★ 120,087MITUpdated 16 days ago
Install

Chrome DevTools MCP

by ChromeDevTools

Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.

Runs on your computer★ 54,821Apache-2.0Updated 15 days ago
Install

MCP Server Browser

by bytedance

MCP server for browser use access

Runs on your computer★ 39,550Apache-2.0Updated 14 months ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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 verdict

SurfacePackage
npm (primary)@weavatrix/wvq
MCP Registryio.github.Weavatrix/weavatrix-quality
crates.iowvq-cli · wvq-mcp · wvq-bench
Releasev0.1.0-alpha.5

Alpha `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.5

Unscoped 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 current

Need 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

Spec / seal / debt
wvq spec validate --change checkout-fix

wvq spec seal --change checkout-fix # fail-closed; needs valid obligations wvq debt --change checkout-fix --base origin/main --head HEAD wvq baseline --change checkout-fix --decision observed_only # CLI-only, not MCP

Observe-only CI (Stage A)
# facts stay honest (UNPROVEN / NOT_ENOUGH_EVIDENCE), process exit stays 0

wvq verify --change checkout-fix --observe-only true

Browser record → promote later via MCP/Studio
wvq record --change checkout-fix --route /checkout

wvq ingest-journal --file .weavatrix-quality/journals/session.json wvq ingest-cassette --file captures/checkout.har --origin https://app.example.test

Shadow selected-vs-full (bench)
wvq bench --repo . --change checkout-fix --base origin/main --head WORKTREE

or: npx @weavatrix/wvq@0.1.0-alpha.5 bench --repo . ...

Exit codes
CodeMeaning
0success / observe-only (even when verdict is unresolved)
1unresolved evidence / ordinary failure
2blocking CONTRADICTED verify

Full CLI surface: wvq --help. Deep product rules live in docs/STATUS.md.


MCP cookbook

WVQ ships as an mcport MCP host. Default profile = 7 tools, no shell, large artifacts as handles only.

Cursor (mcp.json)
{

"mcpServers": { "weavatrix-quality": { "command": "npx", "args": [ "-y", "@weavatrix/wvq@0.1.0-alpha.5", "mcp", "--repo", "C:/path/to/your-repo" ] } } }

Claude Desktop
{

"mcpServers": { "weavatrix-quality": { "command": "npx", "args": ["-y", "@weavatrix/wvq@0.1.0-alpha.5", "mcp", "--repo", "/Users/you/src/app"] } } }

Default tools (coding agents)
quality_context   quality_plan   quality_run   quality_status

quality_verify quality_explain quality_evidence

Example agent workflow:

  1. quality_context — what obligations exist for this change
  2. quality_plan — gaps vs existing proofs (no execution)
  3. quality_run — execute impacted protection and publish .weavatrix/coverage/lcov.info for Weavatrix coverage_map
  4. quality_verify — composite verdict
  5. quality_explain / quality_evidence — drill into a handle or id
Authoring profile (TestProgram draft → preview → promote)
npx @weavatrix/wvq@0.1.0-alpha.5 mcp --repo . \

--profile authoring \ --change checkout-fix \ --base origin/main \ --head WORKTREE

quality_test_draft    quality_test_validate   quality_test_preview

quality_test_promote quality_test_record quality_test_heal

doctor / init / baseline stay CLI-only so agents cannot treat discovery or an observed baseline as authority.

More configs and JSON-RPC samples: examples/mcp/.


JavaScript library cookbook

npm install --save-dev @weavatrix/wvq@0.1.0-alpha.5
Plan → run → verify
import { WvqClient } from '@weavatrix/wvq'

const wvq = new WvqClient({ repo: process.cwd() })

const plan = await wvq.plan({ change: 'checkout-fix' }) console.log(plan.obligations, plan.gaps)

const run = await wvq.run({ change: 'checkout-fix', base: 'origin/main', head: 'WORKTREE', scope: 'impacted', evidencePolicy: 'minimal', }) console.log(run.run_id, run.outcome, run.scope_reason)

const verify = await wvq.verify({ change: 'checkout-fix' }) console.log(verify.state, verify.quality.proof, verify.base, verify.head)

if (verify.blocking) { for (const reason of verify.quality.blocking_reasons) { console.error(reason.code, reason.detail) } process.exit(2) }

Spec / select / debt / explain
await wvq.specValidate({ change: 'checkout-fix' })

const selected = await wvq.select({ change: 'checkout-fix', base: 'origin/main', head: 'HEAD', }) console.log(selected.selected, selected.uncovered_mandatory)

const debt = await wvq.debt({ change: 'checkout-fix', base: 'origin/main', head: 'HEAD', }) console.log({ new: debt.new, fixed: debt.fixed, returned: debt.returned })

const detail = await wvq.explain(verify.proofs[0]?.id) console.log(detail.summary, detail.provenance)

MCP client from Node (default + authoring)
import { WvqMcpClient } from '@weavatrix/wvq/mcp'

const mcp = new WvqMcpClient({ repo: process.cwd(), profile: 'default', change: 'checkout-fix', }) const status = await mcp.call('quality_status', { change: 'checkout-fix' }) const verdict = await mcp.call('quality_verify', { change: 'checkout-fix' })

const authoring = new WvqMcpClient({ repo: process.cwd(), profile: 'authoring', change: 'checkout-fix', base: 'origin/main', head: 'WORKTREE', }) const draft = await authoring.draft() const validated = await authoring.validate(candidateProgram) const preview = await authoring.preview(validated.program, { screenshot: true, trace: true, }) if (preview.passed) { await authoring.promote(preview.preview_id, validated.program) }

CI snippet (GitHub Actions)
- uses: actions/setup-node@v4

with: node-version: 24

  • run: npx @weavatrix/wvq@0.1.0-alpha.5 doctor
  • run: > npx @weavatrix/wvq@0.1.0-alpha.5 run --change current --base origin/${{ github.base_ref }} --head HEAD --scope impacted --evidence-policy minimal
  • run: npx @weavatrix/wvq@0.1.0-alpha.5 verify --change current --observe-only true

Runnable copies: examples/js/ · examples/cli/.


Repository policy

.weavatrix-quality/config.yaml binds concrete tests to obligation IDs. A green suite without this mapping stays UNPROVEN.

quality_policy_v: 1

test_bindings:

  • path: tests/permissions.spec.ts runner: playwright case: viewer cannot delete a widget obligations: [permissions-delete] cost: 10 flake_penalty: 0

browser: base_url: http://127.0.0.1:3000 engine: chromium headless: true module_root: .

wvq init writes a fail-closed starter. This repo dogfoods change wvq-invariants — see examples/cli/dogfood.sh.

Browser preview needs Playwright in the target repo:

npm install --save-dev playwright

npx playwright install chromium


What WVQ is / is not

IsIs not
Spec-to-Proof over existing runnersA second test framework
Weavatrix-backed impact + selectionA browser engine (Playwright stays)
CLI + MCP + typed JS boundaryAn OpenSpec fork
0 LLM tokens on the green pathAutomatic silent oracle healing
Fail-closed on unknown schemasA single global “quality %”

Place in the ecosystem:

Weavatrix          UNDERSTAND   what exists in source

Weavatrix Quality PROVE what must still be true after this change Weavatrix Loom COMPOSE capabilities into ordinary Rust


Build from source

Requires Rust 1.89+.

cargo test --workspace --locked

cargo clippy --workspace --all-targets --locked -- -D warnings


Docs map

DocUse when
examples/Copy-paste CLI / MCP / JS
CHANGELOGWhat alpha ships
docs/STATUS.mdMaturity matrix + next task
docs/adr/0003-…Alpha vs deferred v1
docs/CANONICAL-MASTER-SPEC.mdNormative product design

License

MIT. See LICENSE.

Ask PopNx