MCP.Market

Verificate MCP server

online · 100% uptime
by verificate.ai·ai.verificate/mcp·v1.8.7·1 stars
No reviews yet

Agentic code review, no signup to try: reality gates + frontier-model review, with veto.

B84/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B84/100

full report

Adoption
Growing

1 stars

Reviews

Write one

Nobody has reviewed Verificate MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Verificate MCP tools (5)

write = sends, deletes, buys or posts
  • analyze_codeFree

    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.

  • generate_codeFree

    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.

  • validate_ai_outputFree

    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 caught reward-gaming and hallucinated APIs 0/6 times in a natural review workflow; these gates catch them deterministically on every call. Read-only: nothing is executed. Call it on every AI-generated deliverable before accepting it; use validate_plan for plans, analyze_code for an advisory report without a verdict.

  • validate_artifactFree

    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 invariant; this gates the whole deployable.

  • validate_planFree

    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.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 2017ms17/20
  • Tool poisoning5 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 3 days ago15/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace8/10
Overall 84/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Verificate MCP compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
84/100
higher than 70% of 4,460 AI and agents servers
Tools
5
the typical AI and agents server has 6
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote AI and agents server answers 100%
Response time
379 ms
faster than 37% of 2,331 AI and agents servers
GitHub stars
1
more than 50% of 2,711 AI and agents servers

What its tools let an agent do: 4 read · 1 create

Install Verificate MCP in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp https://mcp.verificate.ai/mcp
Add to Cursor

What the publisher says

From the Verificate MCP repository's README, as published. We do not edit it. Read it on GitHub

Verificate MCP — your vibe-coded MVP, all the way to production

Real output from the live server: 12 lines of AI-written payment code — rejected, fixed, approved, in seconds.

You vibe-coded the demo. This ships it. Between a working demo and a launched product used to stand an experienced CTO and a senior dev team — the people who catch the mock refund path, the invented SDK call, the loop that dies at real traffic. Verificate MCP is that review team as an MCP server: 17 deterministic reality gates with veto power, fused with a frontier-model enterprise review (ISO/IEC 25010: performance, scalability, reliability), run on every AI-written change before it reaches your codebase. The AI writes; the gate holds the bar; you ship. Hosted, zero-install, binary verdict in seconds — in Claude Code, Cursor, Windsurf or any MCP client.

Not another linter wrapper. The code-quality shelf on every MCP directory is two things: scanners (ESLint, Semgrep and SonarQube bridges — deterministic rules, no judgment) and prompt relays that pipe your repo to your own LLM key (self-review with extra steps). Verificate is neither: the gates hold veto power that no model output can override.

Your coding assistant writes a mock and calls it done. It invents an SDK call that doesn't exist. It ships an N+1 loop that passes every test and dies under load. Verificate MCP runs the deep review pass on every AI output — deterministic reality gates first (any one can veto), then an enterprise-grade review scores what survives — before the code reaches your codebase.

A real rejection (verbatim)

12 plausible lines of AI-written payment code were sent through the production gateway. Verdict: REJECTED — score 30.8/100, vetoed by coderealitygate, with findings including:

"N+1 synchronous API calls … For 100 items, this results in 100 sequential HTTP roundtrips, taking ~10–20 seconds and blocking the event loop/worker thread … will trigger Stripe rate limiting (100 req/sec limit)."

"stripe.Inventory is not a valid Stripe SDK resource."

"Floating-point representation issues lead to rounding errors in financial transactions; Stripe API requires integer cents."

Each of those is an afternoon of production debugging, caught in seconds.

Measured — vs. asking the model to review its own code

A frontier model asked "is this OK to merge?" in a natural workflow missed reward-gaming (a test that only does assert True) and a hallucinated API (stripe.Refund.createpartial) in 0 of 6 runs each. Verificate's gate caught both 6 of 6 — deterministically, with 0 false positives** on clean code.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Verificate MCP: common questions

Is Verificate MCP server safe?
Mostly: it is graded B (84/100). Read the Verificate MCP safety report
How do I install Verificate MCP?
It runs remotely at mcp.verificate.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Verificate MCP need an API key?
Yes. The registry entry asks for Authorization.
Is Verificate MCP maintained?
The last commit was 44 days ago (2026-09-21). The latest release is v1.8.7.
Is Verificate MCP up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Verificate MCP?
Servers from other publishers that do the same job: OpenWorkProof MCP server, Decionis Commerce Gate MCP server and PDF MCP server.
How does Verificate MCP compare with other AI and agents MCP servers?
safety score 84/100 (higher than 70% of 4,460 AI and agents servers); tools 5 (the typical AI and agents server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Verificate MCP

Same job from other publishers: the closest match first, then the best rated.

  • OpenWorkProof
    Verifiable agent evidence; opt-in Codex guard and reference SOC alert review.
    A
  • Decionis Commerce Gate MCP
    Commerce preflights, D365 authorization; opt-in agent writes require authorized backend connectors.
    A
  • PDF
    Agentic RAG over one PDF or a whole folder: hybrid search, selective page reads, tables, OCR.
    A
  • Claude Prompts
    Reusable prompt templates, multi-step workflow chains, and quality gates for any MCP client.
    A
  • Maple
    Review comments pinned to a running frontend, read and resolved by your coding agent.
    B