Independently qualify candidate test cases and/or bug findings before you write your final artifact.

Send the candidate result you are holding in memory — do not write it to a file first, and do not call this after the report is published. codex-mcp runs Codex as a separate reviewer that inspects the repository itself, derives its own expected coverage or verdict, and only then compares that against your candidate. It returns a review delta.

What comes back is a second opinion, not a ruling. Verify each objection against the cited evidence: apply the ones the evidence supports, reject the ones it does not and record why, investigate the rest. You own the final artifact; codex-mcp never writes it.

The reviewer is strictly read-only: it cannot edit files, commit, push, modify issues, or write to any database or external system.

Required: reviewType, project.root, and a matching candidate set. Everything else — task context, blast-radius, test-charter, connectors — is optional and never blocks a review.

Report whether Codex is authenticated and which auth mode is in use.

Call this before a review if you want to fail fast with a clear message. Credentials are owned by the Codex CLI and the operating system; this never returns a token, API key, cookie, or any other secret.

Two auth modes are supported: chatgpt (browser sign-in to a ChatGPT subscription) and api (an OpenAI API key). The response reports the active mode, the configured mode, and whether they agree — reviews fail while they disagree.

If it reports authenticated: false, the user must run codex-mcp login in a terminal. That flow is interactive and cannot be triggered from here.

Report what evidence this codex-mcp instance can actually reach, and what it is forbidden to do.

Diagnostic only — it runs no review and changes nothing. Use it to find out, before you rely on it, whether the requirement system or database is available for independent verification, and which downstream tools were withheld by policy.

Probing connectors takes a moment; pass probeConnectors: false for a configuration-only answer.