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

patchpilots-mcp

v0.3.3

Published

PatchPilots security and accessibility agents as an MCP server. Security scanning, supply chain analysis, and WCAG 2.1 AA audits inside Claude Code, Cursor, and any MCP-compatible IDE.

Readme

patchpilots-mcp

npm version license

PatchPilots security and accessibility agents as an MCP server. Catch supply chain attacks, security anti-patterns, and accessibility issues inside Claude Code, Cursor, and any MCP-compatible IDE.

What it does

Three tools, one server:

| Tool | What it scans | |------|--------------| | security_scan | OWASP Top 10 audit — injection, XSS, auth flaws, secrets, crypto issues, misconfigurations. Returns findings with CWE references. | | scan_dependencies | Supply chain risk scanner — typosquatting, postinstall scripts, scope changes, unmaintained packages, known vulnerabilities. | | design_audit | WCAG 2.1 AA accessibility audit — color contrast, semantic HTML, keyboard navigation, ARIA, focus management, design tokens, CSS consistency. Returns findings with WCAG success criterion references. |

All return structured JSON with severity, impact, and remediation for every finding.

Install

Claude Code

// ~/.claude.json or project .claude.json
{
  "mcpServers": {
    "patchpilots": {
      "command": "npx",
      "args": ["-y", "patchpilots-mcp"],
      "env": {
        "ANTHROPIC_API_KEY": "sk-ant-..."
      }
    }
  }
}

Cursor

// .cursor/mcp.json
{
  "mcpServers": {
    "patchpilots": {
      "command": "npx",
      "args": ["-y", "patchpilots-mcp"],
      "env": {
        "ANTHROPIC_API_KEY": "sk-ant-..."
      }
    }
  }
}

VS Code

// .vscode/mcp.json
{
  "servers": {
    "patchpilots": {
      "command": "npx",
      "args": ["-y", "patchpilots-mcp"],
      "env": {
        "ANTHROPIC_API_KEY": "sk-ant-..."
      }
    }
  }
}

API key

The server looks for your Anthropic API key in this order:

  1. ANTHROPIC_API_KEY environment variable
  2. apiKey field in ~/.patchpilots.json

If you already use PatchPilots CLI, your global config works automatically.

Tools

security_scan

path:     string   — file or directory to scan
severity: string   — minimum severity: "critical" | "high" | "medium" | "low" (default: "medium")
roast:    boolean? — brutally honest commentary (default: false)
model:    string?  — Claude model (default: claude-sonnet-4-6)

Returns:

{
  "findings": [
    {
      "file": "src/auth.ts",
      "line": 42,
      "severity": "critical",
      "category": "injection",
      "cwe": "CWE-89",
      "title": "SQL injection in user lookup",
      "description": "User input concatenated into SQL query...",
      "impact": "Full database access...",
      "remediation": "Use parameterized queries..."
    }
  ],
  "riskScore": "critical",
  "summary": "Found 3 security issues..."
}

scan_dependencies

path:   string   — path to package.json or project root
model:  string?  — Claude model (default: claude-sonnet-4-6)

Returns:

{
  "risks": [
    {
      "package": "event-stream",
      "severity": "critical",
      "category": "known-vulnerability",
      "title": "Compromised package with malicious code",
      "description": "...",
      "remediation": "Remove and replace with..."
    }
  ],
  "riskScore": "high",
  "summary": "Found 2 supply chain risks...",
  "stats": {
    "totalDeps": 15,
    "totalDevDeps": 8,
    "risksFound": 2
  }
}

design_audit

path:     string   — file or directory to audit
severity: string   — minimum severity: "critical" | "high" | "medium" | "low" (default: "medium")
roast:    boolean? — brutally honest commentary (default: false)
model:    string?  — Claude model (default: claude-sonnet-4-6)

Returns:

{
  "findings": [
    {
      "file": "src/components/Button.tsx",
      "line": 15,
      "severity": "high",
      "category": "accessibility",
      "wcagRef": "WCAG 2.1 SC 4.1.2",
      "title": "div with onClick instead of button element",
      "description": "Interactive element uses div with onClick...",
      "remediation": "Replace <div onClick=...> with <button>..."
    }
  ],
  "designHealthScore": "high",
  "summary": "Found 4 accessibility issues..."
}

Fun features

Risk emojis — every scan shows a visual risk score: 🟢 none 🟡 low 🟠 medium 🔴 high 💀 critical

Clean scan badges — pass with no findings and get a README badge:

[![Reviewed by PatchPilots](https://img.shields.io/badge/reviewed%20by-PatchPilots%20🔒-blueviolet)](https://github.com/alavesa/patchpilots)

Roast mode — set roast=true on security_scan or design_audit for brutally honest, funny commentary on your findings. Same structured output, spicier language. Try asking your IDE:

"roast the accessibility of my code"

When to use what

| | CLI | GitHub Action | MCP (this) | |---|---|---|---| | When | You run it manually | Every PR automatically | On demand in conversation | | Where | Terminal | GitHub CI | Inside your IDE | | Agents | All 8 | All 8 | Security + deps + design | | Follow-up | Read output, act yourself | Read PR comment, act yourself | Ask assistant to explain and fix | | Safety net | No — you remember to run it | Yes — always runs | No — only when IDE is open |

Need the full crew? Use the PatchPilots CLI — all 8 agents in one command:

npx patchpilots audit ./src --write

Want automatic PR reviews? Add the PatchPilots GitHub Action:

- uses: alavesa/patchpilots@v1
  with:
    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}

All three use the same analysis. The MCP server is for real-time, conversational security and accessibility scanning while you code. The CLI and Action cover the rest.

License

MIT