MCP servers › io.github.kOlapsis › maintenant

MCP server · registry snapshot 2026-10-24

io.github.kOlapsis/maintenant

Docker monitoring for AI agents: logs, history, alerts. Can ack alerts; never touches containers. — the publisher's description

4 of 4 record checks metversion 1.10.1Gostandard input/output, streamable HTTP

Summary

io.github.kOlapsis/maintenant is a remote and local MCP server listed in the official MCP registry at version 1.10.1.

Record checks

4 of 4 record checks met · 4 do not apply · 1 not checked

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
not checked: 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

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

Key facts

Runs: remote and local package
Transport: standard input/output, streamable HTTP
Package: Docker (OCI)
Repository: public
Last tested: not tested

Add to your client

How fresh this is

Live-tested: no
Last tested: not tested
Latest version: 1.10.1, published 2026-10-22 (registry, as of the 2026-10-24 snapshot)
First listed version: 2026-10-22 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-24
Package and repository: checked 2026-10-24

Changes since the last refresh

New in the registry: not in the list of 2026-10-23, listed on 2026-10-24 with version 1.10.1 (published 2026-10-22).

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

What it is

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

This entry needs values of your own (marked < > or { } in the config below), so there is no one-click link: paste the config and fill them in.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://{maintenant_host}/mcp

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

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

VS Code · .vscode/mcp.json

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

Claude Code

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

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

npx @modelcontextprotocol/inspector@2.11.0 --server-url "https://{maintenant_host}/mcp" --transport http

The URL contains parts in { } that the entry marks as variables; replace them with your own values.
The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

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). 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
Repository github.com/kOlapsis/maintenant	Opens publicly	matches	api.github.com · 2026-10-24

Who made it?

Feature #7 · lineage

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

Namespace: io.github.kOlapsis · 3 servers
GitHub owner: an organization (kOlapsis)

Repository: github.com/kOlapsis/maintenant
Stars: 531
Repository age: 181–365 days
Last push: 0–30 days ago
Archived: no

Source: the registry entry and api.github.com · 2026-10-24.

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

4 of 4 record checks met · 4 do not apply · 1 not checked

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.
Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
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-24. 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.kOlapsis/maintenant

Answered from the data above

Is io.github.kOlapsis/maintenant safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 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.kOlapsis/maintenant been security tested?

Not yet. Its package type is not run in our sandbox yet. This is our limit, not the server's.

Where is the source code of io.github.kOlapsis/maintenant?

In github.com/kOlapsis/maintenant, 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

Its package type is not run in our sandbox yet. This is our limit, not the server's. — our limit

Package type: oci.

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 in the weekly update

listed 2026-10-24; not classified yet

Pricing modelAI-classified

pending: added in the weekly update

the website is not read yet

Programming language

api.github.com · 2026-10-24

Hosting type

remote and local package

registry · 2026-10-24

MCP capability

not checked

not read (no session)

Transport

standard input/output, streamable HTTP

registry · 2026-10-24

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

oci

registry · 2026-10-24

Freshness

0–30 days

registry updatedAt · 2026-10-24

Lifecycle status

active

registry · 2026-10-24

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: an organization · repository age: 181–365 days · stars: 100–999

api.github.com · 2026-10-24

Maintenance

active

api.github.com · 2026-10-24

Environment

either (remote or 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.kOlapsis/maintenant: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/io.github.kOlapsis/maintenant

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.kOlapsis/maintenant)](https://protocolprobe.com/mcp/servers/io.github.kOlapsis/maintenant)

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