Runsec Io

io.github.runsec-ioPublished by GitHub account runsec-iov1.0.127Updated Oct 24, 2026

RunSec MCP server for workspace security scanning and remediation workflows.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Lets an assistant run workspace security scans and support remediation workflows.

What you can do
This is a local MCP server that runs over stdio and covers workspace security scanning and remediation workflows. The supplied description only states that purpose; it does not list the available tools or operations.
When to use it
Consider it when you want an assistant to help check workspace security and handle remediation as part of a development workflow. It is not necessary if you only need general coding assistance.
Requirements
Runs as a local process on a desktop machine, started from the npm package @runsec/mcp over stdio, so it needs a Node.js environment. No environment variables, headers, or authentication are declared.
Before you install
The input does not say which credentials or secrets it asks for, nor whether it modifies, writes, or deletes files. Because it involves scanning and remediation, confirm the scope and permissions of any remediation actions before installing, and check whether scan results are sent to third parties.

Installation

In SourceWeft

  1. Open Runsec Io in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.127LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.