vibescan-mcp-server
by Aguantar
README.md
# 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
TDQS
A3.9/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct purposes: one lists detection rules, the other performs scans. There is no overlap or ambiguity.
Naming Consistency5/5
Both tool names follow a consistent 'vibescan_' prefix with a verb_noun pattern ('rules' for list, 'scan' for execute), making it predictable.
Tool Count4/5
With only 2 tools, the set is slightly below the typical 3-15 range, but it is still reasonable for a focused security scanner. Each tool serves a distinct and necessary function.
Completeness4/5
The set covers the core workflow of learning about rules and running scans. A minor gap is the absence of a tool to view a single rule in detail, but the overall surface is adequate for the domain.
Maintenance
ActivityInactive
ResponsivenessUnresponsive