状态检查
STDIOAI编程安全网与高级工程师指导系统
AI编程安全网与高级工程师指导系统
Your AI coding safety net with senior engineer collaborative reasoning - because getting 90% done and then stuck for weeks sucks.
Vibe Check MCP v0.5.1 stops you from building yourself into a corner with AI-generated code. It's like having a team of senior engineers watching over your shoulder, ready to interrupt bad decisions in real-time and catch expensive mistakes before you waste days on unfixable problems.
The game-changing feature that actually prevents disasters before they happen:
❌ You: "I'll build a custom HTTP client for this API" ✅ Mentor: "Have you checked if an official SDK exists?" (INTERRUPT!)
This literally stops you when you're about to make expensive mistakes. It's like having a senior engineer tap you on the shoulder and say "Hey, wait a minute..."
Get feedback from multiple engineering perspectives simultaneously:
Built for Claude Code MCP Integration - Seamlessly integrates with your existing Claude Code workflow for real-time engineering coaching.
Ever spend weeks building something, only to discover there was a simple API call for that?
You're not alone. Vibe Check is specifically designed for vibe coders - people who love AI coding tools but need a sanity check to avoid the overengineering traps that AI often creates.
🔥 "I spent $417 using Claude to build a word game, only to discover my AI-generated code had no server-side validation - it got DDOS'd with the entire Bee Movie script"
🔥 "LLM coded an entire iOS app database in a CSV file instead of Core Data - I had no idea!"
🔥 "Just plug the error back into ChatGPT until the code it generates oscillates between two error states forever"
🔥 "People are already losing touch with what the code they are writing is actually doing. AI can help get code out the door faster, but when it breaks it can be a lot harder to debug and fix"
Vibe Check MCP is your AI coding safety net - keeping the fun of vibe coding while avoiding the expensive traps.
Vibe Check MCP provides three modes of analysis to catch engineering anti-patterns before they become expensive mistakes:
| Anti-Pattern | What It Catches | Real Impact | 
|---|---|---|
| 🏗️ Infrastructure-Without-Implementation | Building custom solutions before testing standard APIs | Days/weeks wasted (Cognee case study) | 
| 🩹 Symptom-Driven Development | Treating symptoms instead of addressing root causes | 3.2x longer project completion time | 
| 🌀 Complexity Escalation | Adding unnecessary complexity without justification | 89% increase in maintenance costs | 
| 📚 Documentation Neglect | Building before researching standard approaches | 2.8x higher failure rate | 
Validated Results: 87.5% detection accuracy, 0% false positives, sub-millisecond component latencies in comprehensive testing.
Revolutionary dynamic response generation that sets Vibe Check apart from all competitors:
# High confidence queries → Static response (50ms) "Use official Stripe SDK instead of custom HTTP client" # Low confidence queries → Dynamic MCP sampling (2000ms) "Analyze this complex microservice architecture for anti-patterns" # Hybrid approach for balanced speed/flexibility (500ms) "Review this FastAPI + Supabase integration approach"
This native MCP integration eliminates the need for external API management while providing enterprise-grade performance and security.
Say goodbye to generic advice! Vibe Check now understands your specific technology stack and provides library-specific recommendations.
User: "Should I build a custom authentication system?"
Vibe Check: "Generally, avoid custom auth. Use established libraries."
User: "Should I build a custom authentication system?"
Vibe Check: "I see you're using FastAPI + Supabase. Supabase has built-in auth with 
JWT tokens and Row Level Security. Use the @supabase/auth-js client for 
frontend auth state management. This eliminates the need for custom auth entirely."
🔍 Library Detection Engine
📖 Project Documentation Parser
🧠 Context-Aware Analysis
detect_project_libraries - Scan your codebase for tech stackload_project_context - Get comprehensive project analysiscreate_vibe_check_directory_structure - Setup .vibe-check/ config📖 Full Contextual Documentation Guide →
Production-ready security without compromising performance:
Perfect for teams that need AI assistance without compromising security posture.
Choose the installation method that works best for your setup:
# Run directly without installation npx vibe-check-mcp --stdio # Add to Claude Code MCP config with GitHub token (for private repos) claude mcp add vibe-check-npm -e GITHUB_TOKEN="your_github_token_here" -- npx vibe-check-mcp --stdio # Or without GitHub token (public repos only) claude mcp add vibe-check-npm -- npx vibe-check-mcp --stdio
Benefits:
npx -y @smithery/cli install vibe-check-mcp --client claude
Benefits:
Perfect for contributing to the project or customizing the server:
# 1. Clone and install dependencies git clone https://github.com/kesslerio/vibe-check-mcp.git cd vibe-check-mcp pip install -r requirements.txt # 2. Test server locally PYTHONPATH=src python -m vibe_check.server --help # 3. Add local development server to Claude Code (with GitHub token) claude mcp add vibe-check-local -e PYTHONPATH="$(pwd)/src" -e GITHUB_TOKEN="your_github_token_here" -- python -m vibe_check.server --stdio # Or without GitHub token (public repos only) claude mcp add vibe-check-local -e PYTHONPATH="$(pwd)/src" -- python -m vibe_check.server --stdio # 4. Restart Claude Code
When to use local development:
# 1. Clone and install git clone https://github.com/kesslerio/vibe-check-mcp.git cd vibe-check-mcp pip install -r requirements.txt # 2. Add to Claude Code with GitHub token claude mcp add vibe-check -e PYTHONPATH="$(pwd)/src" -e GITHUB_TOKEN="your_github_token_here" -- python -m vibe_check.server --stdio # Or without GitHub token (public repos only) claude mcp add vibe-check -e PYTHONPATH="$(pwd)/src" -- python -m vibe_check.server --stdio # 3. Restart Claude Code and start using! 💡 **Tip**: Add `-s project` to share with your team via .mcp.json, or `-s user` to use across all your projects.
curl -fsSL https://raw.githubusercontent.com/kesslerio/vibe-check-mcp/main/install.sh | bash
What it does:
Required for: Private repositories, organization repos, increased rate limits
When you need it:
How to get a GitHub token:
repo (for private repository access)read:org (for organization repositories)ghp_)How to use the token:
# Option A: Set as environment variable (recommended) export GITHUB_TOKEN="ghp_your_token_here" # Add to ~/.zshrc or ~/.bashrc for persistence # Option B: Pass directly in MCP config (see installation options above)
Security Note: Keep your token secure! Don't commit it to version control.
Control which tools are exposed based on your usage needs:
Production Mode (Default) - 30 tools:
# No environment variables needed - this is the default # Includes all core anti-pattern detection and analysis tools
Diagnostics Mode - +11 diagnostic tools:
export VIBE_CHECK_DIAGNOSTICS=true # Enables: # - Claude CLI diagnostics (2 tools: status, diagnostics) # - Configuration validation (2 tools: validate_mcp, check_integration) # - Async LLM monitoring (7 tools: async analysis, health, metrics, status)
Development Mode - +2 dev/experimental tools:
export VIBE_CHECK_DEV_MODE=true # Enables: # - demo_large_prompt_handling (experimental features) # - reset_session_tracking (dev utility)
Comprehensive Test Mode:
export VIBE_CHECK_DEV_MODE_OVERRIDE=true # Enables all dev tools + comprehensive test suite # For contributors and advanced debugging
Benefits of Environment-Based Gating:
Since our project is specifically designed for Claude Code integration, here's the fastest setup:
# With GitHub token (for private repositories) claude mcp add vibe-check -e GITHUB_TOKEN="your_github_token_here" -- npx vibe-check-mcp --stdio # Or without GitHub token (public repositories only) claude mcp add vibe-check -- npx vibe-check-mcp --stdio
# Restart Claude Code to load the new MCP server # No installation, dependencies, or local setup required!
# Test that the MCP server is working claude "Show vibe check server status" # Test a quick analysis claude "Quick vibe check: analyze this text for any engineering anti-patterns"
# Check Claude Code version and MCP integration claude --version # Test the mentor feature (Enhanced in v0.5.1 with MCP sampling) claude "Should I build a custom HTTP client for the Stripe API?" # Test fast pattern detection claude "Quick vibe check issue 42"
GitHub Token Permissions (for GitHub integration):
repo (for private repository access)read:org (for organization repositories)Troubleshooting:
repo scope# Get architectural guidance "Should I build a custom auth system for this project?" → 🤝 Multi-persona feedback from Senior Engineer, Security Expert, Product Manager # Interrupt mode for real-time prevention "I'm planning to build a custom HTTP client for the Stripe API" → 🚨 INTERRUPT: "Have you checked if stripe-python SDK exists?" # Claude model selection for different analysis depths "Use Haiku to quickly validate this API design" "Use Opus for deep architectural review of this microservice"
# Quick pattern detection (fast) "Quick vibe check issue 42" "Fast analysis of this PR" "Basic check on this technical document" # Deep analysis with educational coaching "Deep vibe check issue 42 with full Claude analysis" "Comprehensive review of this integration plan" "Analyze this code for over-engineering patterns"
# Before building integrations "Validate building custom HTTP client for Stripe API" → ⚠️ Risk detected: Use stripe-python SDK instead # During code review "Review this PR for complexity anti-patterns" → 🎓 Educational: Why this abstraction adds unnecessary complexity # Planning phase analysis "Analyze issue 23 for infrastructure anti-patterns" → 🛡️ Prevention: Research official SDK before building custom solution
Unlike code analysis tools that just flag issues, Vibe Check explains:
Core Analysis Tools:
| Tool | Purpose | Mode | Response Time | 
|---|---|---|---|
vibe_check_mentor | Senior engineer collaborative reasoning with MCP sampling | Mentor | <30s | 
analyze_github_issue | Issue analysis for planning anti-patterns | Fast/Deep | <10s / <60s | 
analyze_pull_request | PR review with anti-pattern detection | Fast/Deep | <15s / <90s | 
analyze_text | Text analysis for documents/plans | Fast/Deep | <5s / <30s | 
analyze_code | Code analysis with educational coaching | Deep | <30s | 
validate_integration | Integration approach validation | Fast | <10s | 
Security & Configuration Tools:
45+ total tools including contextual documentation, doom loop detection, productivity interventions, and comprehensive debugging capabilities.
See MCP Deployment Guide for complete setup instructions.
We welcome contributions! Vibe Check MCP is built by the community for the community.
High-Priority Contributions:
See CONTRIBUTING.md for detailed guidelines.
Apache 2.0 License - see LICENSE for details.
Built with FastMCP and designed for seamless Claude Code integration.
Ready to prevent your next engineering failure?
Install Vibe Check MCP v0.5.1 and get your context-aware senior engineer mentor that actually prevents disasters before they happen.
🚀 Get v0.5.1 Now | 📖 Release Notes | 🧠 Try the MCP Sampling Integration
The only AI coding assistant with native MCP sampling integration:
| Feature | Vibe Check MCP v0.5.1 | Competitors | 
|---|---|---|
| MCP Protocol Native | ✅ Built-in, no API keys | ❌ Requires external APIs | 
| Performance | ✅ <0.1ms static, <3s dynamic | ❌ Unoptimized latencies | 
| Tool Count | ✅ 45+ specialized tools | ❌ 5-15 generic tools | 
| Offline Operation | ✅ Complete local operation | ❌ Requires internet connectivity | 
| Security by Design | ✅ 12 built-in protections | ❌ Minimal security features | 
| Real-time Interrupts | ✅ Prevents bad decisions | ❌ Post-hoc analysis only | 
| Collaborative Reasoning | ✅ Multi-persona analysis | ❌ Single perspective | 
Native MCP integration gives you enterprise-grade AI assistance without the enterprise-grade complexity.
Stop building the wrong thing. Start building the right thing faster.
Vibe Check MCP includes comprehensive test coverage including E2E tests for MCP integration.
Python Tests:
pip install -r requirements.txt
Node E2E Tests:
npm install # Installs mcp-test-client and dependencies
Python Unit Tests:
# Run all tests pytest # Run with coverage pytest --cov=src --cov-report=html # Run specific test file pytest tests/unit/test_response_relevance_validator.py -v
Node E2E Tests:
# Run individual E2E tests node tests/e2e/mcp/mentor_basic.mjs # Basic mentor functionality node tests/e2e/mcp/mentor_interrupt_mode.mjs # Interrupt mode validation node tests/e2e/mcp/mentor_relevance.mjs # Response relevance guard # Run via pytest wrapper (skips if mcp-test-client not installed) pytest tests/e2e/test_mentor_relevance_e2e.py -v
pip install -e . required| Test Type | Location | Purpose | 
|---|---|---|
| Unit Tests | tests/unit/ | Core logic validation | 
| E2E Tests | tests/e2e/mcp/*.mjs | MCP integration verification | 
| Pytest Wrappers | tests/e2e/test_*.py | Python test runner integration | 
Problem: Server fails with log_level validation error or Input should be 'DEBUG', 'INFO', 'WARNING', 'ERROR' or 'CRITICAL'
Cause: FastMCP uses case-sensitive environment variable validation. Lowercase values like LOG_LEVEL=error will fail.
Solution: Ensure LOG_LEVEL is uppercase in your .env files:
# ❌ This will fail LOG_LEVEL=error # ✅ This works LOG_LEVEL=ERROR
PYTHONPATH includes the vibe-check-mcp source directorypip install -r requirements.txtpython -m vibe_check.server --stdio directly