SecHelix
PYPI · SECHELIX
Evidence-first security review of authorized repositories. Read-only, root-confined, no shell.
Available components
Last scanned (50 minutes ago)
Scores higher than 87% of PyPI servers
Category Security
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to omarmohelal/SecHelix). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 56 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 226 tokens (~32/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
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 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −3
- Stability: pass → 0.77 functional
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 2 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 functional
- 16 Oct 26 0
- Stability: 0.97 → pass security
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 5 Nov 2026 · Analysed pypi/sechelix@0.3.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | omarmohelal/SecHelix |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/omarmohelal/SecHelix/.github/workflows/publish-pypi.yml@refs/heads/main |
| Rekor log index | 2768348640 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:55c46c7de25021c9fc11e67a94987dd9d3f91ea585b1fc6668946adc77727b99 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
sechelix_audit ~36
Run a STATIC SecHelix audit over a directory.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | string | – | – |
| path | string | – | – |
No output schema declared.
No examples provided.
sechelix_coverage ~25
What previous runs did NOT examine.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | – |
No output schema declared.
No examples provided.
sechelix_doctor ~20
Report which SecHelix components are available.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sechelix_findings ~39
Findings for a run, with why an empty list is empty.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | – |
| run_id | string | yes | – |
No output schema declared.
No examples provided.
sechelix_report ~45
Render a run as markdown, json, sarif or html.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | – |
| path | string | – | – |
| run_id | string | yes | – |
No output schema declared.
No examples provided.
sechelix_run_status ~35
Node statuses and integrity for a recorded run.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | – |
| run_id | string | yes | – |
No output schema declared.
No examples provided.
sechelix_verify ~26
Build safe verification plans for a finding.
| Name | Type | Req | Description |
|---|---|---|---|
| finding_id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the SecHelix MCP server?
SecHelix runs locally as a PyPI package, launched with uvx sechelix. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · sechelix
claude mcp add omarmohelal-sechelix -- uvx sechelix
What is the SecHelix MCP server?
SecHelix is an MCP server listed in the public MCP registry as io.github.omarmohelal/sechelix. Evidence-first security review of authorized repositories. Read-only, root-confined, no shell. This page covers its PyPI package (sechelix).
Is the SecHelix MCP server safe to use?
SecHelix scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 SecHelix MCP server expose?
SecHelix exposes 7 tools: sechelix_audit, sechelix_coverage, sechelix_doctor, sechelix_findings, sechelix_report, and 2 more. Their descriptions and schemas cost roughly 226 tokens of context every time the server is loaded.
Is the SecHelix MCP server still maintained?
SecHelix is still listed as active in the MCP registry. We last reached this channel on 5 November 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 SecHelix MCP server under?
SecHelix declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.