Skip to main content
Glama
Enrique-S-J

sysops-mcp

by Enrique-S-J
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to sysops-mcp

No user-submitted related servers found.

    Related Servers

    • system-monitor

      2428424081cn
      F
      license
      A
      quality
      C
      maintenance
      A secure, read-only MCP server for AI-powered system monitoring. It provides real-time OS metrics, config discovery, and safe log tailing to enable autonomous infrastructure audits without shell access risks.
      4
      1
      -

    • GhostInTheShell MCP

      pronzzz
      A
      license
      Not graded
      quality
      D
      maintenance
      A sandboxed, read-only MCP server that safely exposes system metrics, container diagnostics, and logs to AI agents with intelligent context compression and strict security measures.
      MIT

    • DivLens MCP

      Lohithry
      F
      license
      Not graded
      quality
      C
      maintenance
      A 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
      -

    • DeskSense

      ChituQAQ
      A
      license
      Not graded
      quality
      A
      maintenance
      A read-only Windows MCP server that gives AI assistants awareness of the current PC state, including open applications, focus, idle status, and system metrics.
      MIT

    • local-tools-mcp-server

      fenhuayue
      F
      license
      A
      quality
      C
      maintenance
      A read-only MCP server that enables AI assistants to search files, list directories, retrieve system info, and get file metadata on the local file system.
      4
      -
    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.4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource and action: CPU, memory, disk, processes, network, port probes, host summary, and logs. Even the aggregate get_host_summary is positioned as a high-level entry point rather than overlapping with the individual status tools.

    Naming Consistency5/5

    Tool names consistently follow a verb_noun pattern in snake_case: get_cpu_status, get_memory_status, get_network_status, check_port, tail_log. Minor verb variation (get vs list vs check vs tail) is still predictable and clearly mapped to each tool's function.

    Tool Count5/5

    Eight tools is a well-scoped size for a sysadmin/health-check server. Each tool covers a meaningful monitoring area without redundancy or feature bloat.

    Completeness4/5

    The toolkit covers the core read-only sysadmin surface well: CPU, memory, disk, processes, network, port reachability, host summary, and log inspection. It lacks deeper per-process detail or broader log discovery, but the provided workflows are practical and cover most common health-check scenarios without dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources