Verificate MCP

{
  "id": "aix_eab3976cef",
  "name": "Verificate MCP",
  "operator": "(unclaimed - source: registry-official · publisher: ai.verificate)",
  "description": "Agentic code review, no signup to try: reality gates + frontier-model review, with veto.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-09-24",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "calendar-sync",
    "inventory-check"
  ],
  "protocols": {
    "mcp": "https://mcp.verificate.ai/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 8742,
    "uptime_30d": 0.9725274725274725,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 19,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-09-24T22:01:03.220Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "homepage",
      "url": "https://verificate.ai/mcp"
    },
    {
      "label": "repository",
      "url": "https://github.com/Verificate-Dev/verificate-mcp-quickstart"
    }
  ],
  "avatar": "https://github.com/Verificate-Dev.png?size=160",
  "socials": [
    {
      "label": "github",
      "url": "https://github.com/Verificate-Dev"
    }
  ],
  "profile": {
    "mcp_server": "verificate-mcp-http",
    "mcp_version": "1.2.0",
    "tool_count": 5,
    "tools": [
      {
        "name": "validate_artifact",
        "description": "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 REAL fail-closed check. Returns approve/reject with a fix plan and ISO 27001 / ISO 5055 control evidence. Facts are gathered by the Verificate collector in your CI; the gate is the authority. Non-bypassable, fails closed. This is the control-plane sibling of validate_ai_output — code quality is one"
      },
      {
        "name": "validate_ai_output",
        "description": "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 no evidence. Deterministic reality gates (mock/placeholder veto, gaming and bypass detection, invented-API checks) run first and cannot be overridden; a frontier-model review (ISO/IEC 25010) then scores quality, accuracy, reliability and tech debt. In a benchmark, a frontier model reviewing alone cau"
      },
      {
        "name": "validate_plan",
        "description": "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 considerations (e.g. it rejects a plan that polls an API every 100ms per client, with the request-volume math). Read-only: nothing is executed or stored beyond the verdict. Use validate_ai_output for the code that follows."
      },
      {
        "name": "analyze_code",
        "description": "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: the code is analyzed, never executed. Use it to understand a validate_ai_output rejection or review inherited code; use validate_ai_output when you need an accept/reject decision."
      },
      {
        "name": "generate_code",
        "description": "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 — rejected code is never presented as clean. Generation runs on our infrastructure; nothing executes in your environment."
      }
    ],
    "profiled_at": "2026-09-24T22:01:03.220Z"
  },
  "unreachable": false
}