HomeLab Monitor
OCI · DOCKER.IO/SIKAMIKANIKO123/HOMELAB-MONITOR:0.14.2
Self-hosted homelab dashboard with a built-in read-only MCP server (hosts, Docker, GPU, services).
Available components
Last scanned (20 hours ago)
Scores higher than 91% of OCI servers
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 148 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 983 tokens (~65/item across 15 items; 12 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −1
- Stability: pass → 0.97 functional
- 25 Oct 26 +1
- Stability: 0.97 → pass security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed oci/docker.io/sikamikaniko123/homelab-monitor:0.14.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_ai_models ~82
AI model servers: which models are loaded, their VRAM use, and who is driving them (caller→server connection-seconds attribution over `range`, e.g. "6h", "24h", "7d"). Answers "why is the GPU pinned, and which service is calling it?".
| Name | Type | Req | Description |
|---|---|---|---|
| range | string | – | – |
No output schema declared.
No examples provided.
get_alerts ~34
Alias for `get_events` — the monitor's alerts are its edge-triggered events.
| Name | Type | Req | Description |
|---|---|---|---|
| range | string | – | – |
No output schema declared.
No examples provided.
get_containers ~58
Full Docker container list (Containers tab): per container name, image, state, health, exposed ports, RAM (`mem_bytes`), VRAM (`vram_bytes`), image disk and uptime — plus the summary counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_events ~48
Recent edge-triggered events over `range` (OOM kills, threshold crossings), each with a blame line where one can be attributed, plus derived insights.
| Name | Type | Req | Description |
|---|---|---|---|
| range | string | – | – |
No output schema declared.
No examples provided.
get_gpu ~70
GPU detail: current utilisation, VRAM used/total, power and temperature, plus per-model VRAM use and the caller→server attribution over `range`. Answers "why is the GPU pinned, and which service is calling the model server?".
| Name | Type | Req | Description |
|---|---|---|---|
| range | string | – | – |
No output schema declared.
No examples provided.
get_history ~54
Charted time-series the dashboard graphs over `range`: timestamps + aligned arrays for GPU util/VRAM/power/temp and host CPU/RAM/load/temp. Use for trends.
| Name | Type | Req | Description |
|---|---|---|---|
| range | string | – | – |
No output schema declared.
No examples provided.
get_host ~48
Full System / Network / Security inventory for a single host. `name` is the host's registered name, or "local" for the hub itself.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
get_memory ~70
RAM breakdown behind the memory treemap: per-service peak/avg/present RAM over `range`, the current RAM per process right now, kernel (non-reclaimable) memory, and totals. Answers "what is eating RAM on this hub?".
| Name | Type | Req | Description |
|---|---|---|---|
| range | string | – | – |
No output schema declared.
No examples provided.
get_services ~49
Full systemd unit list (Services tab): per unit active/sub state, description, listening ports, RAM, uptime, admin/watched flags and status verdict — plus the summary counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_snapshot ~59
Current live vitals across the hub: GPU, host RAM/CPU, Docker and systemd health summaries (with any problem containers / failed units), pending OS updates and whether a monitor update is available. DB-free and cheap.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_hosts ~67
List every host in the fleet with headline vitals (hub listed first). Returns the roster: name, online status, OS, CPU/RAM load, fullest disk and any OS-upgrade/reboot hint per host. Start here, then drill in with `get_host`.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan_disk ~109
WizTree-style nested folder-size treemap for a host path (Disks tab). Wraps the monitor's on-demand scan and polls until done. `path` is an absolute host path (e.g. "/", "/var"); set `rescan=True` to force a fresh scan. Returns total/free bytes and a nested `entries` tree of {name, path, bytes, children}.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | – |
| rescan | boolean | – | – |
No output schema declared.
No examples provided.
How do I install the HomeLab Monitor MCP server?
HomeLab Monitor runs locally as a container image, launched with docker run --rm -i -e HOMELAB_MONITOR_URL -e MCP_TRANSPORT docker.io/sikamikaniko123/homelab-monitor:0.14.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · docker.io/sikamikaniko123/homelab-monitor:0.14.2
claude mcp add sikamikanikobg-homelab-monitor -- docker run --rm -i -e HOMELAB_MONITOR_URL -e MCP_TRANSPORT docker.io/sikamikaniko123/homelab-monitor:0.14.2
This image reads HOMELAB_MONITOR_URL and MCP_TRANSPORT. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the HomeLab Monitor MCP server?
HomeLab Monitor is an MCP server listed in the public MCP registry as io.github.SikamikanikoBG/homelab-monitor. Self-hosted homelab dashboard with a built-in read-only MCP server (hosts, Docker, GPU, services). This page covers its container image (docker.io/sikamikaniko123/homelab-monitor:0.14.2).
Is the HomeLab Monitor MCP server safe to use?
HomeLab Monitor scores 54 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the HomeLab Monitor MCP server expose?
HomeLab Monitor exposes 12 tools: list_hosts, get_host, get_snapshot, get_containers, get_services, and 7 more. Their descriptions and schemas cost roughly 748 tokens of context every time the server is loaded.
Is the HomeLab Monitor MCP server still maintained?
HomeLab Monitor is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the HomeLab Monitor MCP server under?
HomeLab Monitor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.