io.github.mswdev/better-unraid-mcp

Better Unraid MCP

Is the Better Unraid MCP server down? It gave no valid answer in the probe of 2026-11-13: crashed on start. One failed probe is not an outage.

Monitor and manage an Unraid server from any MCP client: array, Docker, VMs, ZFS, logs, and UPS.

crashed on start no valid answer since 2026-11-13 · probed 2026-11-14 · unchanged since 2026-11-13

MCP error -32000: Connection closed
    at file:///work/node_modules/better-unraid-mcp/dist/index.js:8107:1
    at ModuleJob.run (node:internal/modules/esm/modu

Run it: npx -y better-unraid-mcp@0.1.1 (stdio, probed in a container with the network off)
Host: npmjs.com
Repository: https://github.com/mswdev/better-unraid-mcp
Website: https://github.com/mswdev/better-unraid-mcp#readme
Registry: active, updated 2026-11-12 · registry entry

Compare this server with others.

More servers

Other registry entries on npmjs.com, the ones next to this name; all of them.

ConnectWise PSA io.github.mspstack/mcp-connectwise-psa · crashed on start
IT Glue io.github.mspstack/mcp-itglue · needs env
Microsoft Planner io.github.mspstack/mcp-planner · alive
io.github.mstang/casemgr-mcp · needs network
io.github.mtbun/storeshots-mcp · alive
io.github.mtjandra/mcp-weather-server · alive
The High Council io.github.muad-yasin/the-high-council · needs env
io.github.muba00/gitstandup · alive

Servers that mention better.

BetterPost ai.betterpost/server · alive
TheBetterHire ai.thebetterhire/mcp · needs auth
BetterChess co.betterchess/betterchess · alive
Beamtrace com.beamtrace/mcp · needs auth
com.interzoid/mcp-server · alive
BetterStack Status Page Scraper & API Tool com.ranovam/betterstack-scraper · needs auth
MakeMeBetter AI com.rohithmariyala/makemebetter-ai · needs auth
Octopus com.tryoctopus/octopus · alive

Badge for the README

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher

The package did not start as an MCP server at its probe on 2026-11-13. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
The process exited on start before it answered initialize. The error output is above.