Verificate MCP server
{
"mcpServers": {
"verificate": {
"type": "http",
"url": "https://mcp.verificate.ai/mcp"
}
}
}{
"mcpServers": {
"verificate": {
"type": "http",
"url": "https://mcp.verificate.ai/mcp"
}
}
}{
"mcpServers": {
"verificate": {
"type": "http",
"url": "https://mcp.verificate.ai/mcp"
}
}
}{
"servers": {
"verificate": {
"type": "http",
"url": "https://mcp.verificate.ai/mcp"
}
}
}{
"mcpServers": {
"verificate": {
"type": "http",
"url": "https://mcp.verificate.ai/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.8.7
What it does
Verificate MCP runs code review on AI-generated code before it reaches your repository. It combines 17 deterministic reality gates (which can veto code automatically) with a frontier-model enterprise review that scores for performance, scalability, and reliability. It works in Claude Code, Cursor, Windsurf, and other MCP clients with no signup required for the first 25 validations.
- Catch AI-written code that invents SDK calls, creates N+1 loops, or uses floating-point math for financial values before merging.
- Review plans and design documents for feasibility and scalability issues before any code is written.
- Analyze existing codebases to understand hot paths, rate-limit implications, and hidden failure modes.
Tools this server exposes
| Tool | Does |
|---|---|
| validate_ai_output | Gate for AI-written code — runs deterministic reality checks first (mock detection, invented-API checks), then scores what survives against ISO/IEC 25010 criter |
| validate_plan | Gate for plans and designs before code exists — checks completeness, feasibility, and scalability implications, returning approve/reject verdict with findings. |
| analyze_code | Advisory review of existing code for hot paths, rate-limit math, failure modes, and tech debt — returns scores and findings without a verdict. |
| generate_code | Combines code generation with gating in one step — an LLM writes code and the same protection engine vets it before output. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.