io.github.coder-ka/procm-mcp

MCPattested
v0.0.43io.github.coder-kaUnknownUpdated 4mo agonpmGitHub

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

A Model Context Protocol (MCP) server for process management. Secure and automatable process creation Cleanup created processes automatically on termination (e.g. exiting claude code) Common process management features supported, restarting, deleting, checking status or retreving stdout/stderr of processes Using these features, LLMs start processes like development servers, docker-compose, or…

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.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
5GitHub stars
1Forks
4mo agoLast update
Package
Authorio.github.coder-ka
LicenseUnknown
Version0.0.43
Sourcemcp-registry
npmprocm-mcp
GitHubcoder-ka/procm-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—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)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 15dcee3
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface11 tools · 2 privileged
Security scan✓ Cleanv0.0.43 · 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

11 tools · 2 privileged
Statically extracted from the published packagev0.0.43 · 3mo 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.

get-server-idNo description published

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

allow-start-processNo description published

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

list-allowed-processes-in-cwdNo description published

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

delete-allowed-processprivilegedNo description published

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

start-processNo description published

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

delete-processprivilegedNo description published

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

restart-processNo description published

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

get-process-infoNo description published

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

list-processesNo description published

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

get-process-stdoutNo description published

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

get-process-stderrNo description published

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

0 of 11 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

A Model Context Protocol (MCP) server for process management. Secure and automatable process creation Cleanup created processes automatically on termination (e.g. exiting claude code) Common process management features supported, restarting, deleting, checking status or retreving stdout/stderr of processes Using these features, LLMs start processes like development servers, docker-compose, or test watchers and check their outputs to fix bugs automatically. You can permit LLMs to use tool…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

11 tools · 2 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.