Skip to main content
Glama
cooderamily

mcp-system-info

by cooderamily

Related Servers

Alternatives to mcp-system-info

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible clients to inspect the local machine's CPU, memory, and disk information through tools, a structured resource, and an upgrade-assessment prompt.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Linux system operations via MCP, including CPU, memory, processes, storage, filesystem, hardware, network, monitoring, and logs.
      9
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Hardware probe MCP server that provides deep hardware inventory and live sensor telemetry for AI agents, including CPU, memory, disk, GPU, and sensor data across platforms.
      6
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables comprehensive system monitoring and diagnostics through 18 tools that provide detailed information about CPU, memory, disk usage, network interfaces, running processes, battery status, hardware details, and temperature monitoring. Allows users to query system information and performance metrics through natural language interactions.
      17 npm
      ISC
    • F
      license
      B
      quality
      D
      maintenance
      A lightweight MCP server that provides real-time hardware statistics including CPU, memory, disk, and NVIDIA GPU usage. It enables users to monitor system performance and retrieve comprehensive host machine specifications through a standardized interface.
      1
      -
    • 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

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of system information: hardware details vs. dynamic system status. There is no overlap in purpose.

    Naming Consistency5/5

    Both tools follow a consistent 'get_<domain>' pattern, making the naming predictable and clear.

    Tool Count3/5

    With only 2 tools, the server feels minimal but not unreasonable for a focused purpose. However, the scope might benefit from a few more to cover software/process information.

    Completeness3/5

    The tools cover fundamental hardware and system status, but lack coverage of software inventory, running processes, or detailed storage analysis. The surface is functional but not comprehensive.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive