Skip to main content
Glama
313ON

corporate-mcp-system-inspector

by 313ON
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to corporate-mcp-system-inspector

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

    • mcpnertes

      thev1ndu
      A
      license
      A
      quality
      C
      maintenance
      Enables read-only Kubernetes cluster inspection through MCP, with namespace allow/deny and resource block policies enforced before any API call.
      11
      Apache 2.0

    • 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

    • openEuler MCP Toolkit

      xTey-wu
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP-capable LLM clients to perform read-only Linux system observation and OS algorithm experiments by exposing typed tools for memory, filesystem, process, and CPU scheduling data with controlled, safe boundaries.
      12
      MIT

    • remote-observer-mcp

      marutyan
      F
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server for observing registered local and SSH hosts, providing system, service, container, Git, and GPU status/log inspection through a closed-world registry without arbitrary shell access.
      -

    • branchlift

      MuratKomurcu1
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables local MCP access to attach to isolated backend environments, monitor runtime health/logs, check security posture, manage snapshots and diffs, audit events, and view sanitized remote inventory.
      6 npm
      1
      Apache 2.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

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a clearly separate subsystem: identity, resources, processes, and network. There is no functional overlap or ambiguity between the tool names and their stated purposes.

    Naming Consistency4/5

    Tool names follow a readable noun-based pattern, with system_ prefix used for two tools and _summary suffix used for the other two. While not perfectly uniform, the naming is predictable and easy to reason about.

    Tool Count5/5

    Four tools is a well-scoped count for a system inspection server. Each tool covers a distinct high-level concern without unnecessary fragmentation or redundancy.

    Completeness4/5

    The surface covers the core system inspection areas: identity, resources, processes, and network. Minor gaps such as detailed disk I/O or user/session information exist, but they are not essential for basic system inspection.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources