Skip to main content
Glama
Sign In
stack-guardian

stack-guardian

by LuminariSoftwares
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to stack-guardian

No user-submitted related servers found.

    Related Servers

    • HomeLab Monitor

      SikamikanikoBG
      A
      license
      Not graded
      quality
      A
      maintenance
      Plug-and-play homelab dashboard in one container — GPU, local-AI VRAM, Docker, systemd, host health. Built-in read-only MCP server so AI agents can explore it too.
      231
      MIT

    • homelab-mcp

      Chain-P
      A
      license
      A
      quality
      C
      maintenance
      Exposes a Raspberry Pi homelab's systemd service health, disk usage, CPU temperature, and LAN game-server status as read-only MCP tools, letting MCP clients answer questions like "how's the homelab doing?" without SSHing in manually.
      4
      MIT

    • Oraclarr

      bdog720
      A
      license
      Not graded
      quality
      B
      maintenance
      A locally-run, read-only MCP server that lets an LLM client diagnose a self-hosted *arr media stack by aggregating across Sonarr, Radarr, Prowlarr, qBittorrent, Tdarr, and Profilarr.
      224 PyPI
      Apache 2.0

    • homelab-mcp

      VedantDesai11
      A
      license
      Not graded
      quality
      D
      maintenance
      Lets MCP clients (Claude Code, Claude Desktop) inspect a Linux home server's health over the network: uptime, load, memory, disk, Docker containers, systemd services, journal errors, and listening ports. Read-only, bearer-token secured.
      MIT
    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.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool occupies a distinct layer of a diagnosis workflow: stack_health grades, stack_snapshot returns raw data, stack_explain decodes a specific code. The descriptions explicitly state when to use each and point at the alternatives, leaving almost no room for misselection.

    Naming Consistency5/5

    All three tools follow an identical `stack_<noun>` snake_case pattern with no stylistic deviation. The shared prefix also reinforces that the tools belong to one coherent family.

    Tool Count4/5

    Three tools is on the low end, but each covers a genuinely separate need (grade, raw evidence, code explanation) with no filler or overlap. The surface is intentionally narrow rather than arbitrarily thin, though a fourth operation (e.g. history or remediation) would round it out.

    Completeness4/5

    The read-only diagnostic lifecycle—detect (health), inspect (snapshot), interpret (explain)—is fully covered with no dead ends within that scope. Gaps are around acting on findings: no way to acknowledge, remediate, or compare against prior snapshots, so agents can diagnose but never resolve.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources