Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.salrad22/code-sentinel

NPM · CODE-SENTINEL-MCP · SCANNED SEP 22

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

Available components

npm · code-sentinel-mcp 85
0 this week 85 Trust /100
Trust breakdown (7 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 → 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
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency44
Schema Quality & AI Usability85
  • 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 Management97
  • Stability observed for 29 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
Install

How do I install the io.github.salrad22/code-sentinel MCP server?

io.github.salrad22/code-sentinel runs locally as an npm package, launched with npx -y code-sentinel-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 · code-sentinel-mcp

# add to Claude Code
claude mcp add salrad22-code-sentinel -- npx -y code-sentinel-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "salrad22-code-sentinel": {
      "command": "npx",
      "args": [
        "-y",
        "code-sentinel-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "salrad22-code-sentinel": {
      "command": "npx",
      "args": [
        "-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"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "salrad22-code-sentinel": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "code-sentinel-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add salrad22-code-sentinel -t stdio -c npx -a -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.

  • 21 Sept 26 +1

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

  • 19 Sept 26 +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.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

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

  • 12 Sept 26 +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.

  • 11 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 10 Sept 26 +1

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

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 22 Sept 2026 · Analysed npm/code-sentinel-mcp@0.2.6

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 →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

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. 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 →

Tool Tokens
analyze_code ~63

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

NameTypeReqDescription
codestringyesThe source code to analyze
filenamestringyesThe 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.

NameTypeReqDescription
codestringyesThe source code to analyze
filenamestringyesThe 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.

NameTypeReqDescription
codestringyesThe source code to analyze
filenamestringyesThe filename (used to detect language)
levelstring–Pattern level to analyze: 'architectural' (system structure), 'design' (GoF patterns), 'code' (implementation idioms), or 'all' (default)
querystring–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.)

NameTypeReqDescription
codestringyesThe source code to check
filenamestringyesThe filename

No output schema declared.

No examples provided.

check_placeholders ~48

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

NameTypeReqDescription
codestringyesThe source code to check
filenamestringyesThe filename

No output schema declared.

No examples provided.

check_security ~48

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

NameTypeReqDescription
codestringyesThe source code to check
filenamestringyesThe 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.

NameTypeReqDescription
codestringyesThe source code to analyze
filenamestringyesThe filename (used to detect language). Example: 'app.ts'

No output schema declared.

No examples provided.

Common questions

What is the io.github.salrad22/code-sentinel MCP server?

io.github.salrad22/code-sentinel is an MCP server listed in the public MCP registry as io.github.salrad22/code-sentinel. Code quality analysis MCP server - detects security issues, deceptive patterns, and placeholders. This page covers its npm package (code-sentinel-mcp).

Is the io.github.salrad22/code-sentinel MCP server safe to use?

io.github.salrad22/code-sentinel scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 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.salrad22/code-sentinel MCP server expose?

io.github.salrad22/code-sentinel exposes 7 tools: analyze_code, generate_report, check_security, check_deceptive_patterns, check_placeholders, and 2 more. Their descriptions and schemas cost roughly 476 tokens of context every time the server is loaded.

Is the io.github.salrad22/code-sentinel MCP server still maintained?

io.github.salrad22/code-sentinel is still listed as active in the MCP registry. We last reached this channel on 22 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 io.github.salrad22/code-sentinel MCP server under?

io.github.salrad22/code-sentinel declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.