maintenant

Name: maintenant
Author: kOlapsis

by kOlapsisversion 1.11.0i★ –iComputer or cloud

Registry nameio.github.kOlapsis/maintenant

Install

Overview

Description from the maker (original English)

Docker monitoring for AI agents: logs, history, alerts. Can ack alerts; never touches containers.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet
DockerDocker installed

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://{maintenant_host}/mcp

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "maintenant": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/kolapsis/maintenant:1.11.0",
        "--mcp-stdio"
      ]
    }
  }
}

Run this in your terminal

claude mcp add --transport http maintenant 'https://{maintenant_host}/mcp'

Or run it on your computer

claude mcp add maintenant -- docker run -i --rm ghcr.io/kolapsis/maintenant:1.11.0 --mcp-stdio

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "maintenant": {
      "url": "https://{maintenant_host}/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "maintenant": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/kolapsis/maintenant:1.11.0",
        "--mcp-stdio"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "maintenant": {
      "type": "http",
      "url": "https://{maintenant_host}/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "maintenant": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/kolapsis/maintenant:1.11.0",
        "--mcp-stdio"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://{maintenant_host}/mcp

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account kOlapsis, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
The address needs your own account values, so we cannot check it for you
– Not applicable
Sign-in with OAuth
The address needs your own account values, so we cannot check it for you
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Developer toolsi

More stars than 0% of the other 1395 servers in this category
Published to the registry more recently than 78% of the other 1395 servers in this category
Basic checks equal to or better than 100% of the other 1395 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is maintenant safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.11.0) reached the registry 12 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 4 days ago

Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 16 days ago

Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

maintenant

Drop a container. Your stack is monitored.

When something breaks, fixed rules catch it, the alert is pushed to you, and your AI agent investigates through the built-in MCP server.

Docker, Kubernetes, uptime, TLS, cron jobs, live logs, image updates, CVEs: auto-discovered, alerting on every one of them,

from a single Go binary that fits in a few tens of MB of RAM when freshly started (about 100 MB after several days on a busy host). No PromQL, no exporters, no dashboards to build.

Try the live demo →

A Pro instance monitoring a real stack, read-only. Nothing to install, nothing to sign up for.

Live demo • Quick Start • Why maintenant • Agents • Features • Documentation • Editions • Pricing

Quick Start

# docker-compose.yml

services: maintenant: image: ghcr.io/kolapsis/maintenant:latest ports:

⚠️ SECURITY: publishes the UI/API (no authentication of their own) on

every interface; put an auth reverse proxy in front, or bind "127.0.0.1:8080:8080". See https://docs.maintenant.dev/security/#reverse-proxy-setup.

"8080:8080" read_only: true security_opt:
no-new-privileges:true tmpfs:
/tmp:noexec,nosuid,size=64m volumes:
/var/run/docker.sock:/var/run/docker.sock:ro
/proc:/host/proc:ro
/etc/os-release:/host/etc/os-release:ro
maintenant-data:/data environment: MAINTENANT_ADDR: "0.0.0.0:8080" MAINTENANT_DB: "/data/maintenant.db" restart: unless-stopped

volumes: maintenant-data:

docker compose up -d

Open http://localhost:8080. Your containers are already there, with their health, restart loops, resources and logs. Nothing to configure.

Docker socket access is automatic: the entrypoint reads the mounted socket's group and grants it to the unprivileged user, on Compose and on Swarm (where docker stack deploy silently ignores group_add). A socket owned by group root needs DOCKER_GID=0. If containers do not show up, see Troubleshooting.

Kubernetes

kubectl create namespace maintenant

kubectl apply -f deploy/kubernetes/

In-cluster API auto-detected, read-only RBAC, namespace filtering, workloads (Deployments, DaemonSets, StatefulSets) as first-class citizens. Kubernetes guide.

Bare Linux, no Docker at all (systemd, amd64 and arm64, statically linked)

curl -fsSL https://install.maintenant.dev | sudo bash

Endpoints, certificates and heartbeats work without any container runtime. Container monitoring switches on by itself the moment a runtime shows up. Install documentation for pinned versions, air-gapped installs and supply-chain verification.

Cloud: one cloud-init file boots a hardened host with maintenant running on Hetzner Cloud, DigitalOcean, Scaleway, OVHcloud or Vultr.

Why maintenant?

Monitoring your own infrastructure with the standard stack means running Prometheus, Grafana, Alertmanager, node-exporter, cAdvisor, blackbox-exporter, a certificate exporter, Loki, Promtail, Trivy and something for image updates. Ten-odd components, each with its own config, upgrades and dashboards, to answer one question: is my stack up, and what is burning?

maintenant answers that question with one container.

Built into maintenant	What you would assemble instead
Container state, health checks, restart loops	cAdvisor + node-exporter + alert rules you write
CPU, memory, network and disk, per container and per host	cAdvisor + node-exporter + Grafana dashboards you build
HTTP / TCP endpoint checks, declared as Docker labels	blackbox-exporter + a config file per target
TLS certificate expiry and chain validation	ssl_exporter
Cron and heartbeat deadlines	Pushgateway + alert rules you write
Live container logs, stdout/stderr demuxed	Dozzle, or Loki + Promtail
Image update detection, with compose-aware update and rollback commands	Diun or Watchtower
Network exposure audit: `0.0.0.0` binds, exposed database ports, host network, privileged containers	nothing standard
CVE enrichment and per-container risk score (Personal)	Trivy + its exporter
Alerts routed to Discord, webhooks, email, Telegram, Slack and Teams, with escalation (Pro)	Alertmanager
Public status page with incidents and subscribers	Cachet, Uptime Kuma, or a SaaS
One real-time dashboard for all of the above	Grafana + dashboards you build and maintain

Do I still need Prometheus?

maintenant monitors your infrastructure. Prometheus monitors your application. There is no PromQL here, no custom exporters, no panels to design: maintenant already knows what a container, a certificate, an endpoint, a cron job and a CVE are, and starts watching them the moment they appear. If you ship business metrics and write your own queries, keep Prometheus for that. The two answer different questions, and plenty of people run both.

Against the tools usually stacked up next to it:

	maintenant	Uptime Kuma	Portainer	Dozzle
Container auto-discovery	Yes	No	Yes	Yes
MCP server, agent-ready	Built in	Third-party	Separate	No
Live container logs	Yes	No	Yes	Yes
HTTP/TCP endpoint checks	Yes	Yes	No	No
Cron/heartbeat monitoring	Yes	Yes	No	No
SSL certificate tracking	Yes	Yes	No	No
CPU/memory/network metrics	Yes	No	Limited	No
Image update detection	Yes	No	Yes	No
Network security insights	Yes	No	No	No
CVE enrichment, risk scoring	Personal	No	No	No
Public status page	Yes	Yes	No	No
Alerting with routing	Yes	Yes	Limited	No
Kubernetes native	Yes	No	Yes	No
Single binary, zero deps	Yes	Node.js	Docker API	Docker API
Runs without a runtime	Yes	No	No	No

One container. One dashboard. Everything monitored.

Screenshots

Dashboard: uptime, response times, resources, unified monitors

Unified alerts across every source

Security posture with CVE enrichment and risk scoring (Personal)

More screenshots

Container auto-discovery

Resources per container and per host

Endpoint monitoring

Heartbeat and cron monitoring

TLS certificate tracking

Update intelligence

Network security insights

Your AI assistant, plugged in over MCP

Status page, all operational

<img src="./docs/screen-captures/8-status-page-d

Only the beginning is shown; read the rest in the repo

maintenant

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

Quick Start

⚠️ SECURITY: publishes the UI/API (no authentication of their own) on

every interface; put an auth reverse proxy in front, or bind "127.0.0.1:8080:8080". See https://docs.maintenant.dev/security/#reverse-proxy-setup.

Why maintenant?

Screenshots