← Back to Docs
FAQ

Frequently asked questions

Short answers to the questions people ask first. The rest of the docs carries the detail behind each one.

What is VibeCop?

VibeCop is Maiife's Architecture Integrity & Product Intelligence platform. It scores repositories with a 0–100 Architecture Integrity Index and flags architectural entropy in AI-generated code — hallucinated abstractions, duplicated logic, and pattern drift — before it merges.

What is the Architecture Integrity Index?

The Architecture Integrity Index is a 0–100 score of your codebase's structural health. It is the sum of four 25-point axis scores — Consistency, Reuse, Simplicity, and Structure — each reduced by the severity-weighted findings on that axis.

What does VibeCop detect?

VibeCop runs nine architectural detector agents across four axes — hallucinated abstractions, semantic duplication, over-engineering, pattern drift, reinvented utilities, architectural complexity, layer violations, orphaned modules, and reintroduced bugs — plus nine static checks: eight hygiene layers tracked separately from the index (dependency CVEs, dependency health, secrets, SAST, infrastructure-as-code, vendored drift, magic numbers, migration safety) and an error-handling check that counts toward the Consistency axis.

Does VibeCop work with GitHub?

Yes. VibeCop connects directly to GitHub repositories and reviews pull requests. Webhook auto-reviews trigger a full analysis on every PR open and sync.

How much does VibeCop cost?

VibeCop is free for everyone until December 31, 2026 — no card required, and nothing is billing. Pricing has not been finalised and will be announced before any plan starts billing.

How is VibeCop different from a linter?

Linters check line-level style and syntax. VibeCop analyzes architecture-level entropy — whether new code drifts from your team's established patterns, duplicates existing logic semantically, or adds unjustified abstraction — using a full code graph of your repository.

What is the VibeCop Plan Review MCP?

A remote MCP server that reviews your AI agent's implementation plan against your codebase's conventions before any code is written. It works with Claude Code, Cursor, Codex, and any MCP-capable agent over streamable HTTP with a Bearer token minted in VibeCop Settings.

How do I connect Claude Code or Cursor to VibeCop?

Mint an MCP token in VibeCop Settings, then add the server: claude mcp add --transport http vibecop https://api.gradus.maiife.ai/mcp/vibecop --header "Authorization: Bearer <TOKEN>" — or add the equivalent mcpServers entry to your agent's MCP config. Setup guide at vibecop.maiife.ai/mcp.

Get startedWhy VibeCop