# npx-vibe

> npx-vibe is an open-source MCP server for security. Read-only npm preflight: reviews what install scripts do before packages run. It runs locally on your machine and is started by your AI client.

- **Kind:** MCP server
- **Pricing:** Open source
- **Platforms:** CLI, macOS, Linux, Windows
- **Website:** https://devrajsinh-jhala.github.io/NPM-Vibe-check/
- **Repository:** https://github.com/devrajsinh-jhala/npm-vibe-check
- **MCP Registry name:** io.github.Devrajsinh-Jhala/npx-vibe
- **Categories:** security, developer tools
- **Listing updated:** 2026-11-16

## About

Since npm 12, install scripts are off until you allow them, but npm only shows the command text. npx-vibe downloads the registry tarball, verifies its integrity, parses it in memory and follows install hooks, bin entry points and the relative imports reachable from them. It then reports Proceed, Caution or Block with the file, line number and matched text behind each finding. No install script is executed during review.

Signals include credential reads combined with network calls, downloaded payload execution, suspicious writes and obfuscation, with known advisories from OSV. Registry age, maintainers and download counts are shown as context but never change the score. Review memory is keyed to the verified tarball hash, so a republished version with different bytes reads as changed. Its approve-scripts command classifies packages as approve, review or deny, and --write records exact-version permissions only for clear-cut cases; anything ambiguous is left for a person. It reads package-lock.json directly, so it works on npm 10 and 11 too.

Exit codes (0 proceed, 2 caution, 3 block, 1 error) make it usable in CI and by agents. A Proceed is not a safety guarantee, scope is bounded rather than exhaustive, and the README states that 3.0.0 is the final planned release with active maintenance ended, though it remains available under MIT.

## Features

- **Evidence-backed verdicts:** Reports Proceed, Caution or Block with file, line and matched text.
- **No execution:** Parses the tarball in memory and never runs the target's scripts.
- **Project scans:** Reviews a project's locked dependency tree from package-lock.json.
- **approve-scripts helper:** Sorts install scripts into approve, review and deny.
- **Tarball-hash memory:** Remembers decisions by verified hash, so republished bytes read as changed.
- **CI-friendly exit codes:** Distinct codes for proceed, caution, block and error.

## Good for

- Decide which install scripts to allow after upgrading to npm 12
- Review a new dependency before adding it
- Gate CI on risky packages in the lockfile
- Let a coding agent check a package before installing it

## Install

### Claude Code (Terminal)

```sh
claude mcp add npx-vibe -- npx -y npx-vibe
```

### Claude Desktop (claude_desktop_config.json)

```json
{
  "mcpServers": {
    "npx-vibe": {
      "command": "npx",
      "args": [
        "-y",
        "npx-vibe"
      ]
    }
  }
}
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "npx-vibe": {
      "command": "npx",
      "args": [
        "-y",
        "npx-vibe"
      ]
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "npx-vibe": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "npx-vibe"
      ]
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "npx-vibe": {
      "command": "npx",
      "args": [
        "-y",
        "npx-vibe"
      ]
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "npx-vibe": {
      "command": "npx",
      "args": [
        "-y",
        "npx-vibe"
      ]
    }
  }
}
```

## FAQ

### Does it run the package it reviews?

No. Scanning is the default and the archive is parsed in memory; execution needs a separate run command.

### Does it need an API key?

No account, AI model or API key is needed for the default scan; Node.js 20 or newer is required.

### Is it still maintained?

The README says 3.0.0 is the final planned release and active maintenance has ended.

### Does a Proceed guarantee safety?

No. The README says it is not a safety guarantee.

### Is npx-vibe free?

Yes. npx-vibe is open source, so you can use and self-host it for free.

### How do I add npx-vibe to Claude Code?

Run this command in your terminal: claude mcp add npx-vibe -- npx -y npx-vibe

### What are the best alternatives to npx-vibe?

The closest alternatives to npx-vibe are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.

## Alternatives

- [REA](https://ai-powered.com/mcp/rea): REA is an open-source MCP server for developer tools.
- [Codebase Memory](https://ai-powered.com/mcp/codebase-memory): Codebase Memory is an open-source MCP server for knowledge and memory.
- [GitHub](https://ai-powered.com/mcp/github-2): GitHub is an open-source MCP server for developer tools.
- [Serena MCP: the IDE for your agent](https://ai-powered.com/mcp/serena-mcp-the-ide-for-your-agent): Serena MCP: the IDE for your agent is an open-source MCP server for developer tools.
- [XERJ](https://ai-powered.com/mcp/xerj): XERJ is an open-source MCP server for knowledge and memory.
- [Ouroboros](https://ai-powered.com/mcp/ouroboros): Ouroboros is an open-source MCP server for developer tools.
- [Claude Code Ultimate Guide](https://ai-powered.com/mcp/claude-code-ultimate-guide): Claude Code Ultimate Guide is an open-source MCP server for ai models and llm tooling.
- [Concord MCP](https://ai-powered.com/mcp/concord-mcp): Concord MCP is a freemium MCP server for developer tools.

---
Source: https://ai-powered.com/mcp/npx-vibe
