Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Procm

NPM · PROCM-MCP · SCANNED SEP 22

A Model Context Protocol (MCP) server for process management.

Available components

npm · procm-mcp 86
+1 this week 86 Trust /100
Trust breakdown (7 categories)

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 35 of 101 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to coder-ka/procm-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 113 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability51
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 331 tokens (~30/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete-allowed-process" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 11 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
Install

How do I install the Procm MCP server?

Procm runs locally as an npm package, launched with npx -y procm-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 · procm-mcp

# add to Claude Code
claude mcp add coder-ka-procm-mcp -- npx -y procm-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "coder-ka-procm-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "procm-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "coder-ka-procm-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "procm-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add coder-ka-procm-mcp -- npx -y procm-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "coder-ka-procm-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "procm-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add coder-ka-procm-mcp --command npx --arg -y --arg procm-mcp
# ~/.hermes/config.yaml
mcp_servers:
  coder-ka-procm-mcp:
    command: "npx"
    args: ["-y", "procm-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "coder-ka-procm-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "procm-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add coder-ka-procm-mcp -t stdio -c npx -a -y procm-mcp
// mcp.json
{
  "mcpServers": {
    "coder-ka-procm-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "procm-mcp"
      ]
    }
  }
}
Changelog

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.

  • 22 Sept 26 +1
    • Stability: 0.97 → pass security
  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −3
    • Security disclosure: unverified → fail ▼ functional
    • Stability: pass → 0.83 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified ▼ functional
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −3
    • Stability: pass → 0.77 functional
Diagnostics

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 22 Sept 2026 · Analysed npm/procm-mcp@0.0.43

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo coder-ka/procm-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/coder-ka/procm-mcp/.github/workflows/publish.yml@refs/heads/main
Rekor log index 1681587535
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:8dbe8e98a467734327bbde959df0834b06bc42640575c3d320817c7c7f121a632e2c456aa23054e7490cb7a01dafe22298d3df596d59f27638fffe00a

Background: How many MCP packages publish verified provenance →

Dependencies 101 packages
Packages resolved 101
Stale 35
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~331 tokens

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 →

Tool Tokens
allow-start-process ~34

Allow process creation

NameTypeReqDescription
argsarray––
cwdstring––
scriptstringyes–

No output schema declared.

No examples provided.

delete-allowed-process ~36

Delete an allowed process

NameTypeReqDescription
argsarray––
cwdstring––
scriptstringyes–

No output schema declared.

No examples provided.

delete-process ~21

Delete a process by ID

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get-process-info ~24

Get information about a process by ID

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get-process-stderr ~34

Get the stderr of a process by ID

NameTypeReqDescription
chunkCountnumber––
idstringyes–

No output schema declared.

No examples provided.

get-process-stdout ~34

Get the stdout of a process by ID

NameTypeReqDescription
chunkCountnumber––
idstringyes–

No output schema declared.

No examples provided.

get-server-id ~13

Get server id

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list-allowed-processes-in-cwd ~29

List allowed processes in current working directory

NameTypeReqDescription
cwdstring––

No output schema declared.

No examples provided.

list-processes ~14

List all running processes

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

restart-process ~21

Restart a process by ID

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

start-process ~71

Start a new process. Warning: Do not invoke background processes that will not exit automatically, and stdout/stderr will not be captured.

NameTypeReqDescription
argsarray––
cwdstringyes–
envsobject––
namestring––
scriptstringyes–

No output schema declared.

No examples provided.

Common questions

What is the Procm MCP server?

Procm is an MCP server listed in the public MCP registry as io.github.coder-ka/procm-mcp. A Model Context Protocol (MCP) server for process management. This page covers its npm package (procm-mcp).

Is the Procm MCP server safe to use?

Procm scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Procm MCP server expose?

Procm exposes 11 tools: get-server-id, allow-start-process, list-allowed-processes-in-cwd, delete-allowed-process, start-process, and 6 more. Their descriptions and schemas cost roughly 331 tokens of context every time the server is loaded.

Is the Procm MCP server still maintained?

Procm is still listed as active in the MCP registry. We last reached this channel on 22 September 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 Procm MCP server under?

Procm declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.