Sentinel Scan
NPM · SENTINEL-SCAN-CLI
MCP security scanner: detect tool poisoning, prompt injection & rug-pulls - 10 OWASP heuristics.
Available components
Last scanned (22 hours ago)
Scores higher than 96% of npm servers
Category Security
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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Ventrova/sentinel-scan-cli). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 70 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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 1 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.
- 4 Nov 26 −3
- Stability: pass → 0.77 functional
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 −1
- Stability: pass → 0.97 functional
- 22 Oct 26 +1
- Stability: 0.97 → pass security
- 21 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
- 16 Oct 26 −3
- Stability: pass → 0.80 functional
- 15 Oct 26 +1
- 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 4 Nov 2026 · Analysed npm/sentinel-scan-cli@1.4.16
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 | Ventrova/sentinel-scan-cli |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Ventrova/sentinel-scan-cli/.github/workflows/npm-publish.yml@refs/tags/v1.4.16 |
| Rekor log index | 2589209094 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:17164229dcf89ee61bb3688d7506a10a861e979a7cf3133756d9246ad4f1e5f7aba4e8ebc3057b886bc5db365bae78cccfc50f5a6bedb8dea9ab896bf |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
scan_mcp_manifest Scan MCP manifest for security findings ~225
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.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline | object | – | Optional prior scan output (as previously returned by this tool) to diff against for tool_definition_drift detection. |
| manifest | object | yes | MCP manifest/config object, e.g. { "tools": [...] } and/or { "mcpServers": {...} } / { "servers": {...} } as found in an mcp.json or client config file. |
No output schema declared.
No examples provided.
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.
npm · sentinel-scan-cli
claude mcp add ventrova-sentinel-scan-cli -- npx -y sentinel-scan-cli
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 93 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 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 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 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.