sphior-code-mcp

MCPcommunity
v1.0.2io.github.ToraastrtaUnknownUpdated 1mo agonpmGitHub

Deterministic SAST/SCA findings + fix guidance for your GitHub repos, handed to your AI agent.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorio.github.Toraastrta
LicenseUnknown
Version1.0.2
Sourcenpm+mcp-registry
npmsphior-code-mcp
GitHubToraastrta/Sphior
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface9 tools · none privileged
Security scan✓ Cleanv1.0.2 · 14d agoHow well does this scan work?
EvalsNone
IndexedJul 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

9 tools · none privileged
Statically extracted from the published packagev1.0.2 · 14d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_findingsNo description published

This tool published no description. Forge does not invent one.

get_findingNo description published

This tool published no description. Forge does not invent one.

get_security_summaryNo description published

This tool published no description. Forge does not invent one.

get_fix_proposalNo description published

This tool published no description. Forge does not invent one.

resolve_findingNo description published

This tool published no description. Forge does not invent one.

mark_false_positiveNo description published

This tool published no description. Forge does not invent one.

health_checkNo description published

This tool published no description. Forge does not invent one.

get_fix_contextNo description published

This tool published no description. Forge does not invent one.

verify_evidenceNo description published

This tool published no description. Forge does not invent one.

0 of 9 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Deterministic SAST/SCA findings + fix guidance for your GitHub repos, handed to your AI agent.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

9 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.