Is io.github.SikamikanikoBG/homelab-monitor safe to use?

io.github.SikamikanikoBG/homelab-monitor has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.SikamikanikoBG/homelab-monitor?

io.github.SikamikanikoBG/homelab-monitor can be installed by cloning its GitHub repository and following the setup instructions in the README.

What AI clients work with io.github.SikamikanikoBG/homelab-monitor?

io.github.SikamikanikoBG/homelab-monitor is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

io.github.SikamikanikoBG/homelab-monitor

Self-hosted homelab dashboard with a built-in read-only MCP server (hosts, Docker, GPU, services).

GitHub

No known CVEs

No license

Maintenance unknown

No commit data

Works with most clients

Transport: stdio

0 tools

Grade F

Edit this pageView history

Developer Tools

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-sikamikanikobg-homelab-monitor": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-sikamikanikobg-homelab-monitor)](https://mcppedia.org/s/io-github-sikamikanikobg-homelab-monitor)

Read me

What io.github.SikamikanikoBG/homelab-monitor does

Self-hosted homelab dashboard with a built-in read-only MCP server (hosts, Docker, GPU, services).

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

21/100across 5 weighted dimensions

How we score →

0255075100

−79

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Help improve this page

This server is missing a description. Tools and install config are also missing.If you've used it, help the community.

Add information

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.SikamikanikoBG/homelab-monitor safe to use?: io.github.SikamikanikoBG/homelab-monitor has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.SikamikanikoBG/homelab-monitor?: io.github.SikamikanikoBG/homelab-monitor can be installed by cloning its GitHub repository and following the setup instructions in the README.
What AI clients work with io.github.SikamikanikoBG/homelab-monitor?: io.github.SikamikanikoBG/homelab-monitor is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Similar servers

Others in developer-tools

View all →

Supabase MCP Server97

Manage Supabase projects — databases, auth, storage, and edge functions

2.7k 4

XcodeBuildMCP97

XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.

5.9k 1

XcodeBuildMCP97

A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.

5.9k 2

Mcp_agent_mail96

Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite

2.0k 6

MCP Security Weekly

Get CVE alerts and security updates for io.github.SikamikanikoBG/homelab-monitor and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Developer Tools

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-sikamikanikobg-homelab-monitor": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-sikamikanikobg-homelab-monitor)](https://mcppedia.org/s/io-github-sikamikanikobg-homelab-monitor)

Read me

What io.github.SikamikanikoBG/homelab-monitor does

Self-hosted homelab dashboard with a built-in read-only MCP server (hosts, Docker, GPU, services).

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

README

🛰️ HomeLab Monitor

One page for your whole home lab & AI rig — GPU, containers, services, disks. No agents, no Prometheus/Grafana, no cloud.

Your home lab grew into a couple of machines, a Pi, and a GPU that's mysteriously always busy. HomeLab Monitor gives you one self-hosted page that answers the real questions: which model is holding the GPU, which container is eating RAM, what's filling your disks, and is anything down — across every box over SSH: Linux, a Pi, even Windows. Readable from your phone over the VPN.

Get started

# Grab the compose file and go. No GPU required — the GPU panels just light up when one's present.
curl -fsSLO https://raw.githubusercontent.com/SikamikanikoBG/homelab-monitor/main/docker-compose.yml
docker compose up -d

Open http://<your-host>:9800 and you're done. Full options (from source, GPU toolkit, Windows/WSL2) → Install docs.

🆕 v0.14.0 — a built-in read-only MCP server: connect Claude (or any MCP client) to your homelab and explore it with full dashboard parity, no extra container. Release notes · changelog · MCP docs.

What you get

GPU, demystified — live VRAM/util/power/temp, and which container is holding the card (auto-mapped).
Containers, honestly — health plus RAM and VRAM in separate columns (real resident RAM, not page cache).
systemd services — local or remote, your own units highlighted, failures first.
WizTree-style disk treemaps — scan a filesystem, drill into folders, find the space hogs.
Multi-machine over SSH — paste one key per box; Linux, a Pi, even Windows. No agents, no installs.
Push alerts — Discord and ntfy.sh, edge-triggered so they don't spam.

Full tab-by-tab tour → Features.

Multi-machine, in two sentences

Open the Hosts tab, paste the hub's auto-generated SSH key onto each remote, and the hub starts polling it — no agents, just SSH + Python 3 (PowerShell on Windows). The hub pipes a small self-contained probe over SSH; nothing persists on the remote.

Onboarding, Windows setup, and the security model → Multi-machine docs.

Configuration

Set these under environment: in docker-compose.yml (all optional):

Variable	Default	Meaning
`SAMPLE_INTERVAL`	`10`	Seconds between samples
`RETENTION_DAYS`	`180`	How long history is kept
`PRESSURE_FREE_MB`	`2048`	Free VRAM below this counts as "pressure"
`PORT`	`9800`	Dashboard port
`MCP_PORT`	`9810`	Port for the built-in read-only MCP server
`ENABLE_MCP`	`1`	Set `0` to run the dashboard without the MCP server
`WATCH_CONTAINERS`	—	Extra containers to scan for OOM (comma-separated)
`WATCH_SERVICES`	—	systemd units to always show, even vendor ones (comma-separated)
`CHECK_UPDATES`	`true`

... View full README on GitHub

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

21/100across 5 weighted dimensions

How we score →

0255075100

−79

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Help improve this page

This server is missing a description. Tools and install config are also missing.If you've used it, help the community.

Add information

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.SikamikanikoBG/homelab-monitor safe to use?: io.github.SikamikanikoBG/homelab-monitor has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.SikamikanikoBG/homelab-monitor?: io.github.SikamikanikoBG/homelab-monitor can be installed by cloning its GitHub repository and following the setup instructions in the README.
What AI clients work with io.github.SikamikanikoBG/homelab-monitor?: io.github.SikamikanikoBG/homelab-monitor is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.