Experimental package — This module provides a set of MCP tools to retrieve information from GitHub
Free
Nothing to run from here
Unraid Toolkit is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
Unraid toolkit umbrella — re-exports the SDK, CLI, and MCP server, and ships the `unraid` command.
Quickstart
# 1 — run it from where its publisher ships it
npx -y unraid-toolkit
# 2 — ask your agent something
> Unraid toolkit umbrella — re-exports the SDK, CLI, and MCP server, and ships the `unraid` command.
Unraid Toolkit is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
MIAll 1 server
mike-north1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Unraid Toolkit as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add unraid-toolkit-mcp -- npx -y unraid-toolkitReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
29 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get the storage array
Takes no parameters.
Example callreturns →
List past parity checks (date, duration, speed, error count, status). Newest entries first as returned by the server. Use limit/offset to page through a long history.
Takes no parameters.
Example callreturns →
Start or stop the storage array. Stopping the array takes all shares and Docker/VM services offline. Destructive — requires human approval.
Takes no parameters.
Example callreturns →
Add a disk to the array at an optional slot. Destructive — requires human approval.
Takes no parameters.
Example callreturns →
Remove a disk from the array. The array must be stopped first. Destructive — requires human approval.
Takes no parameters.
Example callreturns →
Mount a single array disk. Destructive — requires human approval.
Takes no parameters.
Example callreturns →
Unmount a single array disk. Destructive — requires human approval.
Takes no parameters.
Example callreturns →
Start a parity check. With correct=true it writes corrections to parity (a correcting check); correct=false runs a read-only check. Destructive (a correcting check writes to parity) and gated: requires human approval (elicitation or a confirmation token).
Takes no parameters.
Example callreturns →
Cancel a running parity check (discards its progress). Destructive and gated: requires human approval (elicitation or a confirmation token).
Takes no parameters.
Example callreturns →
Pause a running parity check. Reversible — resume it with unraid_parity_resume.
Takes no parameters.
Example callreturns →
Resume a paused parity check.
Takes no parameters.
Example callreturns →
List the physical disks attached to the server: device path, model/vendor, size (bytes), interface (SATA/SAS/NVMe/USB), SMART status, temperature, and spin state. Use limit/offset to page.
Takes no parameters.
Example callreturns →
List Docker containers with name, image, state (running/exited/paused), status text, autostart settings, update availability, and published ports. Use limit/offset to page.
Takes no parameters.
Example callreturns →
Get detailed information about a single Docker container by id, including image, command, sizes, network mode, ports, autostart, template path, and WebUI/support URLs. Fails with NOT_FOUND if no container has that id.
Takes no parameters.
Example callreturns →
Fetch recent log lines for a container. Use
Takes no parameters.
Example callreturns →
Report per-container update availability (UP_TO_DATE / UPDATE_AVAILABLE / REBUILD_READY / UNKNOWN). Use limit/offset to page.
Takes no parameters.
Example callreturns →
Update every Docker container that has an available image update. Returns the resulting state of each updated container.
Takes no parameters.
Example callreturns →
Remove a Docker container, optionally deleting its backing image (withImage). Irreversible and destructive — requires human approval.
Takes no parameters.
Example callreturns →
List notifications filtered by queue (
Takes no parameters.
Example callreturns →
Get unread and archived notification counts broken down by severity (info/warning/alert/total). A fast way to check whether the server needs attention.
Takes no parameters.
Example callreturns →
Create a notification on the server. Requires title, subject, description, and importance (INFO/WARNING/ALERT); link is optional.
Takes no parameters.
Example callreturns →
Archive a single notification by id (moves it out of the unread queue).
Takes no parameters.
Example callreturns →
Unarchive a single notification by id — marks it unread, moving it back to the unread queue.
Takes no parameters.
Example callreturns →
List Unraid user shares with capacity (free/used/total, in KB), included/excluded disks, cache setting, allocation policy, and comment. Use limit/offset to page.
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Get live system utilization: overall and per-core CPU load (percent), and memory usage (total/used/free/available and swap, in bytes plus percentages). This is a point-in-time snapshot. For static hardware/OS details use unraid_system_info.
Takes no parameters.
Example callreturns →
List connected UPS devices with battery telemetry (charge %, estimated runtime, health) and power telemetry (input/output voltage, load %, current/nominal watts). Use limit/offset if multiple UPS units are attached.
Takes no parameters.
Example callreturns →
List the virtual machines (libvirt domains) known to Unraid with their id, name, and current run state (RUNNING/SHUTOFF/PAUSED/...). Use limit/offset to page.
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Unraid Toolkit costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 100 / 100
Release 0.2.1 · scanned 26 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest7519f3cd865d05c3050f325544f9a117d5b661791fc9184bd0a40837acb23ae2
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest7519f3cd865d05c3
Scanned2026-08-26
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 0.2.1 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
0.2.1
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Unraid Toolkit in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.