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
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_service_status |
Query a single service's status |
nagios_current_problems |
All hosts/services not in OK state, with duration, attempt, acknowledgement and plugin output |
nagios_program_status |
Health check on the monitoring path itself (wedged daemon, disabled notifications, stale status) -- not the same as no current problems |
nagios_acknowledge |
Acknowledge a host or service problem |
nagios_add_comment |
Add a comment to a host or service |
nagios_schedule_check |
Force an immediate re-check |
nagios_schedule_downtime |
Fixed downtime from now (5–480 min) on a host and its services, or one service, before planned work |
nagios_list_downtimes |
Downtime in effect or pending |
nagios_cancel_downtime |
End this server's own downtime when the work is done |
nagios_downtime_history |
Past and current downtime windows with author and comment, from nagios.log |
nagios_notification_history |
Recent notifications |
nagios_alert_history |
State changes rolled up per host/service, including warnings and problems that recovered by themselves; problems during scheduled downtime are totalled separately |
License
AGPL-3.0-or-later
1 maintainer
Metadata
1 maintainer
Release files for mcp-nagios-crunchtools 0.8.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mcp_nagios_crunchtools-0.8.1.tar.gz | 203.5 kB | With provenance | Details for mcp_nagios_crunchtools-0.8.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcp_nagios_crunchtools-0.8.1-py3-none-any.whl | Python 3 | none | any | Details for mcp_nagios_crunchtools-0.8.1-py3-none-any.whl |
Total release size: 239.4 kB
Release files / mcp_nagios_crunchtools-0.8.1.tar.gz
| Download URL | mcp_nagios_crunchtools-0.8.1.tar.gz |
|---|---|
| Size | 203.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
557b99c3b15fe4806efdf7d169f3d957fb42cf56c156b13f76c9124cbbebf649
|
|
BLAKE2b-256 checksum How to use checksums |
98faaafc3aed185aa77d73b1c3f80ed2eaeb0b9abed7472d56be40af3b3bdd4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / mcp_nagios_crunchtools-0.8.1-py3-none-any.whl
| Download URL | mcp_nagios_crunchtools-0.8.1-py3-none-any.whl |
|---|---|
| Size | 35.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c138ab41fdaa238a8b6f42a523dfc57759b5da2d2cf21d6be52a0a28d3884f96
|
|
BLAKE2b-256 checksum How to use checksums |
9ba1eccc948b87c0bf7fdf98118a0d4155a69dc1cca8542dbdbaebb0e48e73f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logSecurity for mcp-nagios-crunchtools 0.8.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mcp_nagios_crunchtools-0.8.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
