github JavaScript not analyzable

stcmain/whats-running-mcp

not analyzable — no source code found to analyze

MCP server exposing live machine ground-truth (processes, listening ports, daemons, load) to agent fleets — stop guessing what's actually running.

Drift inferred · capture-to-capture

No drift recorded — single capability capture; advisories appear once its surface changes.

capabilities 5 tools

transport stdio counts 5 tools · 0 res · 0 prompts permission surface via README inference

agent_sessions

Which agent processes are live? Terminal-attached vs detached/orphan, with pid, uptime, and working directory
daemons

What persistent services are loaded? launchctl (macOS, non-Apple) or systemd user services (Linux), with optional label filter
listening_ports

Is service X actually up? Every TCP LISTEN socket with owning process
system_stats

Load average, uptime, root-disk free space
whats_running

Full snapshot in one call — use at session start

code evidence — · github-tarball

evidence-backed findings quoted directly from the published source artifact — not inferred

last analysis: no-source

No code evidence — the analyzed source reached for no tracked permissions, tools, or hooks.