Vibecheck Mcp
Wire an AI code firewall into your MCP client so coding agents cannot silently invent libraries, endpoints, or APIs.
Overview
VibeCheck MCP is a MCP server for the Ship phase that acts as an AI code firewall to reduce hallucination-driven mistakes in agent-generated development work.
What is this MCP server?
- MCP stdio server (@vibecheckdev/vibecheck-mcp on npm) for Claude Code, Cursor, and other MCP hosts
- Positions itself as an AI Code Firewall focused on hallucination prevention in development workflows
- Fits pre-merge and in-session checks when agents propose code, imports, or external integrations
- stdio transport keeps setup limited to npm install plus MCP config—no separate HTTP service in the manifest
- Complements human review and static analysis rather than replacing your test suite
- [object Object]
What problem does it solve?
Coding agents often propose code that looks correct but references packages, APIs, or files that do not exist, and those mistakes are expensive once they are merged.
Who is it for?
Indie builders who merge substantial agent-written diffs and want an MCP-native hallucination guard without building custom validators.
Skip if: Teams that only use AI for prose or tickets, or shops that already enforce the same guarantees solely through CI with no agent integration need.
What do I get? / Deliverables
After you add the server to your MCP config, your agent can invoke firewall-oriented checks so risky or fabricated suggestions are challenged before they become commits.
- Registered stdio MCP server in your agent config
- On-demand firewall-style checks invokable from coding sessions
- Reduced risk of merging hallucination-based code paths
Recommended MCP Servers
Journey fit
How it compares
MCP security integration for model output, not a general-purpose linter skill or test runner.
Common Questions / FAQ
Who is VibeCheck MCP for?
It is for solo and small-team builders using MCP-enabled coding agents who want extra protection against hallucinated code and dependencies.
When should I use VibeCheck MCP?
Use it during active agent coding sessions and before you ship or merge changes that the model drafted or edited.
How do I add VibeCheck MCP to my agent?
Install @vibecheckdev/vibecheck-mcp from npm and register a stdio MCP server entry pointing at that package in Claude Code, Cursor, or your host’s MCP settings.