Skip to main content
Glama
stcmain

whats-running-mcp

by stcmain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to whats-running-mcp

No user-submitted related servers found.

    Related Servers

    • cloud-ops-mcp

      jitendrakumar-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents and assistants to inspect live system telemetry, check TCP port connectivity, audit environment variables for leaked secrets, analyze and summarize log files, and list Docker containers — all with token-efficient, compressed output.
      1
      MIT

    • SysFlow MCP

      johannschiffer
      A
      license
      A
      quality
      A
      maintenance
      Gives AI agents safe, bounded, non-blocking access to Linux sysadmin inspection tasks, including CPU, RAM and disk healthchecks, memory-safe log tailing with regex filtering, and user-level systemd service and timer auditing. All operations run without sudo or unrestricted root shells, avoiding interactive pager hangs and context window flooding.
      4
      MIT

    • runtime-mcp-server

      becketthayes
      F
      license
      A
      quality
      B
      maintenance
      Provides AI coding agents with real-time visibility into local development runtime state, enabling them to tail application logs, inspect ports, monitor process metrics, and diagnose network errors.
      1
      -

    • Enterprise Infrastructure &

      Maneesh-Rajbhar
      A
      license
      A
      quality
      C
      maintenance
      Provides read-only access to host system metrics (CPU, memory, disk), Docker container health/logs, and sandboxed log file analysis via MCP tools, enabling AI agents to monitor enterprise infrastructure safely.
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of system state: daemons for persistent services, system_stats for machine health, listening_ports for network listeners, and agent_sessions for AI processes. The aggregate tool whats_running is explicitly designed to combine these, so there is no ambiguity between specific tools.

    Naming Consistency4/5

    All tool names use lowercase snake_case and are noun phrases describing their data (daemons, system_stats, listening_ports, agent_sessions). The one outlier is whats_running, which is a phrase rather than a simple noun, but it still follows the same formatting and is easily distinguishable.

    Tool Count5/5

    With five tools, the server is well-scoped for its monitoring purpose. Each tool covers a specific area, and the aggregate whats_running tool adds value by providing a single-call snapshot without bloating the count.

    Completeness4/5

    The server covers the key areas of system state: daemons, system stats, listening ports, and AI agent sessions, with a combined snapshot. Minor gaps exist, such as a general process list or memory usage details, but these are not core to the defined scope and can be worked around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources