Your agent wrote the change. Veridu checks what it affects.
Your coding agent sends its change to Veridu before the pull request. Veridu checks it against the code that depends on it.
Your agent has Veridu check its work.
Add Veridu to your coding agent once. When it finishes a change, it asks Veridu to verify it, gets back grounded findings to fix, and checks again. Veridu links the follow-up to the earlier check and reports what is still there, what is new and what is gone.
No repository to connect: only the files your agent sends are read, in an isolated sandbox (for PHP, Veridu also traces callers and overrides within them). Veridu's reviewers run on Veridu's own model access, not your Claude or Codex plan. How it works
claude mcp add --transport http veridu https://api.veridu.io/mcp
codex mcp add veridu --url https://api.veridu.io/mcp && codex mcp login veridu
Cursor / Windsurf: add https://api.veridu.io/mcp as an MCP server.
Then Veridu checks what the change touches.
With the GitHub App, a pull request is reviewed when it is opened or marked ready for review (bot pull requests are skipped, and drafts too unless Review before a human is on; comment /veridu review to request one). In PHP, the review traces who calls what changed, what implements or overrides it, and where removed code is still referenced; TypeScript, JavaScript and Python get lighter checks on changed definitions. The review shows the code outside the diff it checked, so you can see what was looked at.
Results land as a GitHub check and a comment. Choose the severity that fails the check; the PR's own description is checked as a claim against the diff, not taken on trust.
No findings. Nothing in the change or the code it affects needs attention.
Findings worth a look - style, minor risk, or single-reviewer noise.
High-confidence defect, confirmed independently.
Change-impact evidence surfaced - callers, implementers, references to removed symbols the reviewer needs to see.
How change impact analysis works →- 01Your agent makes a change and asks Veridu to verify it.From Claude Code, Codex, Cursor or any MCP client, before anything is committed.
- 02It fixes what was found and checks again.Each finding keeps its id across checks, so the agent and you can see what was fixed, what persists and what the fix introduced.
- 03The pull request is checked against the code that depends on it.Callers, implementations and leftover references to removed code (traced for PHP), with only confirmed problems failing the Veridu check. Also works on any public pull request without installing anything.