# CodeDiag (npm · @sabahattink/codediag)

Find Node.js API routes with no auth check or input validation, and scan project health.

- Trust score: 81/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@sabahattink/codediag`: 81/100 (this document), [markdown](https://verifymcp.io/servers/sabahattink-codediag/sabahattink-codediag.md), [page](https://verifymcp.io/servers/sabahattink-codediag/sabahattink-codediag)

## Channel facts

- Registry: `npm`
- Package: `@sabahattink/codediag`
- Version: `0.13.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 94/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known medium-severity CVE affects minimatch 10.2.6, reached via ts-morph > @ts-morph/common > minimatch. A fixed version is available.
  - No install/post-install scripts declared.
  - 11 of 40 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to sabahattink/codediag).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 584 tokens (~194/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the CodeDiag MCP server?

CodeDiag runs locally as an npm package, launched with npx -y @sabahattink/codediag. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add sabahattink-codediag -- npx -y @sabahattink/codediag
```

### Cursor

```json
{
  "mcpServers": {
    "sabahattink-codediag": {
      "command": "npx",
      "args": [
        "-y",
        "@sabahattink/codediag"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sabahattink-codediag": {
      "command": "npx",
      "args": [
        "-y",
        "@sabahattink/codediag"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add sabahattink-codediag -- npx -y @sabahattink/codediag
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sabahattink-codediag": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@sabahattink/codediag"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sabahattink-codediag --command npx --arg -y --arg @sabahattink/codediag
```

### Hermes

```yaml
mcp_servers:
  sabahattink-codediag:
    command: "npx"
    args: ["-y", "@sabahattink/codediag"]
```

### Netclaw

```json
{
  "McpServers": {
    "sabahattink-codediag": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@sabahattink/codediag"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add sabahattink-codediag -t stdio -c npx -a -y @sabahattink/codediag
```

### Other

```json
{
  "mcpServers": {
    "sabahattink-codediag": {
      "command": "npx",
      "args": [
        "-y",
        "@sabahattink/codediag"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 65, −13)

- [security regression] Malware scan: pass → unverified
- [security] Known CVEs: CVE check failed: a known medium-severity CVE affects minimatch 10.2.6, reached via ts-morph > @ts-morph/common > minimatch. A fixed version is available.
- [functional] Package version: 0.11.2 → 0.13.0
- [functional] Package version: 0.11.2 → 0.12.0

### 2026-11-01 (score 78)

First indexed and scored.

## MCP tools (3)

### `find_unprotected_routes` (~192 tokens)

Find unprotected API routes

List the API routes, form actions, and procedures in a Node.js project that anyone can call: no recognizable auth check, or no input validation. Understands where auth runs in Next.js, SvelteKit, React Router/Remix, Express, Fastify, Hono, Elysia, NestJS, and tRPC (middleware and its matcher, hooks, guards, route middleware, tRPC context). Runs offline. Static analysis: read the cited file before calling a route vulnerable.

Input parameters:

- `check` (string): auth: routes without an auth check; validation: routes without input validation; both (default).
- `maxResults` (integer): The most routes to return. Defaults to 100.
- `path` (string): Absolute path of the project directory. Pass it: the server's working directory may not be the project. A relative path resolves against that working directory, the default.

Output parameters:

- `directory` (string)
- `framework` (string)
- `omitted` (number)
- `project` (string)
- `routes` (array)
- `summary` (string)
- `supported` (boolean)
- `suppressed` (number)

### `scan_project` (~182 tokens)

Scan project health

Run a full CodeDiag scan of a Node.js project: a 0-100 health score with API health, security, dependency, test, and structure findings, each with a rule ID, file, line, and suggested fix. Security includes Supabase tables without row level security, from supabase/migrations. Most severe findings first. Offline unless audit is true.

Input parameters:

- `audit` (boolean): Also run the package manager's vulnerability audit, which needs network access. Defaults to false.
- `maxFindings` (integer): The most findings to return. Defaults to 50.
- `minSeverity` (string): Leave out findings below this severity. Defaults to warning.
- `path` (string): Absolute path of the project directory. Pass it: the server's working directory may not be the project. A relative path resolves against that working directory, the default.

Output parameters:

- `analyzers` (array)
- `directory` (string)
- `findings` (array)
- `framework` (string)
- `grade` (string)
- `omitted` (number)
- `project` (string)
- `score` (number)
- `summary` (string)

### `explain_rule` (~70 tokens)

Explain a CodeDiag rule

Explain a CodeDiag rule ID (the ID in a finding, such as missing-auth-check): what it detects, its severity, CWE and OWASP mapping, documentation link, and how to suppress a finding that is intentional.

Input parameters:

- `ruleId` (string, required): The rule ID, for example missing-auth-check.

Output parameters:

- `analyzer` (string)
- `cwe` (array)
- `defaultSeverity` (string)
- `description` (string)
- `docs` (string)
- `id` (string)
- `owasp` (array)
- `suppress` (string)
- `title` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/sabahattink-codediag/sabahattink-codediag#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 80
- 2026-11-02: 65
- 2026-11-01: 78

## Common questions

### What is the CodeDiag MCP server?

CodeDiag is an MCP server listed in the public MCP registry as io.github.sabahattink/codediag. Find Node.js API routes with no auth check or input validation, and scan project health. This page covers its npm package (@sabahattink/codediag).

### Is the CodeDiag MCP server safe to use?

CodeDiag scores 81 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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 CodeDiag MCP server expose?

CodeDiag exposes 3 tools: find_unprotected_routes, scan_project, explain_rule. Their descriptions and schemas cost roughly 444 tokens of context every time the server is loaded.

### Is the CodeDiag MCP server still maintained?

CodeDiag is still listed as active in the MCP registry. We last reached this channel on 5 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 CodeDiag MCP server under?

CodeDiag declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@sabahattink/codediag
- Socket report: https://socket.dev/npm/package/@sabahattink/codediag
- Repository: https://github.com/sabahattink/codediag
- Website: https://sabahattink.github.io/codediag/
- Changelog RSS feed: https://verifymcp.io/servers/sabahattink-codediag/sabahattink-codediag.xml
- Changelog JSON feed: https://verifymcp.io/servers/sabahattink-codediag/sabahattink-codediag.json
- HTML version of this page: https://verifymcp.io/servers/sabahattink-codediag/sabahattink-codediag