Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Panel Review

by TruVerifAIversion 0.19.50i★ –iRuns in the cloud
Registry nameai.truverif/panel-review

Install

Overview

Description from the maker (original English)

Guardian agent for AI coding: four frontier models review risky diffs and commits before they ship.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Developer tools
  • You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • You fill in yourself: Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http panel-review https://mcp.truverif.ai/mcp --header 'Authorization: your-value'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "panel-review": {
      "url": "https://mcp.truverif.ai/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "panel-review": {
      "type": "http",
      "url": "https://mcp.truverif.ai/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • Authorization secret required HTTP header
    Bearer

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain truverif.ai (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Developer toolsi

  • More stars than 0% of the other 4907 servers in this category
  • Published to the registry more recently than 61% of the other 4907 servers in this category
  • Basic checks equal to or better than 100% of the other 4907 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Panel Review safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.19.50) reached the registry 25 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 4 days ago
Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 16 days ago
Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@truverifai/init

One command to connect your AI coding agents to TruVerifAI — multi-model review tools plus local pre-commit/pre-write review gates — on Claude Code, Codex CLI, Cursor (IDE + CLI), VS Code / GitHub Copilot, Gemini CLI, and Antigravity.

npx @truverifai/init          # plan -> one confirm -> browser login -> install gates + tools -> verify

npx @truverifai/init doctor # re-verify anytime: gates armed, tools connected, key valid npx @truverifai/init logout # remove the API key from every config this tool wrote

init shows a plan of everything it will write for your machine and asks once before touching anything. To scope or preview it:

npx @truverifai/init --dry-run              # print the plan, write nothing

npx @truverifai/init --only claude,codex # install for these agents only npx @truverifai/init --skip gemini,hook,rules # everything except these npx @truverifai/init --yes # non-interactive (CI): accept the plan npx @truverifai/init --version # print the version, do nothing else

Agent names: claude, codex, copilot, vscode, cursor, gemini, antigravity; hook is the git pre-commit gate and rules the agent-rules blocks. Declining the prompt exits with nothing written. A flag init does not recognize also exits with nothing written (it never falls through to an install).

MIT-licensed. Zero runtime dependencies — this package is plain, unminified JavaScript and Python; npm pack @truverifai/init and read every line. There is no build step and no transitive supply chain.

See it in action

Requirements

  • Node 18+ — runs this installer, and every hook command it writes launches a gate via node .py. No node, no gates, on any host.
  • Python 3 (python3, or py on Windows) — the gate code itself.

npx @truverifai/init doctor checks both and names the missing one, rather than letting an absent runtime disable the gates silently.

Turning the gates off (and back on)

The review gates block risky commits and edits. One command controls all of them:

npx @truverifai/init gates off       # stop every gate, everywhere

npx @truverifai/init gates on # turn them back on npx @truverifai/init gates status # what's on, and which setting decided it

(If you installed globally with npm i -g @truverifai/init, the same commands are available as the shorter tvai gates off. Plain npx does not leave a tvai binary on your PATH, so use the full form above unless you installed globally.)

This writes enable_gates to ~/.truverifai/config.json, which every delivery reads — the git pre-commit hook and the Codex, Cursor, Copilot, VS Code, Gemini and Antigravity hooks alike. The MCP review tools stay connected either way; only the automatic gating stops.

Two things worth knowing:

  • Claude Code no longer has its own toggle. enable_gates was removed from the plugin's settings panel (it could only ever reach Claude Code's own hooks — the X8 split), so this command is the single switch. One exception: a value stored in the panel *before* the removal may still be exported to Claude Code's hooks until you clear it; gates status calls that out and says how.
  • `TVAI_ENABLE_GATES` overrides everything. If you have it exported, gates on|off writes the file underneath it and has no effect until you unset it. gates status says so.

To remove the gates entirely rather than switch them off, see Removing it below.

What this installs, exactly

init runs as you, interactively: it prints the plan first, writes only after you confirm, and prints every file it touches. The complete list:

Its own home — `~/.truverifai/`

  • config.json — your tvai_… API key (minted via browser device-flow login; this process never sees a password).
  • gates/current/ — the review-gate code (Python + a Node launcher), vendored from this package's vendor/ directory.
  • .nudge_state.json, gate_state/ — local rate-limit / state files.

Per detected agent (user-level; only for agents found on your machine)

  • Claude Code: the plugin's api_token option, and one permissions.allow entry (mcp__plugin_panel-review_truverifai) in ~/.claude/settings.json so Claude's auto-mode classifier permits the free gate-release calls. Additive merges only — the file is backed up first, never created, and never has anything removed.
  • Codex CLI: an MCP server block (between TRUVERIFAI markers) and [features] hooks = true in ~/.codex/config.toml; ~/.codex/hooks.json.
  • Cursor: ~/.cursor/hooks.json (gates) and ~/.cursor/mcp.json (tools).
  • Copilot CLI: ~/.copilot/mcp-config.json.
  • VS Code: your user mcp.json.
  • Gemini CLI: ~/.gemini/settings.json (tools entry).

Per repository (written in the repo you run `init` from, with a prompt)

  • .github/hooks/truverifai-gate.json + truverifai-vscode.json (Copilot CLI / VS Code gate hooks), .gemini/settings.json (Gemini hooks), .agents/hooks.json (Antigravity hooks).
  • Optional agent-rules blocks (marked TRUVERIFAI_RULES_START…END) in AGENTS.md / CLAUDE.md / GEMINI.md — you are asked first.
  • .git/hooks/pre-commit — the git gate, which catches commits made outside any agent (and is the one layer --no-verify makes an explicit, auditable act). Installed automatically when you run init inside a git repo. It is the only repo-scoped gate, so add it to other repos with cd && npx @truverifai/init hook. An existing pre-commit hook you wrote is never overwritten — init reports it and prints the line to add by hand.

logout strips the API key from every config listed above. Nothing is installed as a service, daemon, or startup item; the gates only run when your agent host invokes its hooks.

What leaves your machine

  • Login: a device-flow handshake with truverif.ai mints your API key in the browser.
  • Gate checks (on risky writes/commits): the gates POST to api.truverif.ai a hashed repo fingerprint (SHA-256 of your git remote URL or repo path — the raw path/URL never leaves the machine), content hashes of the changed hunks, and the local classifier's category labels and scores. Not your source code, and not your file paths (only coarse path-class tags like "test/docs").
  • Review tools (`audit_coding` etc.): send only what your agent explicitly passes when it invokes a review — that is the product: the diff/context you choose to submit is analyzed by multiple frontier models.
  • Update check: gate responses may include a "newer version available" note computed server-side against the public npm registry; the client sends only its own version string.
  • Diagnostics (TVAI_PAYLOAD_LOG) are local-only and opt-in — nothing is uploaded.

The gates fail open by design: if our server is unreachable or anything errors, your commit/write proceeds and a visible notice says the change was not gated. This tool never blocks your work on its own failure.

Verifying this package

The full source is public at github.com/TruVerifAI/init — every release is synced there. To verify a tarball by hand: npm pack @truverifai/init, extract, and diff against the repo — bin/tvai.js, lib/*.js, and vendor/gates/*.py are the entire runtime surface, dependency-free. The gate code (vendor/gates/) is also published at github.com/TruVerifAI/claude-plugins (plugins/panel-review/hooks/). Build provenance attestation (CI publish with cryptographic linkage to this repo) is the planned next step.

Removing it

npx @truverifai/init uninstall

A complete removal, in one command:

  • Every hook config `init` wrote (Codex, Cursor, Copilot, VS Code, Gemini, Antigravity, and the git pre-commit hook), the vendored gate code under ~/.truverifai/, and the MCP server entries. Hook files you share with other tools are edited, not deleted — only our own entries are taken out, matched by marker.
  • Your API key, revoked server-side. Before deleting the local key file, uninstall calls the API to revoke the key itself, so any leaked or synced copy of it is dead. If the server is unreachable it says so and continues (the local removal never blocks on the network).
  • The plugin token in Claude's credential store — on a Mac this is the Keychain entry's panel-review value, edited in place (the Keychain item itself is Claude's and is left alone).
  • The `.tvai-bak` backups init made of shared config files — deleted only after the live file is verified clean; if a live file still contains our entries, its backup is kept and named as the restore source.

Uninstall is honest about failure: anything it could not remove is listed at the end under "needs your attention", and the command exits nonzero when secret-bearing residue remains (CI scripts that assumed exit 0 should check this). Silence means clean.

Uninstall also tries the host CLIs to remove the plugins init installed (claude plugin uninstall panel-review@truverifai, codex plugin remove panel-review@truverifai), best-effort: each attempt prints what happened, a failure never blocks the rest of the uninstall, and where no runnable CLI exists (the Claude desktop app) it prints the in-app step instead (+ button, then Plugins).

npx @truverifai/init logout is the lighter option: it clears the key (and our backups of files that held it) and the MCP entries but leaves the hooks installed. They then fail open for want of a key, and a later npx @truverifai/init login re-arms them.

Support

  • Setup page: https://truverif.ai/settings/mcp
  • Issues / questions: support@truverif.ai
Ask PopNx