Homelab (tmhs) MCP Server

@tmhs/homelab-mcp npm v0.10.0 Source verified

Published by tmhsdigital — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server for home lab operations via SSH - 50 tools for system status, Docker Compose management, service health, monitoring, DNS, reverse proxy, networking, backups, disaster recovery, security auditing, logs, notifications, OS management, certificates

Trust grade
A
100/100
Last scanned get badge →
Trust
A · 100/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 100/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 0 = 100. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

✓ No adoption-risk deductions — minimal blast radius, verified enough, and fully inspected.

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 50

Each tool and what it can reach — statically extracted from the published source.

  • homelab_adguardFiltersno sensitive capability
  • homelab_adguardQueryLogno sensitive capability
  • homelab_adguardStatsno sensitive capability
  • homelab_alertListno sensitive capability
  • homelab_aptHistoryno sensitive capability
  • homelab_aptUpdateno sensitive capability
  • homelab_aptUpgradableno sensitive capability
  • homelab_backupDiffno sensitive capability
  • homelab_backupListno sensitive capability
  • homelab_backupRestoreno sensitive capability
Show 40 more tools ↓
  • homelab_backupRunno sensitive capability
  • homelab_backupStatusno sensitive capability
  • homelab_certCheckno sensitive capability
  • homelab_certListno sensitive capability
  • homelab_certRenewno sensitive capability
  • homelab_composeDownno sensitive capability
  • homelab_composePsno sensitive capability
  • homelab_composePullno sensitive capability
  • homelab_composeUpno sensitive capability
  • homelab_containerScanno sensitive capability
  • homelab_diagnosticsno sensitive capability
  • homelab_diskUsageno sensitive capability
  • homelab_fail2banStatusno sensitive capability
  • homelab_grafanaSnapshotno sensitive capability
  • homelab_healthCheckno sensitive capability
  • homelab_inventorySyncno sensitive capability
  • homelab_journalLogsno sensitive capability
  • homelab_kernelInfono sensitive capability
  • homelab_logSearchno sensitive capability
  • homelab_networkInfono sensitive capability
  • homelab_nodeExecno sensitive capability
  • homelab_nodeListno sensitive capability
  • homelab_nodeStatusno sensitive capability
  • homelab_npmCertsno sensitive capability
  • homelab_npmProxyHostsno sensitive capability
  • homelab_ntfySendno sensitive capability
  • homelab_ntfyTopicsno sensitive capability
  • homelab_openPortsno sensitive capability
  • homelab_piRebootno sensitive capability
  • homelab_piStatusno sensitive capability
  • homelab_prometheusQueryno sensitive capability
  • homelab_serviceHealthno sensitive capability
  • homelab_serviceLogsno sensitive capability
  • homelab_serviceRestartno sensitive capability
  • homelab_speedtestResultsno sensitive capability
  • homelab_sshTestno sensitive capability
  • homelab_systemdServicesno sensitive capability
  • homelab_ufwStatusno sensitive capability
  • homelab_uptimeKumaStatusno sensitive capability
  • homelab_volumeBackupno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.10.0 latest A 100/100 0 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 100/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/tmhs-homelab-mcp/badge.svg)](https://mcptrustchecker.com/registry/tmhs-homelab-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/tmhs-homelab-mcp"><img src="https://mcptrustchecker.com/registry/tmhs-homelab-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/tmhs-homelab-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @tmhs/homelab-mcp --online

Use the free API → How scoring works

Other implementations of Homelab 3

Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →

More in Developer Tools