T
Toraastrta/sphior-code
Deterministic security scanning for source code — hard-coded secrets, insecure patterns mapped to
★ 1·updated 2026-11-17
View on GitHub ↗Direct link · no redirect page
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 1 ★ · Toraastrta/sphior-code · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 1 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
Toraastrta/sphior-code;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# SPHIOR CODE
Excerpted from the repository README (abridged)
Deterministic security scanning for source code — hard-coded secrets, insecure patterns mapped to
CWE, and data-flow (taint) analysis — in your terminal, CI, VS Code, JetBrains IDEs
and AI coding assistants. It runs entirely on your machine.
No AI in detection. No source upload. No telemetry. No account. The same code always produces
the same findings.
## Contents
Try it in 10 seconds
Where you can use it
What it detects
What a finding looks like
Command line
CI and GitHub code scanning
Excluding paths and accepting findings
VS Code
JetBrains IDEs
AI coding assistants (MCP)
Agent skills — Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, claude.ai
Scan on every edit — Claude Code, Codex, Cursor
Evidence records
Privacy and data boundary
What it does not do
SPHIOR CODE on GitHub
AI governance MCP server
Versions
Repository layout and building from source
## Try it in 10 seconds
No install, no account, no config. Requires Node.js 18+.
bash
npx @sphior/scan run .
In a terminal you get a table sorted by severity:
critical app.js:4 Stripe Live Secret Key (CWE-798)
critical app.js:6 SQL injection (untrusted input → query) (CWE-89)
critical app.js:9 Command injection (untrusted input → shell) (CWE-78)
high app.js:12 XSS (untrusted input → HTML sink) (CWE-79)
high util.py:3 Unsafe pickle deserialization (CWE-502)
high util.py:5 TLS verification disabled (verify=False) (CWE-295)
medium util.py:2 Weak hash algorithm (CWE-327)
SPHIOR CODE: 9 findings (critical=3 high=5 medium=1 low=0) 3 files scanned engine=0.1.0 ruleset=2026.10.23-24
Piped, the same command prints SARIF instead, so npx @sphior/scan run . | jq works.
Then hand the findings to the AI assistant you already use:
bash
claude mcp add sphior-code -- npx -y sphior-code-mcp
and ask it: "Scan this project and fix the critical issues."
## Where you can use it
One detection engine, several ways in. Everything in this table runs locally and needs no account.
| Surface | Package | What you get |
| Command line | @sphior/scan | Scan a directory or a single file. Table, SARIF, JSON or AI fix context. Fails the build by severity. |
| CI | @sphior/scan | SARIF for GitHub code scanning and most CI dashboards. --fail-on gate. |
| GitHub Actions | Toraastrta/sphior-scan-action | One step: scan, job summary, Security tab, fail-on gate. |
| pre-commit | hook in this repository | Scan before every commit and stop it on serious findings. |
| VS Code (and Cursor, Windsurf, VSCodium) | sphior.sphior-code · Open VSX | Findings as you type. A quick fix that hands the finding to your AI. |
| JetBrains IDEs | plugin 33696 | The same in IntelliJ IDEA, PyCharm, WebStorm, GoLand, Rider, PhpStorm, RubyMine, CLion and others. |
| Zed | packages/sphior-zed | Findings as you type, and the MCP server for Zed's agent. Two extensions. |
| AI coding assistants | sphior-code-mcp | An MCP server. Your assistant scans the workspace and receives the location and the remediation for each finding. |
| Agent skills | plugin/skills | Four skills — fix, triage, set up CI, pre-release gate — for Claude Code, Codex, Cursor, GitHub Copilot and claude.ai. |
| Claude Code | plugin in this repository | All four skills in one install; add the MCP server with one command. |
CWE, and data-flow (taint) analysis — in your terminal, CI, VS Code, JetBrains IDEs
and AI coding assistants. It runs entirely on your machine.
No AI in detection. No source upload. No telemetry. No account. The same code always produces
the same findings.
## Contents
Try it in 10 seconds
Where you can use it
What it detects
What a finding looks like
Command line
CI and GitHub code scanning
Excluding paths and accepting findings
VS Code
JetBrains IDEs
AI coding assistants (MCP)
Agent skills — Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, claude.ai
Scan on every edit — Claude Code, Codex, Cursor
Evidence records
Privacy and data boundary
What it does not do
SPHIOR CODE on GitHub
AI governance MCP server
Versions
Repository layout and building from source
## Try it in 10 seconds
No install, no account, no config. Requires Node.js 18+.
bash
npx @sphior/scan run .
In a terminal you get a table sorted by severity:
critical app.js:4 Stripe Live Secret Key (CWE-798)
critical app.js:6 SQL injection (untrusted input → query) (CWE-89)
critical app.js:9 Command injection (untrusted input → shell) (CWE-78)
high app.js:12 XSS (untrusted input → HTML sink) (CWE-79)
high util.py:3 Unsafe pickle deserialization (CWE-502)
high util.py:5 TLS verification disabled (verify=False) (CWE-295)
medium util.py:2 Weak hash algorithm (CWE-327)
SPHIOR CODE: 9 findings (critical=3 high=5 medium=1 low=0) 3 files scanned engine=0.1.0 ruleset=2026.10.23-24
Piped, the same command prints SARIF instead, so npx @sphior/scan run . | jq works.
Then hand the findings to the AI assistant you already use:
bash
claude mcp add sphior-code -- npx -y sphior-code-mcp
and ask it: "Scan this project and fix the critical issues."
## Where you can use it
One detection engine, several ways in. Everything in this table runs locally and needs no account.
| Surface | Package | What you get |
| Command line | @sphior/scan | Scan a directory or a single file. Table, SARIF, JSON or AI fix context. Fails the build by severity. |
| CI | @sphior/scan | SARIF for GitHub code scanning and most CI dashboards. --fail-on gate. |
| GitHub Actions | Toraastrta/sphior-scan-action | One step: scan, job summary, Security tab, fail-on gate. |
| pre-commit | hook in this repository | Scan before every commit and stop it on serious findings. |
| VS Code (and Cursor, Windsurf, VSCodium) | sphior.sphior-code · Open VSX | Findings as you type. A quick fix that hands the finding to your AI. |
| JetBrains IDEs | plugin 33696 | The same in IntelliJ IDEA, PyCharm, WebStorm, GoLand, Rider, PhpStorm, RubyMine, CLion and others. |
| Zed | packages/sphior-zed | Findings as you type, and the MCP server for Zed's agent. Two extensions. |
| AI coding assistants | sphior-code-mcp | An MCP server. Your assistant scans the workspace and receives the location and the remediation for each finding. |
| Agent skills | plugin/skills | Four skills — fix, triage, set up CI, pre-release gate — for Claude Code, Codex, Cursor, GitHub Copilot and claude.ai. |
| Claude Code | plugin in this repository | All four skills in one install; add the MCP server with one command. |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/toraastrta-sphior-code/)
- Source
- awesome · https://github.com/Toraastrta/sphior-code
- Browse by field
- MCP servers
- Traction
- 1 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.