Inspectrum

Name: Inspectrum
Author: yannmenec

by yannmenecversion 0.2.3i★ –iRuns on your computer

Registry nameio.github.yannmenec/inspectrum

Install

Overview

Description from the maker (original English)

Review coding-agent plans on demand with peer models, attributed findings, and a structured verdict.

PopNx MCP’s three pillars

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

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

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 on your computer
Transport: stdio
Category: Other

Install

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

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

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

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "inspectrum": {
      "command": "npx",
      "args": [
        "-y",
        "inspectrum"
      ]
    }
  }
}

Run this in your terminal

claude mcp add inspectrum -- npx -y inspectrum

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "inspectrum": {
      "command": "npx",
      "args": [
        "-y",
        "inspectrum"
      ]
    }
  }
}

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": {
    "inspectrum": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "inspectrum"
      ]
    }
  }
}

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 one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

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

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

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

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 with the GitHub account yannmenec, which owns the repo
… 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 applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32620 servers in this category
Published to the registry more recently than 21% of the other 32620 servers in this category
Basic checks equal to or better than 100% of the other 32620 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 Inspectrum 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?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.3) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Intervals 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

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Intervals MCP

by ljcl

Remote MCP server for intervals.icu run data and analysis

Runs on your computerUpdated today

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.

Inspectrum

Independent review before a risky agent change becomes hard to undo.

Claude plans it. GPT reviews it. You approve it.

A plausible plan can commit an agent to a migration, authentication change, payment flow, compatibility break, or deployment that is expensive to undo.

Inspectrum is an independent pre-flight check before that decision. Its first automatic integration runs when Claude Code exits plan mode: Codex (GPT) reviews the plan before the approval dialog reaches you, findings can send the plan back for revision, and you keep final approval. If the reviewer cannot run, the plan passes through with a visible warning instead of being silently reported as reviewed.

Here, independent means a reviewer distinct from the author model, invoked separately. It does not mean their errors are statistically independent. Inspectrum makes the checkpoint repeatable and its failures visible; a net reliability gain and a defensible moat are not yet proven. The post-0.2.2 strategy defines the evidence gates and keeps code review, pull-request review, and pair programming out of scope.

When a skill is enough

For an occasional second opinion, a rule can tell one agent to call another and compare the replies. That is a reasonable lightweight option.

Inspectrum is for the repeatable checkpoint. In Claude Code, the plugin runs at the plan-to-execution boundary without relying on a remembered prompt, caps revision loops, and fails open on operational errors. Other local MCP hosts can call the same review_plan contract on demand. Both paths keep findings attributed, return a common verdict shape, preserve human control, and write local evidence for successful reviews.

Recreating those guarantees with a skill means maintaining the orchestration, output validation, health checks, failure policy, and session record yourself.

Public availability as of 1 August 2026: npm 0.2.3, the GitHub release, and the repository's Claude and Codex plugins are aligned on 0.2.3. Glama is public. The MCP Registry may still show 0.2.2; it was not republished in this pass. Inspectrum was not in the public Claude Community catalog, while PulseMCP blocked the one-time recheck with HTTP 403, so no current PulseMCP listing claim is made.

The public 0.2.3 activation evidence records exact commands, timings, one useful finding, one null result, one visible fail-open case, and the limits of the measurement.

Quick start

You need Node 20+, Claude Code, and Codex CLI >= 0.99.0 authenticated with a ChatGPT subscription (no API key):

claude plugin marketplace add yannmenec/inspectrum

claude plugin install inspectrum@inspectrum

That's the whole install. Next time you finish a plan in plan mode:

⏺ ExitPlanMode

⎿ inspectrum×codex: REVISE (round 1/2) # abridged — real output Majors: # adds a full-report path

[codex] Migration drops the unique index before backfilling — concurrent writes can insert duplicates. Fix: backfill first, drop the index last. Revise the plan to address these findings, then finish the plan again.

⏺ ExitPlanMode ⎿ inspectrum: codex approved the plan (session 2026-07-12…). ┌ Ready to code? ──────────────── │ Here is Claude's plan… ← your normal approval dialog

No prompt to remember, no button, zero tokens spent on triggering. The gate is a deterministic hook — it fires on every plan, whether your session runs Fable, Sonnet, or Haiku. Two commands give you the automatic gate; the on-demand /inspectrum:review command needs one extra line (registering the MCP server — shown in the assisted setup below).

Prefer the agent to install and check everything for you? Paste this into Claude Code.

Set up Inspectrum's Codex plan gate. Use normal approvals only — do not

switch to Bypass Permissions or Full Access.

Steps:

Run node --version. If < 20, stop and tell me to install Node 20+ from https://nodejs.org first.
Run codex --version. If it is missing or older than 0.99.0, run npm install -g @openai/codex@latest and verify again.
Run claude plugin marketplace add yannmenec/inspectrum, then claude plugin install inspectrum@inspectrum.
Run claude mcp add --transport stdio --scope user inspectrum -- npx -y inspectrum@latest (this powers the on-demand /inspectrum:review command).
Run npx -y inspectrum@latest doctor and show me the output, including the resolved codex model/effort lines.
Run codex login status.

If it prints "Logged in", tell me: "✅ Setup complete. Your next plan-mode plan gets a Codex review automatically." Done.
Otherwise (not logged in), pop open a Terminal window with codex already running by executing: osascript -e 'tell application "Terminal" to do script "codex"' Then tell me: "A Terminal window opened with codex running. Inside that window, click 'Sign in with ChatGPT', complete the login in my browser, then close the Terminal window. Inspectrum is then ready."

Do NOT use sudo, edit shell profiles, push git changes, read .env or credentials, or publish packages. Report back: Node version, codex install status, doctor verdict, and whether login was needed.

How it works

you ──▶ Claude Code ──▶ plan ready ──▶ ExitPlanMode

│ inspectrum plan-gate (hook) │ Codex reviews the plan (read-only sandbox, your ChatGPT sub) │ ┌─────────────────────┴──────────────────────┐ APPROVE ✅ REVISE / REJECT ❌ │ │ your approval dialog findings go back to Claude, appears as usual it revises, gate runs again (max 2 rounds)

Built to be boring and safe:

Fails open. Codex not installed, logged out, timed out, network down — the plan proceeds with a visible warning. Operational errors don't block your work; the gate degrades, it doesn't brick.
Never auto-approves. A green review still lands on *your* approval dialog. The gate can delay it (while Claude revises) but can never click it — you keep the final call.
No wasted reviews. Within a session, an unchanged plan is hash-cached and not re-reviewed; only real revisions spend a round.
Read-only reviewer. Codex runs in a pinned read-only sandbox (codex exec -s read-only --ephemeral), and sandbox-weakening flags in your config are stripped. The reviewer reads; it doesn't write.
Kill switch. [plan_gate] enabled = false in ~/.inspectrum/config.toml, or disable the plugin per project.

Why a separate reviewer?

Plans are leverage. A flaw caught before execution can be cheaper to fix than the same flaw found after a difficult-to-reverse change.
Separation makes the check inspectable. The author and reviewer run independently, and findings remain attributed.
Cross-provider value is a hypothesis. Claude and GPT can raise different objections, but Inspectrum has not yet proved that this produces a net reliability gain after false positives, triage, cost, and latency.
Use an existing subscription. No separate API bill when using your ChatGPT subscription; reviews consume your existing Codex subscription allowance. API-key backends are billed by their provider.

What's in the box


🚦 Plan gate	Every Claude Code plan reviewed by Codex before it reaches you — automatic, max 2 revision rounds
🔍 On-demand review	`/inspectrum:review` or "Review this plan with Inspectrum" from any MCP host
🧑⚖️ Multi-reviewer + judge	Run codex + gemini + claude in parallel; a judge consolidates into one verdict
📋 One verdict	`approve / revise / reject` + findings by severity, with reviewer attribution
🗂️ Session logs	Markdown record of every review — verdict, findings, revised plan — under `~/.inspectrum/sessions/` (0700 perms)
🩺 `inspectrum doctor`	One command to check your reviewer is installed, authenticated, and resolving the right model — fails loudly if Codex is logged out

Works with

Your agent	Your reviewer	Setup
Claude Code	Codex (GPT)	Plugin — 2 commands above
Codex app / CLI	Claude	`codex mcp add inspectrum -- npx -y inspectrum@latest` + config below
Claude Desktop (macOS)	Codex (GPT)	Download `inspectrum-0.2.3.mcpb`, open, confirm. The earlier v0.2.0 bundle was incomplete — use the v0.2.3 asset, not npm/stdio.
Cursor	Codex (GPT)

Codex app / CLI setup — use Claude as your reviewer

Paste this into the Codex app or CLI:

Set up Inspectrum so I can review my plans with Claude. Use normal

approvals only.

Steps:

Run node --version. If < 20, stop and tell me to install Node 20+ from https://nodejs.org first.
Run claude --version. If "command not found", run npm install -g @anthropic-ai/claude-code and verify again.
If ~/.inspectrum/config.toml does not exist, create it with:

[defaults] reviewers = ["claude"]

Run codex mcp add inspectrum -- npx -y inspectrum@latest
Run npx -y inspectrum@latest doctor and show me the output.
Pop open a Terminal window with claude already running so I can confirm or complete login, by executing: osascript -e 'tell application "Terminal" to do script "claude"' Then tell me:

"If claude shows its chat prompt, you're already logged in — close the Terminal window. Inspectrum is ready."
"If claude shows /login or opens a browser, complete the sign-in with your Claude account, then close the Terminal window. Inspectrum is then ready." (The ⚠ claude line in the doctor stays even after login because claude doesn't expose a status command we can detect — harmless.)

Do NOT use sudo, edit shell profiles, push git changes, read .env or credentials, or publish packages. Report back: Node version, claude install status, doctor verdict, and whether login was needed.

Needs a Claude Pro/Max subscription — no API key.

Tuning

Which model reviews, at which effort? On the Codex side, precedence is:

Setting	1st (wins)	2nd	3rd
model	`[reviewers.codex] model` in `~/.inspectrum/config.toml`	`model` in `~/.codex/config.toml`	codex built-in default

| reasoning effort | [reviewers.codex] effort | model_reasoning_effort

Only the beginning is shown; read the rest in the repo

Inspectrum

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Intervals MCP

README from the maker

Inspectrum

Independent review before a risky agent change becomes hard to undo.

When a skill is enough

Quick start

How it works

Why a separate reviewer?

What's in the box

Works with

Tuning