github JavaScript not analyzable

stcmain/whats-running-mcp

github

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.

maintainer
stcmain
license
MIT
first seen
2026-08-01
last seen
2026-08-02
releases · 30d
0
short id
risk insufficient evidence

Insufficient evidence to grade. This server's source has not been statically analyzed, so a low grade would only mean "nothing found", not "nothing there". We don't show a reassuring grade we can't stand behind. Attested signals (CVEs, provenance) below still apply.

Once the source is analyzed (see the analysis flag in the header), a graded score appears here. How analysis works: methodology.

graded 7m ago · see ecosystem CVEs →

capability exposure grade factor +16
Inferred surface — each links to servers holding it:
vulnerabilities 0 CVEs

No known CVEs for this server.

tool safety 1 findings · grade factor +5
  1. medium purpose mismatch agent_sessions

    benign-looking name carries shell

embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/github:stcmain/whats-running-mcp/badge.svg)](https://mcpobservatory.com/servers/github:stcmain/whats-running-mcp/security)

Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of stcmain.