# io.github.seayniclabs/homelab-infra-mcp (pypi · homelab-infra-mcp)

Homelab: Nginx Proxy Manager, Docker and Cloudflare DNS, with approval for every change.

- Trust score: 73/100 (medium)
- Change this week: +15
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- pypi · `homelab-infra-mcp`: 73/100 (this document), [markdown](https://verifymcp.io/servers/seayniclabs-homelab-infra-mcp/homelab-infra-mcp.md), [page](https://verifymcp.io/servers/seayniclabs-homelab-infra-mcp/homelab-infra-mcp)

## Channel facts

- Registry: `pypi`
- Package: `homelab-infra-mcp`
- Version: `2.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 0 of 33 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to seayniclabs/homelab-infra-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 39/100
  - 8% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 3686 tokens (~19/item across 187 items; 16 tools + 171 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### How do I install the io.github.seayniclabs/homelab-infra-mcp server?

io.github.seayniclabs/homelab-infra-mcp runs locally as a PyPI package, launched with uvx homelab-infra-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add seayniclabs-homelab-infra-mcp -- uvx homelab-infra-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "seayniclabs-homelab-infra-mcp": {
      "command": "uvx",
      "args": [
        "homelab-infra-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "seayniclabs-homelab-infra-mcp": {
      "command": "uvx",
      "args": [
        "homelab-infra-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add seayniclabs-homelab-infra-mcp -- uvx homelab-infra-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "seayniclabs-homelab-infra-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "homelab-infra-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add seayniclabs-homelab-infra-mcp --command uvx --arg homelab-infra-mcp
```

### Hermes

```yaml
mcp_servers:
  seayniclabs-homelab-infra-mcp:
    command: "uvx"
    args: ["homelab-infra-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "seayniclabs-homelab-infra-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "homelab-infra-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add seayniclabs-homelab-infra-mcp -t stdio -c uvx -a homelab-infra-mcp
```

### Other

```json
{
  "mcpServers": {
    "seayniclabs-homelab-infra-mcp": {
      "command": "uvx",
      "args": [
        "homelab-infra-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-30 (score 73, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-27 (score 58)

First indexed and scored.

## MCP tools (16)

### `proxy_hosts` (~136 tokens)

Proxy hosts. list/get are read-only. create, update and delete change NPM and need the
person's approval (or HOMELAB_PROXY_ALLOW_WRITES=true). dry_run=true previews without asking.

Input parameters:

- `action` (string)
- `block_exploits` (boolean)
- `domain_names` (string)
- `dry_run` (boolean)
- `force_ssl` (boolean)
- `forward_host` (string)
- `forward_port` (integer)
- `host_id` (integer)
- `limit` (integer)
- `offset` (integer)
- `ssl` (boolean)

Output parameters:

- `change`
- `detail`
- `has_more` (boolean)
- `items` (array)
- `total`

### `proxy_redirections` (~100 tokens)

HTTP redirections. list is read-only; create and delete need approval (or ALLOW_WRITES).

Input parameters:

- `action` (string)
- `domain_names` (string)
- `dry_run` (boolean)
- `forward_domain` (string)
- `forward_scheme` (string)
- `limit` (integer)
- `offset` (integer)
- `preserve_path` (boolean)
- `redirection_id` (integer)

Output parameters:

- `change`
- `has_more` (boolean)
- `items` (array)
- `total`

### `proxy_certificates` (~83 tokens)

SSL certificates. list is read-only. request asks Let's Encrypt for a new certificate
(needs approval, or ALLOW_WRITES). Let's Encrypt must be able to reach the domains.

Input parameters:

- `action` (string)
- `domain_names` (string)
- `dry_run` (boolean)
- `limit` (integer)
- `offset` (integer)

Output parameters:

- `change`
- `has_more` (boolean)
- `items` (array)
- `total`

### `proxy_access_lists` (~112 tokens)

IP access lists. list is read-only. create and delete need approval (or ALLOW_WRITES).
allow and deny are comma-separated IPs or CIDRs. Deleting a list affects every proxy host that uses it.

Input parameters:

- `action` (string)
- `allow` (string)
- `deny` (string)
- `dry_run` (boolean)
- `limit` (integer)
- `list_id` (integer)
- `name` (string)
- `offset` (integer)

Output parameters:

- `change`
- `has_more` (boolean)
- `items` (array)
- `total`

### `docker_containers` (~142 tokens)

Containers. list, get, logs and stats are read-only. start, stop, restart, remove and prune
change state and need the person's approval (or HOMELAB_DOCKER_ALLOW_WRITES=true).
remove deletes a container permanently. prune removes ALL stopped containers.
container is a name or id (not needed for list or prune).

Input parameters:

- `action` (string)
- `all` (boolean)
- `container` (string)
- `dry_run` (boolean)
- `limit` (integer)
- `offset` (integer)
- `since` (string)
- `tail` (integer)
- `timeout` (integer)

Output parameters:

- `change`
- `detail`
- `has_more` (boolean)
- `items` (array)
- `logs`
- `stats`
- `total`

### `docker_images` (~101 tokens)

Images. list is read-only. pull, remove and prune change the host and need approval
(or HOMELAB_DOCKER_ALLOW_WRITES=true). remove deletes an image; prune removes dangling and unused images.

Input parameters:

- `action` (string)
- `dry_run` (boolean)
- `force` (boolean)
- `image` (string)
- `limit` (integer)
- `offset` (integer)
- `tag` (string)

Output parameters:

- `change`
- `has_more` (boolean)
- `items` (array)
- `total`

### `docker_inventory` (~74 tokens)

Read-only lists: volumes, networks, or Portainer stacks (stacks need the Portainer backend).
Pass stack_id with kind=stacks to get that stack's compose file.

Input parameters:

- `kind` (string)
- `limit` (integer)
- `offset` (integer)
- `stack_id` (integer)

Output parameters:

- `backend` (string)
- `compose_file`
- `has_more` (boolean)
- `items` (array)
- `kind` (string)
- `total`

### `dns_zones` (~61 tokens)

Zones for the Cloudflare account (action=list), or one zone exported in BIND format (action=export).

Input parameters:

- `action` (string)
- `limit` (integer)
- `page` (integer)
- `zone_id` (string)

Output parameters:

- `action` (string)
- `export`
- `has_more` (boolean)
- `page` (integer)
- `zone_id`
- `zones` (array)

### `dns_records` (~149 tokens)

DNS records. list and get are read-only. create, update and delete change the zone and need
the person's approval (or HOMELAB_DNS_ALLOW_WRITES=true). create needs name, record_type and content;
update needs record_id and any field to change; delete removes the record permanently.

Input parameters:

- `action` (string)
- `content` (string)
- `dry_run` (boolean)
- `limit` (integer)
- `name` (string)
- `page` (integer)
- `proxied`
- `record_id` (string)
- `record_type` (string)
- `ttl` (integer)
- `zone_id` (string)

Output parameters:

- `change`
- `detail`
- `has_more` (boolean)
- `items` (array)
- `page` (integer)

### `expose_service` (~119 tokens)

Expose a container: check it runs, add a Cloudflare CNAME to tunnel_hostname (only if given), and add an
Nginx Proxy Manager host that forwards domain to forward_host:forward_port. The plan is shown to the
person before anything changes.

Input parameters:

- `container_name` (string, required)
- `dns_zone_id` (string)
- `domain` (string, required)
- `dry_run` (boolean)
- `forward_host` (string)
- `forward_port` (integer, required)
- `tunnel_hostname` (string)

Output parameters:

- `approved_by`
- `dry_run` (boolean)
- `errors` (array)
- `note`
- `planned` (array)
- `steps_completed` (array)
- `success` (boolean)

### `teardown_service` (~94 tokens)

Reverse expose_service: delete the proxy host for domain (found by name unless proxy_host_id is given)
and, if dns_record_id is given, that DNS record. The exact plan is shown to the person first.

Input parameters:

- `dns_record_id` (string)
- `dns_zone_id` (string)
- `domain` (string, required)
- `dry_run` (boolean)
- `proxy_host_id` (integer)

Output parameters:

- `approved_by`
- `dry_run` (boolean)
- `errors` (array)
- `note`
- `planned` (array)
- `steps_completed` (array)
- `success` (boolean)

### `service_status` (~54 tokens)

One view of a service: the container, the proxy hosts that name the domain, and its DNS records.

Input parameters:

- `container_name` (string, required)
- `dns_zone_id` (string)
- `domain` (string)

Output parameters:

- `container`
- `dns_records`
- `errors` (array)
- `proxy_hosts`

### `infrastructure_overview` (~27 tokens)

Counts across Docker, Nginx Proxy Manager and Cloudflare DNS, in one call.

Output parameters:

- `dns`
- `docker`
- `proxy`

### `diagnose_service` (~105 tokens)

Check each hop between a public domain and its upstream container, and name the first one that fails
with the fix for it. Hops: DNS record, tunnel route (if the tunnel module is on), Nginx Proxy Manager host,
TLS certificate (expiry and trust), upstream container running (Docker), upstream port answering, uptime
monitor (if on), Authentik login in front (if on). Read-only: it changes nothing.

Input parameters:

- `domain` (string, required)

Output parameters:

- `domain` (string)
- `first_failure`
- `hops` (array)
- `note`

### `homelab_modules` (~59 tokens)

Which modules are on, which settings are missing, whether writes are pre-approved, and what each tool
does. Pass a module name for its full settings list (values are never shown, only whether they are set).

Input parameters:

- `module`

Output parameters:

- `config_file` (string)
- `core_tools` (object)
- `homepage` (string)
- `modules` (array)
- `publisher` (string)
- `read_only` (boolean)
- `skills` (array)
- `version` (string)

### `homelab_health` (~30 tokens)

Connectivity and version for every enabled module. A module with missing settings reports the
variable it needs.

Output parameters:

- `modules` (array)
- `version` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/seayniclabs-homelab-infra-mcp/homelab-infra-mcp#diagnostics

## Score history

- 2026-11-04: 73
- 2026-11-03: 73
- 2026-11-02: 73
- 2026-11-01: 73
- 2026-10-31: 73
- 2026-10-30: 73
- 2026-10-29: 58
- 2026-10-28: 58
- 2026-10-27: 58

## Common questions

### What is the io.github.seayniclabs/homelab-infra-mcp server?

io.github.seayniclabs/homelab-infra-mcp is listed in the public MCP registry as io.github.seayniclabs/homelab-infra-mcp. Homelab: Nginx Proxy Manager, Docker and Cloudflare DNS, with approval for every change. This page covers its PyPI package (homelab-infra-mcp).

### Is the io.github.seayniclabs/homelab-infra-mcp server safe to use?

io.github.seayniclabs/homelab-infra-mcp scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 io.github.seayniclabs/homelab-infra-mcp server expose?

io.github.seayniclabs/homelab-infra-mcp exposes 16 tools: proxy_hosts, proxy_redirections, proxy_certificates, proxy_access_lists, docker_containers, and 11 more. Their descriptions and schemas cost roughly 1,446 tokens of context every time the server is loaded.

### Is the io.github.seayniclabs/homelab-infra-mcp server still maintained?

io.github.seayniclabs/homelab-infra-mcp 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 io.github.seayniclabs/homelab-infra-mcp server under?

io.github.seayniclabs/homelab-infra-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/homelab-infra-mcp/
- Socket report: https://socket.dev/pypi/package/homelab-infra-mcp
- Repository: https://github.com/seayniclabs/homelab-infra-mcp
- Changelog RSS feed: https://verifymcp.io/servers/seayniclabs-homelab-infra-mcp/homelab-infra-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/seayniclabs-homelab-infra-mcp/homelab-infra-mcp.json
- HTML version of this page: https://verifymcp.io/servers/seayniclabs-homelab-infra-mcp/homelab-infra-mcp