Server facts
guardvibe MCP Server
Project
- Author
- goklab
- Repository
- github.com/goklab/guardvibe
- License
- Not specified
- Category
- Security & Reverse Engineering
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 6
- Last commit
- Data as of
Tags
- Supabase
- ai security
- clerk
- code audit
- mcp
- nextjs
- owasp
- prisma
- sast
- security
- stripe
- vibe coding
Overview
Security review in GuardVibe spans individual edits, repository scans, and changes prepared for review. Developers working through MCP-compatible coding agents can inspect supplied code or files on disk, scan staged changes, and limit checks to files modified since a Git reference. Dataflow analysis follows potentially unsafe input within files and across module boundaries. Dependency checks consult OSV for package vulnerabilities, while separate tools assess npm package health and search current files or Git history for exposed credentials. Configuration audits examine related project settings together, and configuration comparisons flag changes that weaken protections.
Findings can lead into suggested patches, remediation explanations, or policies tailored to the detected application stack. Pull request review focuses on changed lines and supports severity-based blocking. For reporting, GuardVibe offers compliance-control mappings, SARIF output, scan baselines, and locally stored progress statistics. Its agent-focused checks inspect MCP settings, hooks, permissions, and environment-related risks; host-level inspection can also include shell profiles and global AI configurations. A shell-command assessment returns an allow, ask, or deny verdict with risk context and alternatives, giving coding agents a separate check before execution.
guardvibe setup notes
- guardvibe records stdio only; confirm a network transport upstream before planning remote access.
- guardvibe has no recorded license; confirm reuse terms in its repository.