Mcp Process

io.github.Digital-DefiancePublished by GitHub account Digital-Defiancev0.1.1Updated Oct 24, 2026

Process management and monitoring for AI agents with strict security boundaries

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Lets an AI assistant manage and monitor local processes on the user's machine within strict security boundaries.

What you can do
This MCP server provides process management and monitoring capabilities for AI agents, running as a local process over stdio. It is described as enforcing strict security boundaries around the process operations it exposes. The manifest does not list individual tools, so the exact commands available are not documented here.
When to use it
Consider it when an assistant needs to start, inspect, or monitor processes on a local desktop machine and you want those operations constrained by explicit security limits. It is a desktop-only tool, so it is not suited to remote or web-hosted use.
Requirements
Runs locally as a stdio process, installed from the npm package @ai-capabilities-suite/mcp-process, so Node.js and npm are needed. Desktop only; no web execution. No authentication, environment variables, or headers are declared.
Before you install
It manages processes on the local machine, so actions may start, stop, or alter running programs; the description claims strict security boundaries but no tool list is published, so review the actual permissions before installing. No credentials are requested in the manifest.

Installation

In SourceWeft

  1. Open Mcp Process 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.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

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

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

35% 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