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

What's Running

NPM · WHATS-RUNNING-MCP · SCANNED AUG 3

Live OS ground truth for agents: running agent sessions, listening ports, daemons, system load.

Available components

66 Trust /100
Trust breakdown (6 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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 255 tokens (~51/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · whats-running-mcp

# add to Claude Code
claude mcp add stcmain-whats-running-mcp -- npx -y whats-running-mcp
# add to Codex CLI
codex mcp add stcmain-whats-running-mcp -- npx -y whats-running-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "stcmain-whats-running-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "whats-running-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add stcmain-whats-running-mcp --command npx --arg -y --arg whats-running-mcp
# ~/.hermes/config.yaml
mcp_servers:
  stcmain-whats-running-mcp:
    command: "npx"
    args: ["-y", "whats-running-mcp"]
// mcp.json
{
  "mcpServers": {
    "stcmain-whats-running-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "whats-running-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.

  • 2 Aug 26 +61
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Tool coverage: unverified → 100 functional
    • First check of Schema quality: excellent functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: unverified functional
    • First check of Tool coverage: 100 functional
    • Licence: MIT functional
  • 1 Aug 26 5

    First indexed and scored.

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 5 exposed · ~255 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.

Tool Tokens
agent_sessions ~89

List AI-agent processes actually running right now (Claude Code, Codex, Aider, ...). Separates terminal-attached sessions (a human can see them) from detached/orphan ones. Reads ps/lsof directly — never transcripts or docs. Patterns configurable via WR_AGENT_PATTERNS.

NameTypeReqDescription
include_detachedbooleanAlso list background/orphan agent processes with no terminal (default true)

No output schema declared.

No examples provided.

daemons ~56

Persistent services actually loaded right now: launchctl (macOS, non-Apple) or systemd user services (Linux). Optional case-insensitive substring filter on the label.

NameTypeReqDescription
filterstringSubstring filter on service label

No output schema declared.

No examples provided.

listening_ports ~43

All TCP ports currently in LISTEN state with owning process and pid (lsof). The definitive answer to 'is service X actually up?' — nothing hidden, nothing assumed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

system_stats ~20

Load average, uptime, and root-disk free space.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

whats_running ~47

Full live snapshot in one call: agent sessions, TCP listeners, loaded daemons, system stats. Use at session start to ground yourself in what is ACTUALLY live instead of stale memory.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.