Veridu

io.github.michaelw-prPublished by GitHub account michaelw-prv1.1.1Updated Oct 30, 2026

Your agent verifies its change before commit; PR review that knows what depends on your change.

VerifiedStreamable HTTPWeb executableDeveloper ToolsAI & ML

Overview

AI-generated overview

Veridu is a hosted MCP server that has an assistant send a code change's diff and files for independent review, returning a pass, review or block verdict with…

What you can do
  • Send a change's diff and changed files for review and get back an outcome plus findings with file, line, severity and evidence
  • Fetch the details of a previously submitted change
  • Request a review of an existing GitHub pull request
  • Check the status of a running review
  • Re-check the same change after fixes, with finding ids kept stable across follow-ups
When to use it
Useful when you want a second, independent check of an AI-made change before committing, or a review of a pull request, and want concrete findings rather than a general opinion.
Requirements
Remote hosted server at api.veridu.io over streamable HTTP; nothing runs locally. OAuth sign-in in the browser (GitHub, Google or an emailed code) is required; no API keys. A Veridu account is needed, and free accounts include 20 reviews a month.
Before you install
The diff and the full content of the files the assistant chooses to send are uploaded to Veridu; nothing else in the repository is read, so a pass only means nothing was found in what was sent. Reviewer prompts go to OpenAI and Anthropic, and the check runs in an AWS us-east-1 sandbox. Uploaded diffs and files are deleted 7 days after the check; the verdict and findings, which can quote code, are kept until account deletion. Reviews beyond the free allowance are paid.

Installation

In SourceWeft

  1. Open Veridu in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.michaelw-pr%2Fveridu/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "veridu": {
      "type": "http",
      "url": "https://api.veridu.io/mcp"
    }
  }
}

README

Veridu for Claude Code

Independent review of the change Claude just made, before you commit. Ask Claude to "verify this change with Veridu": it sends the diff and the files it changed to Veridu, 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. Claude fixes the findings that hold up and checks 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 pull-request review with repository context, use the GitHub App.

What the plugin contains

  • An MCP server entry for Veridu's hosted server at https://api.veridu.io/mcp (tools: verify_change, get_change, veridu_review, veridu_review_status).
  • A skill, verify-before-commit, that tells Claude how to build the payload, read the result, and run the fix-and-check loop.

Nothing runs on your machine: there are no hooks, scripts or packages.

Install

/plugin install veridu --marketplace michaelw-pr/veridu-plugin

Then run /mcp, choose veridu, and sign in in the browser (GitHub, Google or an emailed code). No API keys.

Cursor

The same plugin installs in Cursor (.cursor-plugin/plugin.json): the Veridu MCP server at https://api.veridu.io/mcp and the verify-before-commit skill. Sign-in is OAuth in the browser the first time the server is used; there is no token to paste.

VS Code (GitHub Copilot)

Veridu is a remote MCP server; nothing to install. Add it to .vscode/mcp.json in your project (or your user mcp.json):

json
{  "servers": {    "veridu": {      "type": "http",      "url": "https://api.veridu.io/mcp"    }  }}

Start the server from the file or the MCP servers list and sign in in the browser when asked (GitHub, Google or an emailed code). In Copilot agent mode, ask it to "verify this change with Veridu" before you commit: it calls verify_change with the diff and the changed files and gets back an outcome (pass, review or block) and findings with file, line, severity and evidence. To review an existing GitHub pull request, ask it to review the PR with Veridu (veridu_review).

Cost

Free accounts include 20 reviews a month. Each new change uses one; up to two follow-up checks of the same change are free, and resending an identical change returns the earlier result free. Plans: https://veridu.io/pricing

Privacy

When Claude calls verify_change, it sends to api.veridu.io the diff of the change and the full content of the files it chose to send. Nothing else from your machine or repository is read. The check runs in an isolated sandbox in AWS us-east-1, and the reviewer prompts go to OpenAI and Anthropic, neither of which uses API traffic for training under their published policies. The diff and files are deleted 7 days after the check finishes; the result (verdict and findings, which can quote lines of your code) is kept until you delete your account. Veridu stores only a hash of the sign-in token. Full policy: https://veridu.io/data. Questions or deletion requests: [email protected].

Support

[email protected] · https://veridu.io/docs

Veridu is operated by T3 Interactive LLC.

Source: README.md at commit 85664bc

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

4
  1. v1.1.1LatestOct 29, 2026
  2. v1.1.0Oct 15, 2026
  3. v1.0.0Oct 4, 2026
  4. v0.1.0Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts