npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

vigilis-mcp

v0.4.1

Published

Vigilis MCP server — drive the Vigilis QA tools (generate/triage/heal Playwright, Cypress & Selenium tests) from Claude Desktop/Code over the Model Context Protocol.

Readme

vigilis-mcp

The Vigilis MCP server — drive the QA tools (generate / triage / heal Playwright, Cypress & Selenium tests, plus browser + DOM inspection) straight from Claude Desktop or Claude Code over the Model Context Protocol.

The client LLM (Claude) does the reasoning; this server holds the live browser and runs the tools. No Anthropic API key needed — Claude is the brain. You do need a browser: npx playwright install chromium once. Framework is auto-detected from your project; you can specify one in prompts (e.g. "generate a Cypress test for…").

🌐 vigilis.dev · 💻 GitHub · CLI: vigilis

Claude Code

claude mcp add vigilis -- npx -y vigilis-mcp

…or commit a project .mcp.json:

{
  "mcpServers": {
    "vigilis": { "command": "npx", "args": ["-y", "vigilis-mcp"] }
  }
}

Claude Desktop

Add to claude_desktop_config.json (Settings → Developer → Edit Config), then restart:

{
  "mcpServers": {
    "vigilis": { "command": "npx", "args": ["-y", "vigilis-mcp"] }
  }
}

"vigilis" then appears in the tools menu. Ask Claude things like "generate a Playwright test for the login flow at http://localhost:3000", "generate a Cypress test for the checkout flow", or "this spec is failing — is it a real bug or DOM drift?" and it drives the tools.

What it exposes

The full Vigilis tool registry over MCP: browser_navigate/click/type/snapshot, dom_query/dom_testids, fs_read/write/list, playwright_run, report_verdict.

MIT © Piyush Pathak · provenance powered by Treeship (Zerker Lab)