Inspectrum
NPM · INSPECTRUM
Review coding-agent plans on demand with peer models, attributed findings, and a structured verdict.
Available components
Last scanned (1 day ago)
Scores higher than 92% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to yannmenec/inspectrum). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 94 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability35
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 144 tokens (~72/item across 2 items; 1 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 13 Oct 26 −3
- Stability: pass → 0.77 functional
- 12 Oct 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/inspectrum@0.2.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | yannmenec/inspectrum |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/yannmenec/inspectrum/.github/workflows/npm-stage.yml@refs/tags/v0.2.3 |
| Rekor log index | 2311459543 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:289e3a3c0cb8c574f0d84d2be5fc09deee0ffbaa47a986fc6a08411c6a12cd39cb6fa0a63ff0b30a946b635906d7a517e5c38edc119087df4eecb3c9c |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
review_plan Review Plan ~140
Review a development/architecture plan with peer LLMs and return a consolidated verdict (approve | revise | reject) with prioritized findings. Runs configured reviewer CLIs and writes a local session log to ~/.inspectrum/sessions/.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional codebase excerpts for context. Max 8 000 characters. |
| focus | string | – | Review focus area. |
| judge | boolean | – | Run judge agent to consolidate when >= 2 reviewers. |
| plan | string | yes | The plan to review, in Markdown. Max 16 000 characters. |
| reviewers | array | – | Reviewer IDs (from config). Defaults to config defaults.reviewers. |
| Name | Type | Req | Description |
|---|---|---|---|
| findings | array | yes | – |
| report_markdown | string | yes | – |
| revised_plan | string | – | – |
| session_id | string | yes | – |
| session_path | string | yes | – |
| verdict | string | yes | – |
No examples provided.
How do I install the Inspectrum MCP server?
Inspectrum runs locally as an npm package, launched with npx -y inspectrum. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · inspectrum
claude mcp add yannmenec-inspectrum -- npx -y inspectrum
What is the Inspectrum MCP server?
Inspectrum is an MCP server listed in the public MCP registry as io.github.yannmenec/inspectrum. Review coding-agent plans on demand with peer models, attributed findings, and a structured verdict. This page covers its npm package (inspectrum).
Is the Inspectrum MCP server safe to use?
Inspectrum scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Inspectrum MCP server expose?
Inspectrum exposes 1 tool: review_plan. Their descriptions and schemas cost roughly 140 tokens of context every time the server is loaded.
Is the Inspectrum MCP server still maintained?
Inspectrum is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Inspectrum MCP server under?
Inspectrum declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.