# Sentinel Scan (npm · sentinel-scan-cli)

MCP security scanner: detect tool poisoning, prompt injection & rug-pulls - 10 OWASP heuristics.

- Trust score: 94/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `sentinel-scan-cli`: 94/100 (this document), [markdown](https://verifymcp.io/servers/ventrova-sentinel-scan-cli/sentinel-scan-cli.md), [page](https://verifymcp.io/servers/ventrova-sentinel-scan-cli/sentinel-scan-cli)

## Channel facts

- Registry: `npm`
- Package: `sentinel-scan-cli`
- Version: `1.4.16`
- 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-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Ventrova/sentinel-scan-cli).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 25 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 225 tokens (~225/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 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 Sentinel Scan MCP server?

Sentinel Scan runs locally as an npm package, launched with npx -y sentinel-scan-cli. 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 ventrova-sentinel-scan-cli -- npx -y sentinel-scan-cli
```

### Cursor

```json
{
  "mcpServers": {
    "ventrova-sentinel-scan-cli": {
      "command": "npx",
      "args": [
        "-y",
        "sentinel-scan-cli"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ventrova-sentinel-scan-cli": {
      "command": "npx",
      "args": [
        "-y",
        "sentinel-scan-cli"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ventrova-sentinel-scan-cli -- npx -y sentinel-scan-cli
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ventrova-sentinel-scan-cli": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "sentinel-scan-cli"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ventrova-sentinel-scan-cli --command npx --arg -y --arg sentinel-scan-cli
```

### Hermes

```yaml
mcp_servers:
  ventrova-sentinel-scan-cli:
    command: "npx"
    args: ["-y", "sentinel-scan-cli"]
```

### Netclaw

```json
{
  "McpServers": {
    "ventrova-sentinel-scan-cli": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "sentinel-scan-cli"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ventrova-sentinel-scan-cli -t stdio -c npx -a -y sentinel-scan-cli
```

### Other

```json
{
  "mcpServers": {
    "ventrova-sentinel-scan-cli": {
      "command": "npx",
      "args": [
        "-y",
        "sentinel-scan-cli"
      ]
    }
  }
}
```

## 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-09-20 (score 94, +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.

### 2026-09-17 (score 93, +1)

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

### 2026-09-15 (score 92, +1)

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

### 2026-09-13 (score 91, +1)

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

### 2026-09-11 (score 90, +1)

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

### 2026-09-09 (score 89, +1)

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

### 2026-09-07 (score 88, +1)

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

### 2026-09-05 (score 87, +1)

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

## MCP tools (1)

### `scan_mcp_manifest` (~225 tokens)

Scan MCP manifest for security findings

Runs a static, offline heuristic security scan (OWASP MCP Top 10 mapped) over an MCP server manifest/config (tools[] + mcpServers{}/servers{} JSON, the same shape as a client config or an mcp.json tool list). Detects tool description/name injection, excessive-agency schemas, command injection risk, hardcoded credentials, unpinned/unsigned sources, wildcard scopes, missing human-in-the-loop confirmation, hidden unicode instructions, cross-origin exfiltration, DoS/resource-exhaustion risk, and tool definition drift (vs. an optional prior-scan baseline). Does not execute any server or tool - pure static analysis of the manifest JSON.

Input parameters:

- `baseline` (object): Optional prior scan output (as previously returned by this tool) to diff against for tool_definition_drift detection.
- `manifest` (object, required): MCP manifest/config object, e.g. { "tools": [...] } and/or { "mcpServers": {...} } / { "servers": {...} } as found in an mcp.json or client config file.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/ventrova-sentinel-scan-cli/sentinel-scan-cli#diagnostics

## Score history

- 2026-09-20: 94
- 2026-09-19: 93
- 2026-09-18: 93
- 2026-09-17: 93
- 2026-09-16: 92
- 2026-09-15: 92
- 2026-09-14: 91
- 2026-09-13: 91
- 2026-09-12: 90
- 2026-09-11: 90
- 2026-09-10: 89
- 2026-09-09: 89
- 2026-09-08: 88
- 2026-09-07: 88
- 2026-09-06: 87
- 2026-09-05: 87
- 2026-09-04: 86
- 2026-09-03: 86
- 2026-09-02: 82
- 2026-09-01: 82
- 2026-08-31: 82
- 2026-08-30: 82
- 2026-08-29: 82
- 2026-08-28: 82
- 2026-08-27: 82
- 2026-08-26: 82
- 2026-08-25: 80

## Common questions

### What is the Sentinel Scan MCP server?

Sentinel Scan is an MCP server listed in the public MCP registry as io.github.Ventrova/sentinel-scan-cli. MCP security scanner: detect tool poisoning, prompt injection & rug-pulls - 10 OWASP heuristics. This page covers its npm package (sentinel-scan-cli).

### Is the Sentinel Scan MCP server safe to use?

Sentinel Scan scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 Sentinel Scan MCP server expose?

Sentinel Scan exposes 1 tool: scan_mcp_manifest. Their descriptions and schemas cost roughly 225 tokens of context every time the server is loaded.

### Is the Sentinel Scan MCP server still maintained?

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

Sentinel Scan 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/sentinel-scan-cli
- Socket report: https://socket.dev/npm/package/sentinel-scan-cli
- Repository: https://github.com/Ventrova/sentinel-scan-cli
- Website: https://ventrova.dev/
- Changelog RSS feed: https://verifymcp.io/servers/ventrova-sentinel-scan-cli/sentinel-scan-cli.xml
- Changelog JSON feed: https://verifymcp.io/servers/ventrova-sentinel-scan-cli/sentinel-scan-cli.json
- HTML version of this page: https://verifymcp.io/servers/ventrova-sentinel-scan-cli/sentinel-scan-cli