MCP servers › io.github.polymatx › opsgate

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.polymatx/opsgate

The safety gate between AI agents and your servers: typed, policy-checked, audited ops tools. — the publisher's description

5 of 5 record checks metRead-only · tools listed 2026-10-23Topic: cloud-and-devops · AI-classifiedPricing: open-source · AI-classifiedversion 0.1.3Gostandard input/output25 tools

Summary

io.github.polymatx/opsgate is a local MCP server listed in the official MCP registry at version 0.1.3. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 25 tools, 0 resources and 0 prompts.

Record checks

5 of 5 record checks met · 4 do not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
met: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: not an npm or PyPI package
Not ranked by stars: 1 star (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: local package
Transport: standard input/output
Package: Docker (OCI)
Repository: public
Tools: 25
Described as changing data: 8 of 25 toolsAI-classified
Mainly works on: files and code on the machine it runs on; cloud accounts, servers or DevOps toolsAI-classified
Topic: cloud-and-devopsAI-classified
Pricing: open-sourceAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

8 tools are described as changing something (docker_restart, docker_start, docker_stop, …): our AI model's reading of the descriptions, not something we tested. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

0.1.3, published 2026-10-18 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-17 (earliest version still in the registry; older removed versions would be earlier)

Version history

2 versions listed, 2026-10-17 to 2026-10-18; 2 in the 90 days before the 2026-10-23 snapshot.

Most recent 2 versions

0.1.3 · 2026-10-18
0.1.2 · 2026-10-17

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-23

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.1.3 (published 2026-10-18).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

25tools

0resources

0prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on; cloud accounts, servers or DevOps tools.

8 of 25 tools are described as changing something (creating, editing, deleting, sending or running).

compose_pson 1 other serverreads or searches
“List services of a Docker Compose project in a directory.”
2 inputs, 1 required
- hoststring“target host name from the opsgate config; omit for the default host”
- dirstringrequired“directory containing the compose file”
dir_listreads or searches
“List a directory under one of the configured allowed paths.”
2 inputs, 1 required
- hoststring“target host name from the opsgate config; omit for the default host”
- pathstringrequired“absolute directory path to list”
disk_usageon 5 other serversreads or searches
“Show mounted filesystem usage (df -h) for a host.”
1 input
- hoststring“target host name from the opsgate config; omit for the default host”
docker_inspecton 3 other serversreads or searches
“Inspect a container's health, restart count, image and mounts.”
2 inputs, 1 required
- hoststring“target host name from the opsgate config; omit for the default host”
- containerstringrequired“container name or ID”
docker_logson 4 other serversreads or searches
“Read the recent logs of a Docker container.”
3 inputs, 1 required
- hoststring“target host name from the opsgate config; omit for the default host”
- containerstringrequired“container name or ID”
- linesinteger“how many trailing log lines (default 100, max 2000)”
docker_pson 3 other serversreads or searches
“List Docker containers with status, image and ports.”
2 inputs
- hoststring“target host name from the opsgate config; omit for the default host”
- allboolean“include stopped containers (default false)”
docker_restarton 3 other serversdescribed as changing data
“Restart a Docker container.”
2 inputs, 1 required
- hoststring“target host name from the opsgate config; omit for the default host”
- containerstringrequired“container name or ID”
docker_starton 2 other serversdescribed as changing data
“Start a stopped Docker container.”
2 inputs, 1 required
- hoststring“target host name from the opsgate config; omit for the default host”
- containerstringrequired“container name or ID”
docker_statson 4 other serversreads or searches
“Show a one-shot snapshot of container CPU and memory usage.”
1 input
- hoststring“target host name from the opsgate config; omit for the default host”
docker_stopon 3 other serversdescribed as changing data
“Stop a running Docker container.”
2 inputs, 1 required
- hoststring“target host name from the opsgate config; omit for the default host”
- containerstringrequired“container name or ID”
file_grepreads or searches
“Search a file for a fixed string.”
4 inputs, 2 required
- hoststring“target host name from the opsgate config; omit for the default host”
- pathstringrequired“absolute file path to search”
- patternstringrequired“fixed string to search for (not a regular expression)”
- linesinteger“maximum matching lines to return (default 100, max 1000)”
file_readon 2 other serversreads or searches
“Read a file under one of the configured allowed paths (see files.allow_paths).”
3 inputs, 1 required
- hoststring“target host name from the opsgate config; omit for the default host”
- pathstringrequired“absolute path of the file to read”
- linesinteger“read only the last N lines instead of the whole file”

Show 13 more tools

journal_errorson 1 other serverreads or searches
“Show recent error-and-worse journal entries across the system — a fast triage starting point.”
1 input
- hoststring“target host name from the opsgate config; omit for the default host”
journal_tailreads or searches
“Read recent systemd journal entries, optionally filtered by unit, time and priority.”
5 inputs
- hoststring“target host name from the opsgate config; omit for the default host”
- unitstring“systemd unit to filter by; omit for the whole journal”
- linesinteger“how many trailing lines (default 100, max 2000)”
- sincestring“systemd time expression such as '1 hour ago' or '2026-07-29 10:00'”
- prioritystring“minimum priority: emerg, alert, crit, err, warning, notice, info, debug”
listening_portson 1 other serverreads or searches
“List listening TCP/UDP sockets and the processes owning them.”
1 input
- hoststring“target host name from the opsgate config; omit for the default host”
nginx_reloaddescribed as changing data
“Reload nginx.”
1 input
- hoststring“target host name from the opsgate config; omit for the default host”
nginx_testreads or searches
“Validate the nginx configuration (nginx -t) without applying it.”
1 input
- hoststring“target host name from the opsgate config; omit for the default host”
process_topreads or searches
“List the top processes on a host by CPU or memory usage.”
3 inputs
- hoststring“target host name from the opsgate config; omit for the default host”
- bystring“sort processes by cpu or mem (default cpu)”
- limitinteger“how many processes to return (default 15, max 50)”
service_liston 5 other serversreads or searches
“List systemd services on a host, optionally filtered to running or failed units.”
2 inputs
- hoststring“target host name from the opsgate config; omit for the default host”
- statestring“filter by state: running, failed, or all (default running)”
service_reloaddescribed as changing data
“Reload a systemd service's configuration without restarting it.”
2 inputs, 1 required
- hoststring“target host name from the opsgate config; omit for the default host”
- namestringrequired“systemd unit name, for example nginx or docker.service”
service_restartdescribed as changing data
“Restart a systemd service.”
2 inputs, 1 required
- hoststring“target host name from the opsgate config; omit for the default host”
- namestringrequired“systemd unit name, for example nginx or docker.service”
service_startdescribed as changing data
“Start a stopped systemd service.”
2 inputs, 1 required
- hoststring“target host name from the opsgate config; omit for the default host”
- namestringrequired“systemd unit name, for example nginx or docker.service”
service_statuson 19 other serversreads or searches
“Show the status of one systemd service, including recent log lines.”
2 inputs, 1 required
- hoststring“target host name from the opsgate config; omit for the default host”
- namestringrequired“systemd unit name, for example nginx or docker.service”
service_stopdescribed as changing data
“Stop a running systemd service.”
2 inputs, 1 required
- hoststring“target host name from the opsgate config; omit for the default host”
- namestringrequired“systemd unit name, for example nginx or docker.service”
system_infoon 6 other serversreads or searches
“Show kernel, uptime, load average and memory usage for a host.”
1 input
- hoststring“target host name from the opsgate config; omit for the default host”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 25 tools
Says what it returns: 100% of 25 tools
States limits, defaults or errors: 20% of 25 tools
Says when to use it: 4% of 24 tools
Items covered per tool: 2.3 of 4 on average

Counted from the listing

Parameters with a description: 100% of 51
Tools with a description: 100% of 25
Typical description length: 57 characters

The tool set

Counted from the listing

Tools: 25
Size of the list: about 2,416 tokens for an agent to load (characters ÷ 4)
Naming: 25 of 25 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 25 of 25 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the Docker image ghcr.io/polymatx/opsgate:0.1.3

Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)

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

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

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

VS Code · .vscode/mcp.json

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

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"opsgate","type":"stdio","command":"docker","args":["run","-i","--rm","ghcr.io/polymatx/opsgate:0.1.3"]}'

Claude Code

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

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -- docker run -i --rm ghcr.io/polymatx/opsgate:0.1.3

This runs the publisher's code on your machine (docker). Read its README first.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Published package can be started	Started and answered	matches	our test · 2026-10-23
Repository github.com/polymatx/opsgate	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.polymatx · 2 servers
GitHub owner: a personal account (polymatx)

Repository: github.com/polymatx/opsgate
Stars: 1
Repository age: 31–90 days
Last push: 0–30 days ago
Archived: no
Security policy: SECURITY.md

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

5 of 5 record checks met · 4 do not apply

Not ranked by downloads: not an npm or PyPI package
Not ranked by stars: 1 star (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
Does not applyPackage names its licence with a standard (SPDX) identifierNot an npm or PyPI package.
Does not applyThe version the registry lists can be installed and is not withdrawnNot an npm or PyPI package.
Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
Does not applyNo known critical or high advisory in the package or its dependenciesNot an npm or PyPI package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.polymatx/opsgate

Answered from the data above

Is io.github.polymatx/opsgate safe to install?

We do not rate servers as safe or unsafe. 5 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. 8 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is io.github.polymatx/opsgate free to use?

Its website (polymatx.dev/blog/posts/opsgate-ai-agents-without-a-shell/) describes a open-source pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Has io.github.polymatx/opsgate been security tested?

Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.polymatx/opsgate do?

It lists 25 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.polymatx/opsgate change or delete data?

8 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.polymatx/opsgate publish a security policy?

Yes: its repository has a public security policy (github.com/polymatx/opsgate/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Where is the source code of io.github.polymatx/opsgate?

In github.com/polymatx/opsgate, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

com.oneuptime/mcpOneUptimealso has tools that reads or searchescompare with this one
com.cloudflare.mcp/mcpalso has tools that reads or searchescompare with this one
io.github.patrickchugh/terravisionTerraVisionalso has tools that reads or searchescompare with this one
io.github.BetterDB-inc/monitoralso has tools that reads or searchescompare with this one
io.github.TencentCloudBase/cloudbase-mcpCloudBasealso has tools that reads or searchescompare with this one
io.github.Higangssh/homebutleralso has tools that reads or searchescompare with this one

Active servers whose topic is also “cloud-and-devops” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

2 exercised10 not run (reason given)6 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 12 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised

Not run, with the reason · 10

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against

Does not apply to this server · 6

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted the published package in an isolated sandbox (read-only mode)
156 msConnected after 0 redirects.
Read the inventory: 25 tools, 0 resources, 0 prompts.
2,789 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

cloud-and-devops

AI-classified · 2026-10-23

Pricing modelAI-classified

open-source

read from polymatx.dev/blog/posts/opsgate-ai-agents-without-a-shell/ · 2026-10-23

“The code is MIT licensed at github.com/polymatx/opsgate .”

Programming language

api.github.com · 2026-10-23

Hosting type

local package

registry · 2026-10-23

MCP capability

logging, tools

our test · 2026-10-23

Transport

standard input/output

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

oci

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

does not apply

package ecosystem not queried by this layer (oci); only npm and PyPI are supported here

Integrity hash

does not apply

package ecosystem not queried by this layer (oci); only npm and PyPI are supported here

Signature / provenance

does not apply

package ecosystem not queried by this layer (oci); only npm and PyPI are supported here

Dependency advisories

not checked

only npm and PyPI packages are audited

Popularity

does not apply

package ecosystem not queried by this layer (oci); only npm and PyPI are supported here

Publisher signals

owner: a personal account · repository age: 31–90 days · stars: 0–9

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

your machine

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.polymatx/opsgate: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.polymatx/opsgate

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.polymatx/opsgate)](https://protocolprobe.com/mcp/servers/io.github.polymatx/opsgate)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology