Metadata-Version: 2.4
Name: vibescan-mcp-server
Version: 0.1.0
Summary: MCP server for VibeScan — scan projects for leaked secrets and security issues
Project-URL: Homepage, https://github.com/Aguantar/vibescan-mcp-server
Project-URL: Repository, https://github.com/Aguantar/vibescan-mcp-server
Author-email: Junsu Lee <aguantar@users.noreply.github.com>
License: MIT
License-File: LICENSE
Keywords: code-review,mcp,secrets,security,vibescan
Classifier: Development Status :: 4 - Beta
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python :: 3
Classifier: Topic :: Security
Requires-Python: >=3.10
Requires-Dist: mcp>=1.0.0
Requires-Dist: vibescan-cli>=0.2.5
Description-Content-Type: text/markdown

# vibescan-mcp-server

mcp-name: io.github.Aguantar/vibescan-mcp-server

MCP server for [VibeScan](https://github.com/Aguantar/vibescan) — scan projects for leaked secrets and security issues directly from Claude Code.

## Features

- **`vibescan_scan`** — Scan a project for secrets, dangerous patterns, and git hygiene issues
- **`vibescan_rules`** — List all 17 detection rules

### What VibeScan detects

- **14 secret categories**: env files, config hardcodes, cloud credentials, Docker/infra, CI/CD pipelines, IDE settings, SSH keys, hardcoded patterns, frontend env vars, data files, doc secrets, mobile files, system configs, editor remnants
- **Dangerous code patterns**: eval(), exec(), shell injection, SQL injection, pickle, innerHTML
- **Git hygiene**: missing .gitignore, unignored .env/.pem/.key files

All scanning runs locally — your code never leaves your machine.

## Installation

```bash
pip install vibescan-mcp-server
```

## Usage with Claude Code

Add to your `.mcp.json`:

```json
{
  "mcpServers": {
    "vibescan": {
      "command": "vibescan-mcp-server"
    }
  }
}
```

Then ask Claude: "scan this project for security issues" or "check for leaked secrets".

## License

MIT
