SecHelix

Name: SecHelix
Author: omarmohelal

by omarmohelalversion 0.3.0i★ –iRuns on your computer

Registry nameio.github.omarmohelal/sechelix

Install

Overview

Description from the maker (original English)

Evidence-first security review of authorized repositories. Read-only, root-confined, no shell.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiVery new↓ 23/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "sechelix": {
      "command": "uvx",
      "args": [
        "sechelix",
        "mcp",
        "."
      ]
    }
  }
}

Run this in your terminal

claude mcp add sechelix -- uvx sechelix mcp .

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "sechelix": {
      "command": "uvx",
      "args": [
        "sechelix",
        "mcp",
        "."
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "sechelix": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "sechelix",
        "mcp",
        "."
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account omarmohelal, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

More stars than 0% of the other 5571 servers in this category
Published to the registry more recently than 37% of the other 5571 servers in this category
Basic checks equal to or better than 100% of the other 5571 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is SecHelix safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

by githubWidely used★ 34.2KUpdated 6 days ago

Computer or cloud

Install

Desktop Commander

MCP server for terminal commands, file operations, and process management

by wonderwhy-erWidely used↓ 709.6K/wk★ 10.2KUpdated 18 days ago

Runs on your computer

Install

Cloudflare MCP

Cloudflare MCP servers

by cloudflareWidely used★ 4.4KUpdated 14 months ago

Runs in the cloud✓ mcp.cloudflare.com

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Most AI security tools try to find more. SecHelix tries to prove itself wrong.

SecHelix

Every candidate finding goes to an independent verifier whose only job is to disprove it. The report shows you what it refuted and why — and returns INCOMPLETE rather than a clean PASS when it could not actually check.

Open source, Apache-2.0, for code you own or are authorized to test. Runs in Claude Code, Codex, Copilot and other Agent Skills-compatible agents; the Python runtime is optional.

It helps a coding agent:

map the attack surface and trust boundaries;
review only security checks that apply to the project;
investigate authentication, authorization, business logic, injection, SSRF, files, supply chain, AI/MCP and other security surfaces;
verify important candidates instead of reporting guesses;
fix the root cause;
add regression proof and retest;
return a clear release decision.

See it work in 90 seconds

git clone https://github.com/omarmohelal/SecHelix && cd SecHelix

python examples/expense-api/prove.py

A small multi-tenant API with two candidate issues. One is a real cross-tenant read that a scanner walks past, because the endpoint *does* have an authorization check — it just checks the wrong thing. The other is f-string SQL that every pattern matcher flags and that is not exploitable at all.

Walkthrough, root cause, the two-line fix and the regression proof: [examples/expense-api](examples/expense-api/README.md).

Or take the same test in your browser — ten cases, three of them decoys, no signup: [Can you tell the real bug from the decoy?](https://omarmohelal.github.io/sechelix-challenge/)

Install

Recommended for Agent Skills-compatible coding agents:

npx skills@latest add omarmohelal/SecHelix --skill sechelix

Then open the repository you want to review in your coding agent. The skill installs instructions and data only — no executable code. The optional runtime below is a separate, explicit install.

A compact edition, sechelix-lite, is a single runtime-free review skill (about 200 lines plus five references) for skill directories and hosts where a small context footprint matters. See [docs/distribution/awesome-copilot.md](docs/distribution/awesome-copilot.md).

Use it

Full security audit

Copy this into your agent:

Use SecHelix for a complete authorized security audit of this repository.

Start STATIC and use LOCAL only if it is safe and useful. Map the attack surface and trust boundaries first. Verify important candidates before reporting them. Fix root causes, add regression tests, retest, and give me the final release gate.

Fast security review

Use SecHelix to triage this repository for security issues.

Prioritize authentication, authorization, business logic, secrets, injection, SSRF, file handling, supply chain, dangerous configuration, and AI/MCP surfaces. Return evidence-backed findings and clearly mark anything unproven.

AI-built app launch audit

Use this before launching an AI-generated, agent-generated, rapidly prototyped, or vibe-coded application:

Use SecHelix's AI-Built App Launch Audit on this authorized application.

Evaluate launch checks 01-36 from references/ai-built-app-launch.md. Do not mark PASS without exact code, configuration, policy, test, log, or safe runtime evidence. For every FAIL or security-relevant UNKNOWN, give the realistic failure mode, smallest root-cause fix, and exact safe verification step. After fixes, re-run the failed/unknown checks and produce the normal SecHelix release gate.

The launch profile covers practical pre-release failures around secrets, auth/authz, cross-user data, database/storage permissions, debug exposure, input validation, SQL/NoSQL injection, XSS/CSRF, uploads, traversal, SSRF, password reset, sessions/JWT, CORS, rate limiting, staging, default credentials, webhooks, payments/entitlements, IDOR/BOLA, sensitive logs, and production artifacts.

Review a pull request

Review this PR with SecHelix.

Focus on security changes introduced by the diff, verify important candidates, and tell me whether the PR introduces a verified blocker or known risk.

Fix findings

Use SecHelix Fix Mode on the verified findings.

Fix the root cause, look for variants of the same bug, add security regression tests, and retest the original finding.

More copy-paste workflows: [Command Cookbook](docs/COMMANDS.md).

What should I ask SecHelix to do?

Goal	Ask for
Full repository review	`complete security audit`
Quick first pass	`security triage`
AI-built/vibe-coded app before launch	`AI-Built App Launch Audit`
Broken access control	`authorization / IDOR / BOLA audit`
Login and sessions	`authentication / session / OAuth audit`
Input handling	`injection / XSS / SSRF / files audit`
Payments and workflows	`business logic / race / idempotency audit`
Dependencies and CI	`supply chain / CI/CD audit`
LLMs, agents and tools	`AI / Agent / MCP security audit`
A code change	`PR security review`
Existing verified issues	`Fix Mode`
Release decision	`release gate`
Shareable output	`security report`

You do not need to memorize special slash commands. SecHelix is primarily a skill: tell the coding agent what security job you want done.

How the review works

scope

→ map attack surface → select applicable checks → investigate → independently verify important candidates → fix root cause → add regression proof → retest → report + release gate

A scanner match or model suspicion is treated as a candidate, not automatically as a vulnerability.

A strong finding should show the affected surface, attacker control or security boundary involved, reachability, impact, root cause, safe evidence, the fix, and regression/retest status.

What SecHelix does not claim

It is not a certification. PASS means the release-gate rules found no unresolved blocking condition in what was reviewed, not that the software has no vulnerabilities.
On real code it found 2 of 12 known CVEs. A blinded run against the vulnerable and patched trees of 12 recent CVEs found 2 cleanly under the pre-registered rule, 3 with hand adjudication, and no finding it marked VERIFIED was one of the known defects (report). Precision is NOT_MEASURED.
The model still does the reasoning. SecHelix structures the review and labels unproven claims as unproven rather than dropping them: in that run 92 of 106 findings were marked LIKELY_BUT_UNPROVEN or HYPOTHESIS. It does not make a model see a bug it cannot reason about.
Host support varies. Installation is verified for the Claude Code plugin, the Agent Skills CLI, the portable bundle and the curated Copilot CLI plugin; other hosts are documented paths (compatibility).
Authorized targets only. It is not an internet scanner and ships no exploit payloads.

Full local runtime: SecHelix + embedded Strix

For the complete local stack, including the exact Strix source revision that SecHelix has compatibility-tested, clone with submodules and run the bootstrap:

git clone --recurse-submodules https://github.com/omarmohelal/SecHelix.git

cd SecHelix bash scripts/bootstrap-full.sh

This materializes Strix under engines/strix inside the SecHelix checkout and installs both projects into one Python 3.12 virtual environment. The source is embedded for reproducible installation, while the SecHelix adapter remains the authorization/evidence boundary. OpenRouter setup and first-run commands are in [docs/full-install.md](docs/full-install.md).

Optional CLI runtime

The Agent Skill works without the Python runtime. The runtime is optional and adds stored runs, coverage tracking, replayable evidence, reports, CI-friendly exit codes, and an MCP adapter.

Install it with:

pipx install sechelix

sechelix doctor

uv tool install sechelix and python -m pip install sechelix are also supported.

Useful CLI commands

Command	What it does
`sechelix doctor`	Shows available components and reasoning executors
`sechelix audit . --executor claude-code`	Runs an audit using Claude Code as the reasoning executor
`sechelix audit . --executor gemini-cli`	Runs an audit using Gemini CLI as the reasoning executor
`sechelix audit . --resume-from .sechelix/checkpoints/RUN-....json --executor nexus`	Resumes only unfinished nodes after verifying the sealed checkpoint against the same target, scope, graph and input world
`sechelix launch-audit . --executor claude-code`	Runs evidence-routed AI-built-app launch checks 19-36 without turning “no candidate” into PASS
`sechelix runs`	Lists saved runs and checks their integrity
`sechelix coverage`	Shows what previous runs did not examine
`sechelix report`	Renders the latest saved run
`sechelix replay`	Replays a recorded run offline and checks consistency
`sechelix mcp .`	Serves the local MCP adapter over stdio

Example:

sechelix doctor

sechelix audit . --executor claude-code sechelix launch-audit . --executor claude-code sechelix coverage sechelix report --format markdown

sechelix audit . with the default --executor none intentionally does not pretend to analyze code. Reasoning nodes are blocked and the run remains incomplete until a real executor is configured.

Audit and launch-audit runs now write a self-sealed node-boundary checkpoint under .sechelix/checkpoints/ by default. If the process or host dies, pass that file to --resume-from; completed node evidence is kept, remaining nodes can use a different executor/provider, and resume fails closed if the target commit, scope, graph, input world, budget limits, or checkpoint digest changed.

For all CLI flags:

sechelix --help

sechelix audit --help

Advanced runtime guide: [V4 Runtime Quickstart](docs/v4-quickstart.md).

GitHub Action

- uses: omarmohelal/SecHelix@v4.0.0-alpha.7

with: executor: none

Outputs PASS, PASS_WITH_KNOWN_RISK, BLOCKED or INCOMPLETE, writes SARIF for code scanning, and uploads the run as an artifact. The default executor: none deliberately reports INCOMPLETE rather than a green check it did not earn — configure a reasoning executor to get an actual review.

Full reference: [GitHub Action](docs/github-action.md).

MCP adapter

uvx sechelix mcp /path/to/the/repository

Seven tools over a root you choose, no shell, no network. Six only read; sechelix_audit writes only a run workspace inside that root. The root is the security boundary: point it at the repository under review, not at your home directory.

Reference: [MCP adapter](docs/mcp.md).

Execution modes

Mode	Use it for
`STATIC`	Source, configuration and schema review without dynamic traffic
`LOCAL`	Safe dynamic proof against a local app and fixtures
`STAGING`	Explicitly authorized non-production testing
`PRODUCTION_SAFE`	Bounded, non-destructive verification only

Only test systems you own or are explicitly authorized to assess. See [SECURITY.md](SECURITY.md).

Only the beginning is shown; read the rest in the repo

SecHelix

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

SecHelix

See it work in 90 seconds

Install

Use it

Full security audit

Fast security review

AI-built app launch audit

Review a pull request

Fix findings

What should I ask SecHelix to do?

How the review works

What SecHelix does not claim

Full local runtime: SecHelix + embedded Strix

Optional CLI runtime

Useful CLI commands

GitHub Action

MCP adapter

Execution modes