io.github.icohangar-ops/codesentinel-mcp
NPM · @CUBICZAN/CODESENTINEL-MCP
Codebase health MCP: dead code, cycles, coupling, architectural drift.
Available components
Last scanned (7 hours ago)
Scores higher than 65% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects adm-zip 0.5.18, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 384 of 385 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 62 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 400 tokens (~66/item across 6 items; 6 tools + 0 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 Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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.
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
- 22 Oct 26 0
- CVE-2026-114104 affects this package: high ▼ security
- CVE-2026-114102 affects this package: high ▼ security
- CVE-2026-114103 affects this package: high ▼ security
- GHSA-8238-w5pm-2374 no longer affects this package ▲ security
- GHSA-c6fg-446q-cg94 no longer affects this package ▲ security
- GHSA-p634-w6r4-rjp2 no longer affects this package ▲ security
- 19 Oct 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 18 Oct 26 +1
- CVE-2026-44294 affects this package: high ▼ security
- CVE-2026-44289 affects this package: high ▼ security
- CVE-2026-44292 affects this package: high ▼ security
- CVE-2026-44288 affects this package: high ▼ security
- CVE-2026-45740 affects this package: high ▼ security
- CVE-2026-44291 affects this package: high ▼ security
- CVE-2026-54269 affects this package: high ▼ security
- CVE-2026-44293 affects this package: high ▼ security
- CVE-2026-59877 affects this package: high ▼ security
- CVE-2026-48712 affects this package: high ▼ security
- CVE-2026-44290 affects this package: high ▼ security
- Security disclosure: fail → unverified ▼ functional
- 17 Oct 26 0
- CVE-2026-44292 no longer affects this package ▲ security
- CVE-2026-48712 no longer affects this package ▲ security
- CVE-2026-44289 no longer affects this package ▲ security
- CVE-2026-59877 no longer affects this package ▲ security
- CVE-2026-44293 no longer affects this package ▲ security
- CVE-2026-54269 no longer affects this package ▲ security
- CVE-2026-44288 no longer affects this package ▲ security
- CVE-2026-44291 no longer affects this package ▲ security
- CVE-2026-44290 no longer affects this package ▲ security
- CVE-2026-45740 no longer affects this package ▲ security
- CVE-2026-44294 no longer affects this package ▲ security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 −3
- Stability: pass → 0.80 functional
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 24 Oct 2026 · Analysed npm/@cubiczan/codesentinel-mcp@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 22 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-8988-4f7v-96qf | CVE-2026-54285 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-45rx-2jwx-cxfr | CVE-2026-59892 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-7q85-xj36-vmfc | CVE-2026-77301 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-8238-w5pm-2374 | CVE-2026-114102 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-c6fg-446q-cg94 | CVE-2026-114103 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-j5f4-cc29-5x44 | CVE-2026-102282 | high | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-p634-w6r4-rjp2 | CVE-2026-114104 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-rcw4-f5rp-g42v | CVE-2026-92000 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-vwc7-r8mq-g2x9 | CVE-2026-76845 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N | no |
| GHSA-xcpc-8h2w-3j85 | CVE-2026-39244 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-2pr8-phx7-x9h3 | CVE-2026-44294 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-66ff-xgx4-vchm | CVE-2026-44293 | high | yes | |
| GHSA-685m-2w69-288q | CVE-2026-44289 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-75px-5xx7-5xc7 | CVE-2026-44291 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-f38q-mgvj-vph7 | CVE-2026-54269 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-fx83-v9x8-x52w | CVE-2026-44292 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-j3f2-48v5-ccww | CVE-2026-59877 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-jggg-4jg4-v7c6 | CVE-2026-45740 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-jvwf-75h9-cwgg | CVE-2026-44290 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-q6x5-8v7m-xcrf | CVE-2026-44288 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-wcpc-wj8m-hjx6 | CVE-2026-48712 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 384 packages
| Packages resolved | 384 |
|---|---|
| Deprecated | 4 |
| Stale | 104 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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 →
analyze_coupling ~65
Analyze coupling metrics across the codebase. Identifies modules with high fan-out (too many dependencies) and tightly coupled clusters.
| Name | Type | Req | Description |
|---|---|---|---|
| fan_out_threshold | number | – | Fan-out threshold for flagging modules |
| repo_path | string | – | Path or URL to the repository |
No output schema declared.
No examples provided.
analyze_dead_code ~75
Analyze a codebase for dead code — functions, classes, and modules that are defined but never referenced. Returns findings with file paths, line numbers, severity, and fix suggestions.
| Name | Type | Req | Description |
|---|---|---|---|
| include_suggestions | boolean | – | Whether to include fix suggestions |
| repo_path | string | – | Path or URL to the repository to analyze |
No output schema declared.
No examples provided.
detect_architectural_drift ~80
Detect architectural drift — violations of intended layer boundaries (e.g., UI importing from data layer, reverse dependencies).
| Name | Type | Req | Description |
|---|---|---|---|
| layers_config | string | – | JSON string defining layer patterns, e.g. {"ui": ["src/components/"], "data": ["src/db/"]} |
| repo_path | string | – | Path or URL to the repository |
No output schema declared.
No examples provided.
detect_circular_deps ~45
Detect circular dependencies between modules using DFS-based cycle detection. Returns cycles with involved files and impact assessment.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | – | Path or URL to the repository |
No output schema declared.
No examples provided.
explain_finding ~77
Get a detailed explanation of a specific code health finding, including why it matters, potential risks, and detailed remediation steps.
| Name | Type | Req | Description |
|---|---|---|---|
| codebase_context | string | – | Additional context about the codebase (language, framework, etc.) |
| finding_description | string | yes | Description of the specific finding to explain |
| finding_type | string | yes | – |
No output schema declared.
No examples provided.
full_health_scan ~58
Run a complete codebase health scan: dead code, circular dependencies, coupling metrics, and architectural drift. Returns an overall health score (0-100) and prioritized findings.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | – | Path or URL to the repository |
No output schema declared.
No examples provided.
How do I install the io.github.icohangar-ops/codesentinel-mcp server?
io.github.icohangar-ops/codesentinel-mcp runs locally as an npm package, launched with npx -y @cubiczan/codesentinel-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @cubiczan/codesentinel-mcp
claude mcp add icohangar-ops-codesentinel-mcp -- npx -y @cubiczan/codesentinel-mcp
What is the io.github.icohangar-ops/codesentinel-mcp server?
io.github.icohangar-ops/codesentinel-mcp is listed in the public MCP registry as io.github.icohangar-ops/codesentinel-mcp. Codebase health MCP: dead code, cycles, coupling, architectural drift. This page covers its npm package (@cubiczan/codesentinel-mcp).
Is the io.github.icohangar-ops/codesentinel-mcp server safe to use?
io.github.icohangar-ops/codesentinel-mcp scores 79 out of 100 on VerifyMCP. We recorded 22 known advisories against it as of 24 October 2026. It declares no install or post-install scripts. 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 io.github.icohangar-ops/codesentinel-mcp server expose?
io.github.icohangar-ops/codesentinel-mcp exposes 6 tools: analyze_dead_code, detect_circular_deps, analyze_coupling, detect_architectural_drift, full_health_scan, explain_finding. Their descriptions and schemas cost roughly 400 tokens of context every time the server is loaded.
Is the io.github.icohangar-ops/codesentinel-mcp server still maintained?
io.github.icohangar-ops/codesentinel-mcp is still listed as active in the MCP registry. We last reached this channel on 24 October 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 io.github.icohangar-ops/codesentinel-mcp server under?
io.github.icohangar-ops/codesentinel-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.