io.github.runsec-io/mcp

MCPcommunity
v1.0.127io.github.runsec-ioUnknownUpdated 4mo agonpm

RunSec MCP server for workspace security scanning and remediation workflows.

AI-powered MCP server for secure coding — zero noise, instant proof. RunSec connects your IDE or CI agent to local-first security analysis: deterministic rules, cognitive filtering, and evidence-backed findings you can verify in seconds. Run via (recommended for Cursor, VS Code, Windsurf, and Claude Desktop): Get an API key from RunSec Hub under API Keys, then wire the server in your editor MCP…

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 →
4mo agoLast update
Package
Authorio.github.runsec-io
LicenseUnknown
Version1.0.127
Sourcemcp-registry
npm@runsec/mcp
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 surface—
Security scan✓ Cleanv1.0.127 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

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

Tools

No tool declarations found in the source3mo ago

Forge read 3 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

AI-powered MCP server for secure coding — zero noise, instant proof. RunSec connects your IDE or CI agent to local-first security analysis: deterministic rules, cognitive filtering, and evidence-backed findings you can verify in seconds. Run via (recommended for Cursor, VS Code, Windsurf, and Claude Desktop): Get an API key from RunSec Hub under API Keys, then wire the server in your editor MCP config: Website: IDE setup guide: Trust center: Runs security scans locally in your workspace (source…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

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