Vibe Check MCP Server

If you want an AI assistant working directly with Vibe Check, the vibe check mcp server is the bridge. Metacognitive AI agent oversight: adaptive CPI interrupts for alignment, reflection and safety.

What Vibe Check does

KISS overzealous agents goodbye. Plug & play agent oversight tool.

Vibe Check MCP keeps agents on the minimal viable path and escalates complexity only when evidence demands it. Vibe Check MCP is a lightweight server implementing Anthropic's Model Context Protocol. It acts as an AI meta-mentor for your agents, interrupting pattern inertia with Chain-Pattern Interrupts (CPI) to prevent Reasoning Lock-In (RLI). Think of it as a rubber-duck debugger for LLMs – a quick sanity check before your agent goes down the wrong path.

Tools it exposes

Once connected, the assistant can call these 14 tools directly:

• Security — ** npm audit is clean — 10 advisories resolved across axios, the MCP SDK's Hono stack, form-data, fast-uri, postcss and the test toolchain
• Dependencies — ** MCP SDK 1.29, axios 1.18, OpenAI SDK 6.x, vitest 4.x; the unused body-parser direct dependency was dropped
• Feature — Description
• Provider — Default model
• gemini — gemini-3.6-flash
• anthropic — claude-sonnet-5
• openai — gpt-5.6-terra
• openrouter — (none — required)
• Variable — Default
• CORS_ORIGIN — loopback origins only
• MCP_ALLOWED_HOSTS — localhost, 127.0.0.1, ::1
• MCP_MAX_BODY_SIZE — 100kb
• Recognition — The Recognition tool exposed by this server
• Configuration — See docs/TESTING.md for instructions on how to run tests

Installing the vibe check mcp server

The server is distributed via npm as @pv-bhat/vibe-check-mcp, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 6 environment variables: GEMINI_API_KEY, OPENAI_API_KEY, OPENROUTER_API_KEY, ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN, ANTHROPIC_BASE_URL. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Vibe Check sits in that group, and the shape of its toolset — Security, Dependencies, Feature among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This is a hosted server — you point your client at an endpoint rather than running a local process, so there is nothing to keep updated on your machine.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 14 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Vibe Check.
• Maintained by PV-Bhat.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the vibe check mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.