Codesentinel

Created By
Rasha Salim5 months ago
Overview

what is CodeSentinel?

CodeSentinel is a comprehensive code quality analysis server designed for the Model Context Protocol (MCP). It integrates with various MCP-compatible clients to detect security vulnerabilities, deceptive patterns, incomplete code, and highlight good practices in code.

how to use CodeSentinel?

To use CodeSentinel, install it via npm or clone the repository from GitHub. You can then integrate it with Claude Code or run it directly to analyze your code for quality issues.

key features of CodeSentinel?

  • Security Analysis: Detects hardcoded secrets, SQL injection, XSS, and more.
  • Deceptive Pattern Detection: Identifies patterns that hide errors or create false confidence.
  • Placeholder Detection: Finds TODOs, dummy data, and incomplete implementations.
  • Error & Code Smell Detection: Analyzes for type coercion issues, null references, and async anti-patterns.
  • Strength Recognition: Highlights good practices in code.
  • HTML Reports: Generates visual reports with quality scores and actionable suggestions.

use cases of CodeSentinel?

  1. Analyzing code for security vulnerabilities before deployment.
  2. Ensuring code quality by detecting deceptive patterns and placeholders.
  3. Generating reports for code reviews and audits.

FAQ from CodeSentinel?

  • Can CodeSentinel analyze all programming languages?

CodeSentinel supports multiple languages including TypeScript, JavaScript, Python, Go, Rust, and Java.

  • Is CodeSentinel free to use?

Yes! CodeSentinel is open-source and free to use.

  • How does CodeSentinel reduce false positives?

CodeSentinel includes verification-aware detection steps in many patterns to minimize false positives.

Server Config

{
  "mcpServers": {
    "code-sentinel": {
      "command": "npx",
      "args": [
        "code-sentinel-mcp"
      ]
    }
  }
}
Project Info
Created At
5 months ago
Updated At
5 months ago
Author Name
Rasha Salim
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago