io.github.salrad22/code-sentinel

NPM · CODE-SENTINEL-MCP · SCANNED AUG 3

Code quality analysis MCP server - detects security issues, deceptive patterns, and placeholders

Available components

+17 this week 70 70 Trust /100

Trust breakdown (6 categories)

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 →

Supply Chain Security87

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (95 of 99), 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 211 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability82

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 613 tokens (~43/item across 14 items; 7 tools + 7 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management23

Stability observed for 7 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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · code-sentinel-mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add salrad22-code-sentinel -- npx -y code-sentinel-mcp

# add to Codex CLI

codex mcp add salrad22-code-sentinel -- npx -y code-sentinel-mcp

// opencode.json

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

# add to OpenClaw

openclaw mcp add salrad22-code-sentinel --command npx --arg -y --arg code-sentinel-mcp

# ~/.hermes/config.yaml

mcp_servers:
  salrad22-code-sentinel:
    command: "npx"
    args: ["-y", "code-sentinel-mcp"]

// mcp.json

{
  "mcpServers": {
    "salrad22-code-sentinel": {
      "command": "npx",
      "args": [
        "-y",
        "code-sentinel-mcp"
      ]
    }
  }
}

Changelog

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 Aug 26 +44
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
1 Aug 26 +21
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
31 Jul 26 −48
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
27 Jul 26 53

First indexed and scored.

Show 3 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 7 exposed · ~476 tokens

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.

Tool Tokens

analyze_code ~63

Analyze code for security issues, errors, deceptive patterns, and placeholders. Returns a structured analysis with issues and strengths.

Input Output Examples

Name	Type	Req	Description
code	string	yes	The source code to analyze
filename	string	yes	The filename (used to detect language). Example: 'app.ts'

No output schema declared.

No examples provided.

analyze_design_patterns ~72

Focused analysis of Gang of Four (GoF) design patterns in code. Detects Singleton, Factory, Observer, Strategy, and other classic patterns with confidence levels and implementation details.

Input Output Examples

Name	Type	Req	Description
code	string	yes	The source code to analyze
filename	string	yes	The filename (used to detect language)

No output schema declared.

No examples provided.

analyze_patterns ~137

Analyze code for architectural, design, and implementation patterns. Detects pattern usage, inconsistencies, and provides actionable suggestions for improvement. Returns LLM-optimized JSON with action items.

Input Output Examples

Name	Type	Req	Description
code	string	yes	The source code to analyze
filename	string	yes	The filename (used to detect language)
level	string	—	Pattern level to analyze: 'architectural' (system structure), 'design' (GoF patterns), 'code' (implementation idioms), or 'all' (default)
query	string	—	Optional natural language query to focus analysis (e.g., 'how is error handling done?')

No output schema declared.

No examples provided.

check_deceptive_patterns ~52

Check for code patterns that hide errors or create false confidence (empty catches, silent failures, etc.)

Input Output Examples

Name	Type	Req	Description
code	string	yes	The source code to check
filename	string	yes	The filename

No output schema declared.

No examples provided.

check_placeholders ~48

Check for placeholder code, dummy data, TODO/FIXME comments, and incomplete implementations

Input Output Examples

Name	Type	Req	Description
code	string	yes	The source code to check
filename	string	yes	The filename

No output schema declared.

No examples provided.

check_security ~48

Check code for security vulnerabilities only (hardcoded secrets, SQL injection, XSS, etc.)

Input Output Examples

Name	Type	Req	Description
code	string	yes	The source code to check
filename	string	yes	The filename

No output schema declared.

No examples provided.

generate_report ~56

Analyze code and generate a detailed HTML report with visual indicators for issues and strengths.

Input Output Examples

Name	Type	Req	Description
code	string	yes	The source code to analyze
filename	string	yes	The filename (used to detect language). Example: 'app.ts'

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug