# Reported issues for Inspectrum

Pod holds 6 of 6 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [Inspectrum](/mcp/inspectrum).

## Most discussed

### Bug: invalid config crashes the MCP server with a raw ZodError; MCPB manifest pins an exact npm version

## Summary

In the Claude Desktop app, the Inspectrum MCP server fails to start and the app shows only two generic banners — `MCP Inspectrum: Server disconnected` and `Could not attach to MCP server Inspectrum`. The developer settings pane marks the server `failed` with `Erreur: Server disconnected` and no further detail.

The banners are a symptom, not the cause. The MCP host log shows the server process dying immediately on startup with an **unhandled `ZodError` from config parsing**. Nothing 

[Read the thread](https://github.com/yannmenec/inspectrum/issues/67) · 2026-08-03 · closed · 3 comments

### doctor: warn when an installed MCPB bundle is older than the running package

Split out of #67, where the reported "MCPB pins an exact npm version" defect turned out to
be stale (see #68 for the evidence: the packaging script has shipped a self-contained
bundle since #29, locked by `tests/contract/distribution.contract.test.ts`).

## The residual gap

An MCPB bundle that was already installed stays at its build-time version forever, with no
signal anywhere. That is how a 0.1.1 bundle survived until it crashed on a config that
0.2.3 accepts. Reinstalling is the only fix, a

[Read the thread](https://github.com/yannmenec/inspectrum/issues/69) · 2026-08-03 · open · 1 comment

### Story: Expose reviewed, partial, and unreviewed coverage with reviewer counts

Parent Feature: #61
Parent Outcome: #59

## User story

As a developer approving a risky agent plan, I want the result to state exactly how much requested review happened so that plan quality and reviewer availability cannot be confused.

## Acceptance criteria

- [ ] `src/schemas.ts` defines an additive status-discriminated output for `reviewed`, `partial`, and `unreviewed`.
- [ ] Output and session evidence record ordered requested, attempted, and succeeded reviewer counts.
- [ ] Reports rende

[Read the thread](https://github.com/yannmenec/inspectrum/issues/64) · 2026-08-02 · open · 0 comments

### Feature: Honest review coverage in every review_plan result

Parent Outcome: #59

## Expected result

Every `review_plan` response separates plan-content verdict from reviewer coverage. A reviewer failure is never hidden behind an unqualified `approve`.

## Scope

- Additive machine-readable `reviewed`, `partial`, and `unreviewed` coverage.
- Requested, attempted, and succeeded reviewer counts.
- Failure evidence persisted for partial and all-failed runs.
- Existing fail-open and human-approval guarantees preserved.

## Out of scope

Fallback routing, per

[Read the thread](https://github.com/yannmenec/inspectrum/issues/61) · 2026-08-02 · open · 0 comments

### Generate mcpb manifest version from package.json + release version-consistency test

From the Codex GPT-5.6 week review (findings DXR-3, TEST-3). 0.2.0 is aligned today across package.json / plugin.json / manifest.json / src/version.ts, so this bites the NEXT version bump, not this release.

- **DXR-3** (major) — `mcpb/manifest.json` still hardcodes both `"version": "0.2.0"` and the `inspectrum@0.2.0` npx arg. PR #20 only de-hardcoded the output *filename* (`build:mcpb` uses `$npm_package_version`). On the next bump, `build:mcpb` can produce `inspectrum-<new>.mcpb` whose manifes

[Read the thread](https://github.com/yannmenec/inspectrum/issues/23) · 2026-07-12 · closed · 0 comments

### Harden the plan-gate plugin shim (version drift, npx-failure fail-open)

From the Codex GPT-5.6 week review (findings SEC-6, DXR-1, DXR-2). Deferred from the pre-0.2.0 hardening PR because the shim is shipped in the plugin and pinning needs 0.2.0 on npm first.

\`scripts/plan-gate-shim.sh\`:
- **DXR-1** (major): the shim prefers ANY global \`inspectrum\` binary (`command -v inspectrum` → `exec inspectrum plan-gate`). A user with a stale global 0.1.5 gets a binary with no `plan-gate` subcommand. Version-check the global (`inspectrum --version`) before using it, or dro

[Read the thread](https://github.com/yannmenec/inspectrum/issues/21) · 2026-07-12 · closed · 0 comments

## Most recent

The remaining reports are on [the project's issue tracker](https://github.com/yannmenec/inspectrum/issues).