Analyzes Firebase security rules to identify potential vulnerabilities and configuration issues.
Performs security audits on project dependencies using npm audit to detect known vulnerabilities and package-level CVEs.
Maps detected security findings to OWASP categories and standards to provide industry-standard vulnerability context.
Scans Prisma schemas to identify security vulnerabilities and configuration risks in database rules.
Analyzes Supabase security rules to identify potential vulnerabilities and configuration issues.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@VibeCheck MCP Serveraudit this codebase for security vulnerabilities and hardcoded secrets"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
VibeCheck MCP Server
AI-powered security audit tool for codebases. Analyzes code for vulnerabilities using real-time data from MITRE CWE and npm audit.
Features
AI-Powered Analysis: Uses MCP sampling to analyze code with Claude
Real-Time CWE Data: Fetches vulnerability definitions from MITRE's CWE API
Dependency Scanning: Uses npm audit for package vulnerability checks
Zero Configuration: No API keys required to get started
Installation
Claude Code (Recommended)
Manual Installation
Add to your Claude Desktop config (~/.claude/claude_desktop_config.json):
From Source
Tools
scan_codebase
Full AI-powered security audit with real-time vulnerability data.
Analyzes:
Authentication and authorization issues
API security vulnerabilities
Database security rules
Exposed secrets and environment variables
Dependency vulnerabilities (via npm audit)
Data flow and injection vulnerabilities
Input:
Or provide files directly:
Categories:
auth- Authentication, sessions, middlewareapi- API routes, endpointsdatabase-rules- Firebase/Supabase rules, Prisma schemassecrets-env- Environment variables, config filesdependencies- package.json vulnerabilitiesdata-flow- User input handling, injection points
check_dependencies
Quick dependency-only scan using npm audit.
Input:
Requirements:
npm installed
package-lock.jsonin the project
Data Sources
Source | Purpose | Auth Required |
MITRE CWE API | Vulnerability definitions | No |
npm audit | Package CVEs | No |
OWASP | Security categories | No (bundled) |
Development
How It Works
File Reading: Reads files from the specified path or accepts file contents directly
Hotspot Collection: Categorizes files by security relevance (auth, api, secrets, etc.)
Dependency Audit: Runs
npm auditif package-lock.json existsAI Analysis: Uses MCP sampling to analyze each category with expert prompts
CWE Enrichment: Fetches relevant CWE definitions from MITRE API
Results: Returns structured findings with severity, CWE/OWASP refs, and remediation steps
Output Format
License
MIT