opsgate
OCI · GHCR.IO/POLYMATX/OPSGATE
The safety gate between AI agents and your servers: typed, policy-checked, audited ops tools.
Available components
Last scanned (21 hours ago)
Scores higher than 74% of OCI servers
Category Cloud Infrastructure
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 & Transparency48
- 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 16 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1554 tokens (~62/item across 25 items; 25 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 25 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 4 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
- 20 Oct 26 +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.
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/ghcr.io/polymatx/opsgate@0.1.3
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 →
compose_ps ~52
List services of a Docker Compose project in a directory.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | yes | directory containing the compose file |
| host | string | – | target host name from the opsgate config; omit for the default host |
No output schema declared.
No examples provided.
dir_list ~52
List a directory under one of the configured allowed paths.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | target host name from the opsgate config; omit for the default host |
| path | string | yes | absolute directory path to list |
No output schema declared.
No examples provided.
disk_usage ~42
Show mounted filesystem usage (df -h) for a host.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | target host name from the opsgate config; omit for the default host |
No output schema declared.
No examples provided.
docker_inspect ~54
Inspect a container's health, restart count, image and mounts.
| Name | Type | Req | Description |
|---|---|---|---|
| container | string | yes | container name or ID |
| host | string | – | target host name from the opsgate config; omit for the default host |
No output schema declared.
No examples provided.
docker_logs ~70
Read the recent logs of a Docker container.
| Name | Type | Req | Description |
|---|---|---|---|
| container | string | yes | 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) |
No output schema declared.
No examples provided.
docker_ps ~52
List Docker containers with status, image and ports.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | include stopped containers (default false) |
| host | string | – | target host name from the opsgate config; omit for the default host |
No output schema declared.
No examples provided.
docker_restart ~45
Restart a Docker container.
| Name | Type | Req | Description |
|---|---|---|---|
| container | string | yes | container name or ID |
| host | string | – | target host name from the opsgate config; omit for the default host |
No output schema declared.
No examples provided.
docker_start ~46
Start a stopped Docker container.
| Name | Type | Req | Description |
|---|---|---|---|
| container | string | yes | container name or ID |
| host | string | – | target host name from the opsgate config; omit for the default host |
No output schema declared.
No examples provided.
docker_stats ~41
Show a one-shot snapshot of container CPU and memory usage.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | target host name from the opsgate config; omit for the default host |
No output schema declared.
No examples provided.
docker_stop ~46
Stop a running Docker container.
| Name | Type | Req | Description |
|---|---|---|---|
| container | string | yes | container name or ID |
| host | string | – | target host name from the opsgate config; omit for the default host |
No output schema declared.
No examples provided.
file_grep ~98
Search a file for a fixed string. Useful for finding an error in a large log.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | absolute file path to search |
| pattern | string | yes | fixed string to search for (not a regular expression) |
No output schema declared.
No examples provided.
file_read ~77
Read a file under one of the configured allowed paths (see files.allow_paths).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | absolute path of the file to read |
No output schema declared.
No examples provided.
journal_errors ~48
Show recent error-and-worse journal entries across the system — a fast triage starting point.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | target host name from the opsgate config; omit for the default host |
No output schema declared.
No examples provided.
journal_tail ~139
Read recent systemd journal entries, optionally filtered by unit, time and priority.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
listening_ports ~41
List listening TCP/UDP sockets and the processes owning them.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | target host name from the opsgate config; omit for the default host |
No output schema declared.
No examples provided.
nginx_reload ~45
Reload nginx. Validates the configuration first and refuses to reload a broken config.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | target host name from the opsgate config; omit for the default host |
No output schema declared.
No examples provided.
nginx_test ~43
Validate the nginx configuration (nginx -t) without applying it.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | target host name from the opsgate config; omit for the default host |
No output schema declared.
No examples provided.
process_top ~78
List the top processes on a host by CPU or memory usage.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
service_list ~65
List systemd services on a host, optionally filtered to running or failed units.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
service_reload ~58
Reload a systemd service's configuration without restarting it.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | target host name from the opsgate config; omit for the default host |
| name | string | yes | systemd unit name, for example nginx or docker.service |
No output schema declared.
No examples provided.
service_restart ~53
Restart a systemd service.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | target host name from the opsgate config; omit for the default host |
| name | string | yes | systemd unit name, for example nginx or docker.service |
No output schema declared.
No examples provided.
service_start ~54
Start a stopped systemd service.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | target host name from the opsgate config; omit for the default host |
| name | string | yes | systemd unit name, for example nginx or docker.service |
No output schema declared.
No examples provided.
service_status ~61
Show the status of one systemd service, including recent log lines.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | target host name from the opsgate config; omit for the default host |
| name | string | yes | systemd unit name, for example nginx or docker.service |
No output schema declared.
No examples provided.
service_stop ~54
Stop a running systemd service.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | target host name from the opsgate config; omit for the default host |
| name | string | yes | systemd unit name, for example nginx or docker.service |
No output schema declared.
No examples provided.
system_info ~43
Show kernel, uptime, load average and memory usage for a host.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | target host name from the opsgate config; omit for the default host |
No output schema declared.
No examples provided.
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.
oci · ghcr.io/polymatx/opsgate
claude mcp add polymatx-opsgate -- docker run --rm -i ghcr.io/polymatx/opsgate:0.1.3
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.