io.github.Toraastrta/sphior-code-mcp
NPM · SPHIOR-CODE-MCP
Deterministic SAST/SCA findings + fix guidance for your AI agent. Runs locally, no account needed.
Available components
Last scanned (1 hour ago)
Scores higher than 50% of npm 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 105 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 16 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 710 tokens (~88/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 −4
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 +1
- Package version: 1.0.2 → 1.1.6 functional
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 npm/sphior-code-mcp@1.1.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 105 packages
| Packages resolved | 105 |
|---|---|
| Stale | 30 |
| 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 →
get_finding ~73
Fetch full details of a single security finding by ID — includes CVSS score, CWE classification, exact file path and line number, vulnerability message, and fix hint. Use when the user wants to investigate a specific issue from list_findings.
| Name | Type | Req | Description |
|---|---|---|---|
| findingId | string | yes | Finding UUID — obtain via list_findings |
No output schema declared.
No examples provided.
get_fix_context ~217
Scan for security problems and get deterministic remediation guidance so YOU (the AI agent) can fix them. Works with no account: without SPHIOR_API_KEY it scans the local workspace with the bundled engine. SPHIOR does not generate code or transmit source — open the referenced file in your workspace, read the code yourself, and apply the fix. Returns why-it-matters, remediation steps, exact location, and references. Findings at the same line are merged into one entry; `also` lists the others and one fix must satisfy all. A human must review before merge.
| Name | Type | Req | Description |
|---|---|---|---|
| findingId | string | – | A specific finding fingerprint to fix. Omit for all findings. |
| path | string | – | Local mode only: directory to scan. Omit to scan the directory this server was launched in. Use it to narrow a large repository. |
| repo | string | – | Cloud mode only: repository full_name (owner/repo). Omit for the latest scanned repo. |
| severity | string | – | Filter to one severity. |
No output schema declared.
No examples provided.
get_security_summary ~45
Get the user's overall security posture: counts by severity, last scan time, and number of monitored repos. Use this when the user wants a high-level overview of their security health.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
health_check ~35
Verify connectivity and authentication with the SPHIOR CODE API. Returns service version and current security summary. Use this to debug connection issues.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_findings ~113
List security vulnerabilities (SAST + SCA) detected by SPHIOR CODE across the user's GitHub repositories. Use this when the user asks about security issues, vulnerabilities, or CVEs in their code. Returns up to 100 findings ordered by detection date (newest first).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max number of results (1-100). Default: 20 |
| severity | string | – | Filter by severity level |
| status | string | – | Filter by triage status. Default: open |
No output schema declared.
No examples provided.
mark_false_positive ~66
Mark a finding as a false positive (the reported vulnerability is not actually exploitable). Use this when the AI's detection is incorrect for a specific code context.
| Name | Type | Req | Description |
|---|---|---|---|
| findingId | string | yes | Finding UUID |
| reason | string | – | Optional reason why this is a false positive |
No output schema declared.
No examples provided.
resolve_finding ~66
Mark a finding as resolved (e.g., after applying a fix). Use only when the vulnerability has actually been remediated. For false positives, use mark_false_positive instead.
| Name | Type | Req | Description |
|---|---|---|---|
| findingId | string | yes | Finding UUID |
| reason | string | – | Optional reason for closing |
No output schema declared.
No examples provided.
verify_evidence ~95
Independently verify SPHIOR's tamper-evident code evidence chain (Merkle root + hash-chain + commit anchor). Confirms the deterministic scan records were not altered — for auditors. No source code is returned.
| Name | Type | Req | Description |
|---|---|---|---|
| includePack | boolean | – | Include the independently-verifiable evidence pack (records + SHA-256 manifest). |
| repo | string | – | Filter to one repository (full_name). Omit for all. |
No output schema declared.
No examples provided.
How do I install the io.github.Toraastrta/sphior-code-mcp server?
io.github.Toraastrta/sphior-code-mcp runs locally as an npm package, launched with npx -y sphior-code-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · sphior-code-mcp
claude mcp add toraastrta-sphior-code-mcp -- npx -y sphior-code-mcp
What is the io.github.Toraastrta/sphior-code-mcp server?
io.github.Toraastrta/sphior-code-mcp is listed in the public MCP registry as io.github.Toraastrta/sphior-code-mcp. Deterministic SAST/SCA findings + fix guidance for your AI agent. Runs locally, no account needed. This page covers its npm package (sphior-code-mcp).
Is the io.github.Toraastrta/sphior-code-mcp server safe to use?
io.github.Toraastrta/sphior-code-mcp scores 75 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.Toraastrta/sphior-code-mcp server expose?
io.github.Toraastrta/sphior-code-mcp exposes 8 tools: list_findings, get_finding, get_security_summary, resolve_finding, mark_false_positive, and 3 more. Their descriptions and schemas cost roughly 710 tokens of context every time the server is loaded.
Is the io.github.Toraastrta/sphior-code-mcp server still maintained?
io.github.Toraastrta/sphior-code-mcp 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 io.github.Toraastrta/sphior-code-mcp server under?
io.github.Toraastrta/sphior-code-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.