Skip to main content
Glama
alexcgodwin

OpsChugex LocalOps MCP

by alexcgodwin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to OpsChugex LocalOps MCP

No user-submitted related servers found.

    Related Servers

    • mcp-vpsobs

      0mandrock1
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only observability of a Linux host via MCP, exposing allowlisted systemd, docker, nginx, logs, disk, and cert info without shell access.
      MIT

    • corporate-mcp-system-inspector

      313ON
      F
      license
      A
      quality
      C
      maintenance
      Enables observation-only system inspection through MCP, exposing system identity, resources, process summary, and network summary without any mutation or command execution.
      4
      -

    • homelab-mcp

      lstkhN
      A
      license
      B
      quality
      C
      maintenance
      Enables stdio MCP clients to gather read-only diagnostics and incident evidence from Linux homelabs, including health, disks, services, Docker containers, logs, and confirmation-required remediation proposals.
      10
      MIT

    • 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
      -

    • System Explorer MCP

      techiebod
      A
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server for observing Linux hosts (systemd, ZFS, Docker, VMs, network, hardware, NixOS) as a graph of objects with provenance. Provides seven tools to list hosts, get status, collections, objects, evidence, lookup, and changes.
      1
      GPL 3.0
    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

    B3.4/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools target distinct resources or actions, but the system health area has some overlap: system_health summarizes CPU, memory, and disk while cpu_status, memory_status, and disk_status provide detailed views of the same domains. Descriptions help distinguish them, but an agent could still hesitate between a summary tool and a detail tool.

    Naming Consistency4/5

    All names use snake_case, which is consistent, but the conventions vary between noun phrases (system_info, cpu_status, network_interfaces) and verb-led names (list_processes, inspect_process, list_services). The pattern is readable but not uniform verb_noun throughout.

    Tool Count3/5

    23 tools sits in the 16-25 range that the rubric calls borderline heavy for a server's scope. While many tools serve distinct read-only inspection needs, several could be consolidated with the summary tools, making the surface feel somewhat expansive.

    Completeness4/5

    Coverage is broad for local read-only system inspection: hardware, OS, processes, services, software, users, security artifacts, startup, and scheduled tasks are all represented. Minor gaps exist, such as network connection/port inspection and event log access, but agents can work around most of these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources