Skip to main content
Glama
LuminariSoftwares

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.
      219
      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.
      Apache 2.0

    • homelab-mcp

      VedantDesai11
      A
      license
      Not graded
      quality
      C
      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

    B3.4/5.0

    Scored across 3 tools

    Disambiguation4/5

    stack_health and stack_snapshot are clearly distinct (graded findings vs raw data), but stack_health and explain overlap because both mention 'what to try.' An agent could reasonably confuse them when seeking details about a specific finding, though descriptions provide some guidance.

    Naming Consistency3/5

    Two tools follow a stack_<noun> pattern while explain is a bare verb, mixing noun-phrase and verb naming conventions. The names are readable and snake_case throughout, but the inconsistent pattern prevents a higher score.

    Tool Count4/5

    Three tools is on the low end but appropriate for a focused diagnostics server: one to report health, one to expose raw evidence, and one to explain codes. Each earns its place, though the surface is lean.

    Completeness4/5

    The core diagnostic loop is covered: health findings, raw snapshot evidence, and code explanations. Minor gaps exist around historical trends and remediation actions, but agents can work around these for a read-only guardian.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources