MCP.Market

Stack Guardian MCP server

by LuminariSoftwares·io.github.LuminariSoftwares/stack-guardian·v0.4.0

Health doctor for a home AI stack: Ollama nodes, GPUs and tailnet, with graded confidence.

B82/100grade B
What users say
No reviews yet
Be the first
Safety scan
B82/100

not scanned yet

Adoption
Growing

0 stars146 downloads/wk

Reviews

Write one

Nobody has reviewed Stack Guardian yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Stack Guardian tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Stack Guardian compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 63% of 48,255 servers
Downloads a week
146
more than 70% of 12,191 servers with a package

Release history: 3 versions in the registry since 2026-10-15, latest 2026-10-24, typically one every 7 days.

Install Stack Guardian in Claude Code, Cursor or VS Code

claude mcp add stack-guardian -- uvx stack-guardian
Add to Cursor

What the publisher says

From the Stack Guardian repository's README, as published. We do not edit it. Read it on GitHub

stack-guardian

mcp-name: io.github.LuminariSoftwares/stack-guardian

A health doctor for a home AI stack. It collects a snapshot of your nodes (Ollama endpoints, loaded models, NVIDIA GPUs, tailnet peers), runs small Python rules against it, remembers the last runs, and reports findings with a confidence grade: one sample is at most LIKELY, the same finding twice in a row is VERIFIED. A finding can carry a typed fix that you run on purpose, never automatically.

Status: 0.1.0, first release. Standard library only, Python 3.11+.

Install

pip install stack-guardian

This gives you three commands: stack-guardian (the CLI), stack-guardian-serve and stack-guardian-mcp.

Try it offline first: the example snapshot makes every shipped rule fire once.

curl -LO https://raw.githubusercontent.com/LuminariSoftwares/stack-guardian/main/examples/snapshot.json
curl -LO https://raw.githubusercontent.com/LuminariSoftwares/stack-guardian/main/examples/ctx.json
stack-guardian doctor --snapshot snapshot.json --ctx ctx.json

From a clone instead (for writing rules or running the tests):

git clone https://github.com/LuminariSoftwares/stack-guardian.git
cd stack-guardian
python -m venv .venv
.venv\Scripts\activate          # Windows;  macOS/Linux: source .venv/bin/activate
pip install -e .
stack-guardian doctor --snapshot examples/snapshot.json --ctx examples/ctx.json

For coding agents

stackhealth, stacksnapshot and explain. In Claude Code:

  • MCP server (any MCP client): stack-guardian-mcp speaks MCP over stdio with three read-only tools,
claude mcp add stack-guardian -e STACK_GUARDIAN_NODES=/path/to/nodes.json -- stack-guardian-mcp

Other clients: command stack-guardian-mcp, args ["--nodes", "/path/to/nodes.json"]. stack_health grades against the saved run history without adding to it, and reuses one snapshot for 10 s (--ttl SECONDS).

WARN or FAIL, and nothing otherwise. It runs stack-guardian doctor --json --quiet, so set STACKGUARDIANNODES to your nodes file in the harness environment.

  • DSH plugin (npm install dsh-stack-guardian, source in dsh/, Node 20+): adds one line at the start of a DeepSeek Harness session when the doctor reports

state (new, resolved, severity change), so an agent can tail it; stack-guardian-serve --nodes FILE also answers GET /metrics in Prometheus text format.

  • Watching and scraping: stack-guardian doctor --watch 30 --json prints one JSON object per finding that changes

What it does

1. doctor - run the checks

Describe your nodes in a JSON file (see examples/nodes.json) and check them live:

stack-guardian doctor --nodes examples/nodes.json --ctx examples/ctx.json

With neither --snapshot nor --nodes, doctor reads the nodes file named by $STACKGUARDIANNODES.

Options: --checks-dir DIR (your own rules, default is the shipped checks.d), --ctx FILE (rule settings such as the model each node is expected to hold), --state FILE (default $STACKGUARDIANSTATE or ~/.stack-guardian/state.json), --json, --quiet (print nothing when all is OK).

Exit codes: 0 all OK/INFO, 1 a WARN, 2 a FAIL, 3 usage, 4 the doctor itself crashed.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Stack Guardian: common questions

Is Stack Guardian MCP server safe?
Mostly: it is graded B (82/100). Read the Stack Guardian safety report
How do I install Stack Guardian?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Stack Guardian need an API key?
No secret keys are declared. It reads 1 setting from the environment.
Is Stack Guardian maintained?
The last commit was 20 days ago (2026-10-15). The latest release is v0.4.0.
How does Stack Guardian compare with other MCP servers?
safety score 82/100 (higher than 63% of 48,255 servers); downloads a week 146 (more than 70% of 12,191 servers with a package). Full comparison.

More from LuminariSoftwares →