# opsgate (oci · ghcr.io/polymatx/opsgate)

The safety gate between AI agents and your servers: typed, policy-checked, audited ops tools.

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

## Components

- oci · `ghcr.io/polymatx/opsgate`: 49/100 (this document), [markdown](https://verifymcp.io/servers/polymatx-opsgate/ghcr-io-polymatx-opsgate.md), [page](https://verifymcp.io/servers/polymatx-opsgate/ghcr-io-polymatx-opsgate)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/polymatx/opsgate`
- Version: `0.1.3`
- 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**: 0/100
  - 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.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 16 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1554 tokens (~62/item across 25 items; 25 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 25 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (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 opsgate MCP server?

opsgate runs locally as a container image, launched with docker run --rm -i ghcr.io/polymatx/opsgate:0.1.3. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add polymatx-opsgate -- docker run --rm -i ghcr.io/polymatx/opsgate:0.1.3
```

### Cursor

```json
{
  "mcpServers": {
    "polymatx-opsgate": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/polymatx/opsgate:0.1.3"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "polymatx-opsgate": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/polymatx/opsgate:0.1.3"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add polymatx-opsgate -- docker run --rm -i ghcr.io/polymatx/opsgate:0.1.3
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "polymatx-opsgate": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/polymatx/opsgate:0.1.3"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  polymatx-opsgate:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/polymatx/opsgate:0.1.3"]
```

### Netclaw

```json
{
  "McpServers": {
    "polymatx-opsgate": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/polymatx/opsgate:0.1.3"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "polymatx-opsgate": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/polymatx/opsgate:0.1.3"
      ]
    }
  }
}
```

## 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-11-04 (score 49, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 48, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 47, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 46, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 45, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 44, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (25)

### `compose_ps` (~52 tokens)

List services of a Docker Compose project in a directory.

Input parameters:

- `dir` (string, required): directory containing the compose file
- `host` (string): target host name from the opsgate config; omit for the default host

### `dir_list` (~52 tokens)

List a directory under one of the configured allowed paths.

Input parameters:

- `host` (string): target host name from the opsgate config; omit for the default host
- `path` (string, required): absolute directory path to list

### `disk_usage` (~42 tokens)

Show mounted filesystem usage (df -h) for a host.

Input parameters:

- `host` (string): target host name from the opsgate config; omit for the default host

### `docker_inspect` (~54 tokens)

Inspect a container's health, restart count, image and mounts.

Input parameters:

- `container` (string, required): container name or ID
- `host` (string): target host name from the opsgate config; omit for the default host

### `docker_logs` (~70 tokens)

Read the recent logs of a Docker container.

Input parameters:

- `container` (string, required): container name or ID
- `host` (string): target host name from the opsgate config; omit for the default host
- `lines` (integer): how many trailing log lines (default 100, max 2000)

### `docker_ps` (~52 tokens)

List Docker containers with status, image and ports.

Input parameters:

- `all` (boolean): include stopped containers (default false)
- `host` (string): target host name from the opsgate config; omit for the default host

### `docker_restart` (~45 tokens)

Restart a Docker container.

Input parameters:

- `container` (string, required): container name or ID
- `host` (string): target host name from the opsgate config; omit for the default host

### `docker_start` (~46 tokens)

Start a stopped Docker container.

Input parameters:

- `container` (string, required): container name or ID
- `host` (string): target host name from the opsgate config; omit for the default host

### `docker_stats` (~41 tokens)

Show a one-shot snapshot of container CPU and memory usage.

Input parameters:

- `host` (string): target host name from the opsgate config; omit for the default host

### `docker_stop` (~46 tokens)

Stop a running Docker container.

Input parameters:

- `container` (string, required): container name or ID
- `host` (string): target host name from the opsgate config; omit for the default host

### `file_grep` (~98 tokens)

Search a file for a fixed string. Useful for finding an error in a large log.

Input parameters:

- `host` (string): target host name from the opsgate config; omit for the default host
- `lines` (integer): maximum matching lines to return (default 100, max 1000)
- `path` (string, required): absolute file path to search
- `pattern` (string, required): fixed string to search for (not a regular expression)

### `file_read` (~77 tokens)

Read a file under one of the configured allowed paths (see files.allow_paths).

Input parameters:

- `host` (string): target host name from the opsgate config; omit for the default host
- `lines` (integer): read only the last N lines instead of the whole file
- `path` (string, required): absolute path of the file to read

### `journal_errors` (~48 tokens)

Show recent error-and-worse journal entries across the system — a fast triage starting point.

Input parameters:

- `host` (string): target host name from the opsgate config; omit for the default host

### `journal_tail` (~139 tokens)

Read recent systemd journal entries, optionally filtered by unit, time and priority.

Input parameters:

- `host` (string): target host name from the opsgate config; omit for the default host
- `lines` (integer): how many trailing lines (default 100, max 2000)
- `priority` (string): minimum priority: emerg, alert, crit, err, warning, notice, info, debug
- `since` (string): systemd time expression such as '1 hour ago' or '2026-07-29 10:00'
- `unit` (string): systemd unit to filter by; omit for the whole journal

### `listening_ports` (~41 tokens)

List listening TCP/UDP sockets and the processes owning them.

Input parameters:

- `host` (string): target host name from the opsgate config; omit for the default host

### `nginx_reload` (~45 tokens)

Reload nginx. Validates the configuration first and refuses to reload a broken config.

Input parameters:

- `host` (string): target host name from the opsgate config; omit for the default host

### `nginx_test` (~43 tokens)

Validate the nginx configuration (nginx -t) without applying it.

Input parameters:

- `host` (string): target host name from the opsgate config; omit for the default host

### `process_top` (~78 tokens)

List the top processes on a host by CPU or memory usage.

Input parameters:

- `by` (string): sort processes by cpu or mem (default cpu)
- `host` (string): target host name from the opsgate config; omit for the default host
- `limit` (integer): how many processes to return (default 15, max 50)

### `service_list` (~65 tokens)

List systemd services on a host, optionally filtered to running or failed units.

Input parameters:

- `host` (string): target host name from the opsgate config; omit for the default host
- `state` (string): filter by state: running, failed, or all (default running)

### `service_reload` (~58 tokens)

Reload a systemd service's configuration without restarting it.

Input parameters:

- `host` (string): target host name from the opsgate config; omit for the default host
- `name` (string, required): systemd unit name, for example nginx or docker.service

### `service_restart` (~53 tokens)

Restart a systemd service.

Input parameters:

- `host` (string): target host name from the opsgate config; omit for the default host
- `name` (string, required): systemd unit name, for example nginx or docker.service

### `service_start` (~54 tokens)

Start a stopped systemd service.

Input parameters:

- `host` (string): target host name from the opsgate config; omit for the default host
- `name` (string, required): systemd unit name, for example nginx or docker.service

### `service_status` (~61 tokens)

Show the status of one systemd service, including recent log lines.

Input parameters:

- `host` (string): target host name from the opsgate config; omit for the default host
- `name` (string, required): systemd unit name, for example nginx or docker.service

### `service_stop` (~54 tokens)

Stop a running systemd service.

Input parameters:

- `host` (string): target host name from the opsgate config; omit for the default host
- `name` (string, required): systemd unit name, for example nginx or docker.service

### `system_info` (~43 tokens)

Show kernel, uptime, load average and memory usage for a host.

Input parameters:

- `host` (string): target host name from the opsgate config; omit for the default host

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/polymatx-opsgate/ghcr-io-polymatx-opsgate#diagnostics

## Score history

- 2026-11-04: 49
- 2026-11-03: 48
- 2026-11-02: 48
- 2026-11-01: 48
- 2026-10-31: 47
- 2026-10-30: 47
- 2026-10-29: 46
- 2026-10-28: 46
- 2026-10-27: 45
- 2026-10-26: 45
- 2026-10-25: 44
- 2026-10-24: 44
- 2026-10-23: 43
- 2026-10-22: 43
- 2026-10-21: 42
- 2026-10-20: 42
- 2026-10-19: 41
- 2026-10-18: 41

## Common questions

### What is the opsgate MCP server?

opsgate is an MCP server listed in the public MCP registry as io.github.polymatx/opsgate. The safety gate between AI agents and your servers: typed, policy-checked, audited ops tools. This page covers its container image (ghcr.io/polymatx/opsgate).

### Is the opsgate MCP server safe to use?

opsgate scores 49 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 opsgate MCP server expose?

opsgate exposes 25 tools: compose_ps, dir_list, disk_usage, docker_inspect, docker_logs, and 20 more. Their descriptions and schemas cost roughly 1,457 tokens of context every time the server is loaded.

### Is the opsgate MCP server still maintained?

opsgate 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 opsgate MCP server under?

opsgate 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

- GitHub Container Registry: https://ghcr.io/polymatx/opsgate
- Repository: https://github.com/polymatx/opsgate
- Website: https://polymatx.dev/blog/posts/opsgate-ai-agents-without-a-shell/
- Changelog RSS feed: https://verifymcp.io/servers/polymatx-opsgate/ghcr-io-polymatx-opsgate.xml
- Changelog JSON feed: https://verifymcp.io/servers/polymatx-opsgate/ghcr-io-polymatx-opsgate.json
- HTML version of this page: https://verifymcp.io/servers/polymatx-opsgate/ghcr-io-polymatx-opsgate