Codesentinel MCP server

by icohangar-ops·io.github.icohangar-ops/codesentinel-mcp·v1.0.2

No reviews yet

Codebase health MCP: dead code, cycles, coupling, architectural drift.

C65/100grade C

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

C65/100

full report

Adoption

New

0 stars93 downloads/wk

Reviews

Write one

Nobody has reviewed Codesentinel yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Codesentinel tools (6, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

analyze_coupling
Analyze coupling metrics across the codebase. Identifies modules with high fan-out (too many dependencies) and tightly coupled clusters.
analyze_dead_code
Analyze a codebase for dead code — functions, classes, and modules that are defined but never referenced. Returns findings with file paths, line numbers, severity, and fix suggestions.
detect_architectural_drift
Detect architectural drift — violations of intended layer boundaries (e.g., UI importing from data layer, reverse dependencies).
detect_circular_deps
Detect circular dependencies between modules using DFS-based cycle detection. Returns cycles with involved files and impact assessment.
explain_finding
Get a detailed explanation of a specific code health finding, including why it matters, potential risks, and detailed remediation steps.
full_health_scanwrite action
Run a complete codebase health scan: dead code, circular dependencies, coupling metrics, and architectural drift. Returns an overall health score (0-100) and prioritized findings.

Public scan report

scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it

no findings

Code scan31 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancerepository not readable: repo not found3/15
Maintainer identityno repository or website to verify2/10

Overall 65/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Codesentinel compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 65/100; higher than 20% of 48,255 servers
Tools: 6; the typical server has 7
Tools that change things: 17%; typical: 0%. Fewer write tools means less an agent can break
Downloads a week: 93; more than 61% of 12,191 servers with a package

What its tools let an agent do: 5 read · 1 change

Install Codesentinel in Claude Code, Cursor or VS Code

Runs npx -y @cubiczan/codesentinel-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add codesentinel-mcp -- npx -y @cubiczan/codesentinel-mcp

Add to Cursor

What the publisher says

From the Codesentinel repository's README, as published. We do not edit it. Read it on GitHub

CodeHealth MCP

Codebase health analysis that works everywhere. Dead code, circular dependencies, coupling issues, and architectural drift — exposed as MCP tools for Claude Desktop, Cursor, Windsurf, and Slack.

The Problem

Dead code, circular dependencies, excessive coupling, and architectural drift are invisible in day-to-day work. Static analysis tools produce noise in CI dashboards nobody checks. CodeHealth MCP brings these insights into the tools developers actually use — via the Model Context Protocol.

What CodeHealth MCP Does

7 analysis tools, available in any MCP-compatible client:

Where It Works

Claude Desktop Config (stdio)

{
  "mcpServers": {
    "codehealth": {
      "command": "node",
      "args": ["/path/to/codehealth-mcp/mcp-server/index.js"]
    }
  }
}

Remote Streamable HTTP (Glama / hosted)

Public HTTPS + streamable-http is required to list CodeSentinel as a Glama remote connector. Replace the host from your deploy env — do not commit a fake hostname.

export MCP_BEARER_TOKEN="replace-with-a-long-random-secret"
npm run mcp:http

Local default: http://127.0.0.1:8787/mcp (health: GET /health). Production must be HTTPS.

{
  "mcpServers": {
    "codesentinel": {
      "type": "streamable-http",
      "url": "https://${MCP_HTTP_HOST}/mcp",
      "headers": {
        "Authorization": "Bearer ${MCP_BEARER_TOKEN}"
      }
    }
  }
}

Cursor / Claude remote connectors use the same url + Authorization header. Unauthenticated /mcp returns HTTP 401. LLMAPIKEY and other provider keys stay on the server and are never echoed.

Deploy on Vercel (public HTTPS)

Stateless Streamable HTTP (JSON request/response) runs on Vercel Fluid Compute. No sticky sessions. Do not invent a hostname — use the URL Vercel assigns.

npx vercel          # preview
npx vercel env add MCP_BEARER_TOKEN     # required for /mcp — fail-closed Bearer auth
npx vercel env add LLM_API_KEY          # optional, server-side only
npx vercel env add DAYTONA_API_KEY      # optional, isolated GitHub scans
npx vercel env add GITHUB_TOKEN         # optional, private repo fetch
npx vercel --prod
# GET /health must be 200 even if MCP_BEARER_TOKEN is not set yet.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

2026-11-01downgradeA → Cscore 65

Codesentinel: common questions

Is Codesentinel MCP server safe?: With care: it is graded C, so read the findings first (65/100). Read the Codesentinel safety report
How do I install Codesentinel?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Codesentinel need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Codesentinel maintained?: The last commit was 45 days ago (2026-09-20). The latest release is v1.0.2.
What can I use instead of Codesentinel?: Servers from other publishers that do the same job: pyscn MCP server.
How does Codesentinel compare with other MCP servers?: safety score 65/100 (higher than 20% of 48,255 servers); tools 6 (the typical server has 7); tools that change things 17% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Codesentinel

Same job from other publishers: the closest match first, then the best rated.

pyscn
Python code analysis for AI agents: complexity, dead code, clones, coupling, and a health score.
not reviewed
Established
A