Skip to content

MCP servers › io.github.gkdis6 › opsgate

MCP server · registry snapshot 2026-11-12 · last checked 2026-11-12

opsgate MCP server

Registry name io.github.gkdis6/opsgate

by gkdis6 · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗

Kubernetes MCP server where AI proposes changes and you approve each with a passkey on your phone. — the publisher's description

5 of 5 record checks metversion 0.8.0Gostandard input/output

Summary

io.github.gkdis6/opsgate is a local MCP server listed in the official MCP registry at version 0.8.0, under the namespace of the GitHub account gkdis6. Its linked repository, github.com/gkdis6/opsgate, belongs to the same GitHub account.

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: 2 stars (ranked from 10)

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

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
local package
Transport
standard input/output
Your own values
none declared (not a guarantee)
Package
Docker (OCI)
Repository
public
Last tested
not tested

Tool list

Not read: It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it. So there is no tool-list size and no result from the three APIs.

Add to your client

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
0.8.0, published 2026-11-11 (registry, as of the 2026-11-12 snapshot)
First listed version
2026-11-09 (earliest version still in the registry; older removed versions would be earlier)
Version history
4 versions listed, 2026-11-09 to 2026-11-11; 4 in the 90 days before the 2026-11-12 snapshot.
Most recent 4 versions
  • 0.8.0 · 2026-11-11
  • 0.7.0 · 2026-11-09
  • 0.6.0 · 2026-11-09
  • 0.5.0 · 2026-11-09
(versions still listed in the registry only)
Registry data
snapshot 2026-11-12
Package and repository
checked 2026-11-12

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 0.7.0 (published 2026-11-09) → 0.8.0 (published 2026-11-11), between the registry lists of 2026-11-09 and 2026-11-12.

The publisher’s GitHub release note for v0.8.0, published 2026-11-11.

Read the release note (the publisher’s text, shown as plain text, cut at 4,000 characters)
**AI proposes. Your passkey runs it.** This release is about trust: a security pass over every outside input, approvals that survive a restart, and the first compatibility policy.

## Highlights

- **Approvals survive a restart.** With `approval.state_file` (on by default with a mode), approval cards opened from links, inbox notices and the link-signing key are kept across restarts. A restored card gets a new form token and is planned again when approved; a decided one is never restored.
- **Signed action links.** The source on a card ("rule" or "AI") can no longer be relabelled. A link the server did not sign still needs the same approval, but its card says so.
- **Security pass.** Go fuzz tests for every parser that takes outside input, two known limitations closed, and nine fixes from an AI-assisted audit: hidden values for `MYSQL_PWD`-style names, bounded `$(VAR)` expansion, a restart bound to the reviewed spec, "Outcome unknown" instead of a false "Not applied", link approvals deduplicated and capped, upload deadlines and a session admission rate. The audit was automated, not a third-party human review.
- **Stability policy.** [docs/stability.md](https://github.com/gkdis6/opsgate/blob/main/docs/stability.md) says which configuration, tools, routes and formats are kept compatible and how changes are announced. Watch, the approval inbox and push are no longer labelled experimental; the analyzer, notes and the host provider still are.
- **Shorter analyzer reports.** Cause first with its certainty, at most three steps (an approval link or one command alone in a code block), up to three evidence lines.
- **Metrics.** `http.metrics_listen` serves Prometheus metrics on a separate, unauthenticated port for an in-cluster scraper.
- **End-to-end test.** Every pull request runs the real binary on a kind cluster: passkey sign-in, an action link, approval after a server restart, the restart and its recovery check.

## Upgrade notes

- `action_link` only issues `source=ai` links; `source: rule` is refused.
- `approval_status` can return `unknown` when an apply timed out or lost its connection.
- `/healthz` answers only GET. Request bodies must arrive within 30 seconds.
- With a mode, the server writes `/var/lib/opsgate/approvals.json` (0600). If the path is not writable it logs a warning and keeps the state in memory.
- Links issued by another process (`opsgate watch`, the analyzer's reader) show as unsigned on the server; the choices page they lead to issues signed ones.

Full list: [CHANGELOG](https://github.com/gkdis6/opsgate/blob/main/CHANGELOG.md#080---2026-11-11).

## Changelog
* 5c511415ad7de52bc89d9e9f4c4159a27d462ed7 analyzer: short reports that lead with the cause and copyable steps
* ef0433c1dd650d83bdfc835becbda5bc058af7d4 approval: keep link approvals, notices and the link key across restarts
* 494f1a9a810983685d26d6dc4cb1bb2608cf18d5 approval: sign action links so the source on a card cannot be forged
* 88563cf0bd71188294ccb5a3861fc8ff5fd868e5 build(deps): bump actions/setup-go from 6.5.0 to 7.0.0
* c6c04428f330d3f85d948f3d5fbaad8b71577f18 build(deps): bump docker/login-action from 3.7.0 to 4.8.0
* 59a27db515af147891589605d176978f694905a3 build(deps): bump docker/setup-qemu-action from 3.7.0 to 4.4.0
* 237e65492980e745415aa87952f0de87c8e5cdea build(deps): bump github.com/fxamacker/cbor/v2 from 2.9.4 to 2.10.0
* 3dbd697f039a0dc5b32e4f382f871f413835f3c1 build(deps): bump go-jose to 4.1.9 and x/oauth2 to 0.38.0
* 815e80fc7f225e9e48cf8084ba2af28903963cc1 build(deps): bump golang from `2920bb1` to `e519d3b`
* 90a9f4f5e4e064dbe2e2b96a4911d475b722b64e build(deps): bump golang.org/x/sys from 0.49.0 to 0.50.0
* bc8249104256fbcf1e560e8c853eb18930a014db ci: pin all three CodeQL actions to v4.39.3
* 16b6282502bb4b346dd655c4a40097be3f2b1d3d ci: update CodeQL actions together and group them in Dependabot
* f8a9c6ff952ace7b57f83e0dc3e1a065a2006908 docs: rewrite the Korean README in natural Korean
* 2289f6e3c60024bfcc189c7f2f206ca4efc294

The release on GitHub

Source: the official MCP Registry list on 2026-11-09 and on 2026-11-12; release notes from the GitHub Releases API, checked 2026-11-12.

What it is

How do I add it to my client?

Config from the registry entry
  • No config: the Docker image declares runtime arguments (options for the runner itself), and the registry documentation gives no rule for where they go.

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; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). 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.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Image

  • Image platforms. The image is published for linux/amd64 and linux/arm64. Source: read 2026-11-12.
  • Image user. The image config sets user nonroot. Read from the image config; the image was not pulled or run. Source: oci:ghcr.io/gkdis6/opsgate:v0.8.0 · read 2026-11-12.
  • Image tag history. The tag ghcr.io/gkdis6/opsgate:v0.8.0 points to the same image as when we first read it on 2026-11-12. Source: oci:ghcr.io/gkdis6/opsgate:v0.8.0 · read 2026-11-16.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-16. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-16. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-16. Source: read 2026-11-16.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-16. Source: read 2026-11-16.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Repository github.com/gkdis6/opsgateOpens publiclymatchesapi.github.com · 2026-11-12

Who made it?

Feature #7 · lineage

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

Namespace
io.github.gkdis6
GitHub owner
a personal account (gkdis6)
Repository
github.com/gkdis6/opsgate
Stars
2
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
SECURITY.md

Source: the registry entry and api.github.com · 2026-11-12; security policy read from GitHub · 2026-11-09.

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: 2 stars (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-11-12 (security policy 2026-11-09). 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, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.gkdis6/opsgate

Answered from the data above

Who publishes io.github.gkdis6/opsgate?

The registry ties the namespace io.github.gkdis6 to the GitHub account gkdis6; only its owner can publish under it. Its linked repository, github.com/gkdis6/opsgate, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.gkdis6/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. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

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

No. It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it.

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

Yes: its repository has a public security policy (github.com/gkdis6/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.gkdis6/opsgate?

In github.com/gkdis6/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.

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

Has it been tested?

Feature #1

It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it. — the server's own choice

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
pending: added at the next monthly refresh
listed 2026-11-12; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
api.github.com · 2026-11-12
Hosting type
registry · 2026-11-12
MCP capability
not checked
not read (no session)
Transport
standard input/output
registry · 2026-11-12
Required credentials
none declared
registry · 2026-11-12 · no declaration is not a guarantee
Package registry
registry · 2026-11-12
Freshness
0–30 days
registry updatedAt · 2026-11-12
Lifecycle status
registry · 2026-11-12
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: 0–30 days · stars: 0–9
api.github.com · 2026-11-12
Maintenance
api.github.com · 2026-11-12
Environment
your machine
where it runs, from the hosting type · 2026-11-12

“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.gkdis6/opsgate: MCP server record.” Data checked 2026-11-12. https://protocolprobe.com/mcp/servers/io.github.gkdis6/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: 5 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.gkdis6/opsgate)](https://protocolprobe.com/mcp/servers/io.github.gkdis6/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, except for a server whose operator has claimed it and given permission (that server's page says so).

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