F
licenseNot graded
qualityD
maintenanceGives AI agents real-time access to system metrics, process management, and container orchestration.
-
whats-running-mcp
by stcmain
Related Servers
Alternatives to whats-running-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables LLMs to monitor system health, manage processes, execute shell commands, and inspect environment variables and directories.1MIT
- FlicenseAqualityBmaintenanceProvides 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-
- AlicenseAqualityCmaintenanceProvides 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.3MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI to monitor and analyze local system processes through custom tools. Provides real-time access to process information including CPU usage, memory consumption, process counts, and process searching capabilities.-
- FlicenseNot gradedqualityCmaintenanceA real-time system diagnostics MCP server that gives AI agents live access to CPU, RAM, disk, network, processes, and hardware health metrics, with zero cloud dependency.7-
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
ActivitySlowing
ResponsivenessNo issues