ai.verificate/mcp · v1.8.7 · developer-tools
Verificate MCP is healthy: it completed an MCP handshake in 2114 ms and exposes 5 tools.
Agentic code review, no signup to try: reality gates + frontier-model review, with veto.
Endpoint: https://mcp.verificate.ai/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 5 |
| Latency | 2114 ms |
| Last checked (UTC) | 2026-10-15T16:55:11.785Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-15T16:55:11.785Z | Healthy | 2114 | |
| 2026-10-14T16:25:43.155Z | Healthy | 2005 |
validate_artifact | Deterministic production-readiness gate for AI-built systems. Verifies the invariants that stop a system silently shipping broken: every critical component is PRESENT and LOADS, the import closure resolves (nothing assumed 'already on the box'), all runtime dependencies are declared, and health is a |
validate_ai_output | The merge gate for ANY AI-written output — code, documentation, reports, emails, configs: returns a binary approve/reject verdict with veto power — e.g. it rejects code calling the nonexistent stripe.Inventory API, an N+1 loop with the latency arithmetic to prove it, or a doc claiming success with n |
validate_plan | The gate for PLANS, designs and specs — run BEFORE any code is written, the cheapest place to catch a bad design. Returns the same binary verdict shape as validate_ai_output, with findings on completeness, feasibility, performance and scalability implications, security risks and missing consideratio |
analyze_code | Advisory deep-dive on existing code — scores and findings, deliberately NO pass/fail verdict, so it never blocks an agent. Surfaces performance hot paths, scalability cliffs, reliability gaps and tech debt with concrete latency/throughput arithmetic (e.g. 'O(n²) dedup: ~4s at 10k items'). Read-only: |
generate_code | Generate code and gate it in one step: an LLM writes the implementation, then the same protection engine as validate_ai_output vets it — retrying generation when the gate rejects. If every attempt is vetoed you still receive the last attempt, clearly marked validated:false with the gate findings — r |