MCP App Store
by KeenEthics
Veridu icon

Veridu MCP Server for Claude and ChatGPT

By T3 Interactive LLC

Overview

Veridu reviews the change you or your agent just made. Ask Claude to verify a change with Veridu: it sends the diff and the files it changed, two reviewers from different vendors check them, findings that cannot be grounded in the code are dropped, and Claude gets back an outcome (pass, review or block) and concrete findings with file, line, severity and evidence. Only problems both reviewers confirm can block. Claude can fix the findings that hold up and check again; each finding keeps the same id across follow-ups, so you can see what was fixed, what persists and what a fix introduced. Veridu reviews only what is sent; it does not read the rest of your repository, so a pass means "nothing found in what was sent", not "safe to merge". For PHP it also traces callers and subclass overrides within the files sent. You can also review a GitHub pull request by URL. Public repositories work right away; private ones once linked through the Veridu GitHub App. Free accounts include 20 reviews a month. Sign-in is in the browser (GitHub, Google or an emailed code); no API keys.

How to connect

  1. Claude: Open the Veridu listing in the Claude connectors directory and choose Connect. Claude listing Veridu exposes 4 tools here.
  2. ChatGPT: Open the Veridu listing in the ChatGPT app directory and choose Connect. ChatGPT listing Veridu exposes 4 tools here.

Tools

get_change

ChatGPT
Fetch the result of a verify_change that was still running. Never starts a new review; wait ~20 seconds between calls.

veridu_review

ChatGPT
Review a GitHub pull request with Veridu: code review that knows what depends on the change. Veridu finds the callers, implementations and references the PR affects, independent reviewers check it in that context, ungrounded findings are dropped, and only problems both reviewers confirm can block. Returns the outcome, agreements, disputes and per-reviewer findings. Requires a Veridu account. Each new review counts as one review on that account; asking again for the same pull request head returns the existing review. Notes: - Private repos: link the repo at https://veridu.io/repos first (GitHub App or fine-grained PAT). No credentials are passed through this tool. - The models array selects the reviewer panel for this call. Panel must include at least two distinct vendors; tier-gated models require a paid account. If more than one model per vendor is passed the first per vendor wins. Omit models to use the account default panel.

veridu_review_status

ChatGPT
Check a Veridu review that was still running when veridu_review returned, and fetch the result once it finishes. This never starts a review and never counts as one. Safe to call repeatedly — but wait roughly 30 seconds between calls; a large diff can take several minutes. If a review is still running, DO NOT call veridu_review again for the same pull request. That starts a second review and consumes another attempt. Use this tool with the review_id you were given.

verify_change

ChatGPT
Have Veridu review a code change you just made, before you commit or open a pull request. Independent reviewers check the change against the files you send (for PHP, Veridu also traces callers and overrides within them), findings that cannot be grounded in the code are dropped, and only problems both reviewers confirm can block. You get an outcome (pass / review / block) and concrete findings with file, line, severity and evidence. Send: diff = git diff --no-renames <base> of your change (include new files: git add -N first), and files = the FULL current content of every file the diff adds or modifies, keyed by repo-relative path. You may add up to a few closely related unchanged files (callers, interfaces) to files for context. Text files only; no renames, mode changes, symlinks, submodules or binaries. Limits: diff 256 KB / 60 files, files 512 KB total. After fixing findings, call again with the new diff and parent_change = the previous change_id: up to two follow-ups per change do not count as a new review. Sending exactly the same change again returns the earlier result. Every finding has a finding_id that stays the same across follow-ups while the problem persists. A follow-up also returns followup: which ids persist, which are new (possibly introduced by your fix), and which are no longer reported, with code_changed saying whether the flagged line changed. "No longer reported" is not proof of a fix. Low-severity findings can be left out of the list but are still counted in followup. An identical resend returns the earlier result as it was. Each other new change counts as one review on the signed-in Veridu account. Results are advisory: Veridu sees only what you send, not the rest of the repository. If the review is still running after ~45 seconds you get a change_id: call get_change with it (do not call verify_change again for the same change).

get_change

Claude

veridu_review

Claude

veridu_review_status

Claude

verify_change

Claude

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/veridu"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/veridu)