maintenant
OCI · GHCR.IO/KOLAPSIS/MAINTENANT · 2 COMPONENTS
Docker monitoring for AI agents: logs, history, alerts. Can ack alerts; never touches containers.
Available components
Last scanned (22 hours ago)
Scores higher than 33% of OCI servers
Category Monitoring and Observability
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 Security8
- 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
- CVE check failed: a known advisory affects this package; its severity couldn't be graded. See how to fix → View diagnostics → Fail
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency87
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to kOlapsis/maintenant). View diagnostics → Pass
- License check failed: the license (Apache-2.0 AND LicenseRef-Maintenant-Commercial) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 9 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
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.
- 30 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 29 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
- 28 Oct 26 0
- CVE-2026-78661 affects this package: none ▼ security
- CVE-2026-97045 affects this package: none ▼ security
- 25 Oct 26 0
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 1.10.1 → 1.11.0 functional
- 23 Oct 26 20
First indexed and scored.
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/kolapsis/maintenant@1.11.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | oci |
| Reason | Verified |
| Discovered via | OCI referrers API |
| Source repo | kOlapsis/maintenant |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/kOlapsis/maintenant/.github/workflows/release.yml@refs/tags/v1.11.0 |
| Rekor log index | 3469726291 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:49981af48393027d92e7f50fd261605a114e1d3f17f53bc32973c33f2a696819 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 4 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-685w-q87j-wqw3 | CVE-2026-85747 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N | no |
| GO-2026-5932 | none | yes | ||
| GO-2026-6860 | CVE-2026-78661 | none | yes | |
| GO-2026-6866 | CVE-2026-97045 | none | yes |
Background: What a vulnerability scan can and cannot prove →
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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the maintenant MCP server?
maintenant runs locally as a container image, launched with docker run --rm -i ghcr.io/kolapsis/maintenant:1.11.0. 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/kolapsis/maintenant
claude mcp add kolapsis-maintenant -- docker run --rm -i ghcr.io/kolapsis/maintenant:1.11.0
What is the maintenant MCP server?
maintenant is an MCP server listed in the public MCP registry as io.github.kOlapsis/maintenant. Docker monitoring for AI agents: logs, history, alerts. Can ack alerts; never touches containers. This page covers its container image (ghcr.io/kolapsis/maintenant).
Is the maintenant MCP server safe to use?
maintenant scores 20 out of 100 on VerifyMCP. We recorded 4 known advisories against 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.
Is the maintenant MCP server still maintained?
maintenant 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.