Secure MCP server for Nagios Core monitoring — query status, acknowledge problems, manage checks
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-nagios-crunchtools","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# mcp-nagios-crunchtools Secure MCP server for Nagios Core monitoring. Query host and service status, acknowledge problems, add comments, schedule forced checks, and read notification history. ## Installation ```bash uvx mcp-nagios-crunchtools ``` ## Configuration | Variable | Required | Description | |----------|----------|-------------| | `NAGIOS_URL` | Yes | Base URL (e.g., `https://nagios.example.com`) | | `NAGIOS_USER` | Yes | HTTP Basic Auth username | | `NAGIOS_PASS` | Yes | HTTP Basic Auth password | | `NAGIOS_COMMENT_AUTHOR` | No | Author recorded on acknowledgements and comments. Defaults to `NAGIOS_USER`. Not a tool parameter. | | `NAGIOS_CGI_PREFIX` | No | Path under `NAGIOS_URL` where the CGI scripts are served. Defaults to `/nagios/cgi-bin`. Set to `/cgi-bin` for a Nagios served at the web root. A trailing slash is ignored. | | `NAGIOS_LOG_PATH` | No | Read-only path to `nagios.log`. Enables `nagios_downtime_history` and the planned-work split in `nagios_alert_history`; archivejson.cgi never returns downtime entries. | | `TZ` | Effectively yes | The container's local timezone. Must match the Nagios server's own timezone. | ### Why `TZ` matters `schedule_check` submits a `start_time` to `cmd.cgi`, which parses it as naive wall-clock time in the Nagios server's local timezone — there is no offset field to send. The value is therefore built with `time.localtime()`, so this container must run in the same timezone as the Nagios server. When it does not, forced checks are silently scheduled into the future by the offset between the two — four hours against an EDT server — and "check now" appears to do nothing at all. No error is raised. This was a real defect, fixed in 0.1.2 by switching from `gmtime()` to `localtime()`; the timezone assumption it introduced is why `TZ` belongs in this table rather than being left implicit. ## Tools | Tool | Description | |------|-------------| | `nagios_host_status` | Query a single host's status | | `nagios_serv…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.