MCP.Market

Vigilis MCP server

by piyushpathakqa·io.github.piyushpathakqa/vigilis-mcp·v0.4.1·5 stars
No reviews yet

Gate AI-written tests: heal safe drift, refuse to hide real bugs, sign a verifiable receipt.

B71/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B71/100

full report

Adoption
Growing

5 stars26 downloads/wk

Reviews

Write one

Nobody has reviewed Vigilis yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Vigilis tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

1 medium
  • Code scan2 source files scanned20/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 qualitystatic API keys via environment variables6/15
  • Maintenancelast push 38 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • mediumeval / new Function usedexec.eval
    dist/index.js: …sync testids() { return this.page.$$eval( "[data-testid]", (els) => e…
Overall 71/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Vigilis compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
71/100
higher than 36% of 48,255 servers
GitHub stars
5
more than 83% of 28,688 servers
Downloads a week
26
more than 13% of 12,191 servers with a package

Install Vigilis in Claude Code, Cursor or VS Code

Runs npx -y vigilis-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add vigilis-mcp -- npx -y vigilis-mcp
Add to Cursor

What the publisher says

From the Vigilis repository's README, as published. We do not edit it. Read it on GitHub

👁️ Vigilis

The QA gate for AI-written code. It heals safe test drift, refuses real regressions, and signs every decision into an independent, verifiable receipt.

The problem

Tell any coding agent to "make CI pass" and the cheapest path to green is deleting the test that caught the bug. AI now writes and fixes tests on its own — so the only question that matters is: can you trust what it did?

Vigilis answers it. Point it at the Playwright, Cypress, or Selenium suite you already have. When a test breaks, it decides:

  • Cosmetic drift (a renamed selector) → it heals the locator, re-runs to verify green, opens a PR.
  • A real behaviour change (checkout total went from $49 to $0) → it refuses to touch the test, fails the gate, and surfaces the bug instead of burying it.

And every decision is sealed into a signed, offline-verifiable receipt by an independent notary — so a refusal is something you can prove, not just claim.

Self-healing is the wedge. Verifiable proof is the point.

Where teams point it: gate AI-written code · self-heal without hiding bugs · auditable test runs · audit-grade evidence for SOX / payment controls · agent-native (MCP). → see the use cases

See it refuse a real bug

The agent ran the spec, saw it fail, checked that the selectors were all correct, concluded the app's login was genuinely broken, and refused to heal — then sealed a receipt anyone can verify offline.

Quickstart

npm i -D vigilis                      # in your Playwright / Cypress / Selenium project
npx playwright install chromium       # one-time, for browser automation
export ANTHROPIC_API_KEY=sk-ant-...   # a pay-as-you-go API key (not a Claude.ai subscription)

npx vigilis init                                   # scaffold vigilis.config.json (auto-detects your framework)
npx vigilis generate https://your-app.com --run    # explore the app → write + run a real spec
npx vigilis heal https://your-app.com --spec tests/login.spec.ts   # heal drift → verify green → PR (refuses real bugs)

# already have a suite running in CI? attest the run you just did — no API key, no secrets:
npx playwright test --reporter=json > report.json
npx vigilis attest-run report.json --commit $GITHUB_SHA --exit-code $?
npx vigilis verify .vigilis/attestation/qa-run-*.json    # offline: chain intact, or broken at record #N

Runs in your CI on your own key + chromium. About 10¢ per run on the fast model (--model claude-haiku-4-5); Opus by default for quality.

Why it's different

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Vigilis: common questions

Is Vigilis MCP server safe?
Mostly: it is graded B (71/100). Read the Vigilis safety report
How do I install Vigilis?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Vigilis need an API key?
Yes. The registry entry asks for ANTHROPIC_API_KEY.
Is Vigilis maintained?
The last commit was 77 days ago (2026-08-19). The latest release is v0.4.1.
How does Vigilis compare with other MCP servers?
safety score 71/100 (higher than 36% of 48,255 servers); github stars 5 (more than 83% of 28,688 servers); downloads a week 26 (more than 13% of 12,191 servers with a package). Full comparison.