vibeMK runs on your own machine — the client starts it, so there is no endpoint to ping. 206 installs a week from pypi. Last commit 3 Oct 2026.
Query and configure CheckMK monitoring: hosts, services, rules, downtimes, metrics
What the code does
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
этот файл ставится пользователю, но в репозитории его нет
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add vibemk -e 'CHECKMK_SERVER_URL=<CHECKMK_SERVER_URL>' -e 'CHECKMK_SITE=<CHECKMK_SITE>' -e 'CHECKMK_USERNAME=<CHECKMK_USERNAME>' -e 'CHECKMK_PASSWORD=<CHECKMK_PASSWORD>' -- uvx vibemk{
"mcpServers": {
"vibemk": {
"command": "uvx",
"args": [
"vibemk"
],
"env": {
"CHECKMK_PASSWORD": "<CHECKMK_PASSWORD>",
"CHECKMK_SERVER_URL": "<CHECKMK_SERVER_URL>",
"CHECKMK_SITE": "<CHECKMK_SITE>",
"CHECKMK_USERNAME": "<CHECKMK_USERNAME>"
}
}
}
}[mcp_servers.vibemk]
command = "uvx"
args = ["vibemk"]
env = { CHECKMK_SERVER_URL = "<CHECKMK_SERVER_URL>", CHECKMK_SITE = "<CHECKMK_SITE>", CHECKMK_USERNAME = "<CHECKMK_USERNAME>", CHECKMK_PASSWORD = "<CHECKMK_PASSWORD>" }{
"mcpServers": {
"vibemk": {
"command": "uvx",
"args": [
"vibemk"
],
"env": {
"CHECKMK_PASSWORD": "<CHECKMK_PASSWORD>",
"CHECKMK_SERVER_URL": "<CHECKMK_SERVER_URL>",
"CHECKMK_SITE": "<CHECKMK_SITE>",
"CHECKMK_USERNAME": "<CHECKMK_USERNAME>"
}
}
}
}{
"servers": {
"vibemk": {
"type": "stdio",
"command": "uvx",
"args": [
"vibemk"
],
"env": {
"CHECKMK_PASSWORD": "<CHECKMK_PASSWORD>",
"CHECKMK_SERVER_URL": "<CHECKMK_SERVER_URL>",
"CHECKMK_SITE": "<CHECKMK_SITE>",
"CHECKMK_USERNAME": "<CHECKMK_USERNAME>"
}
}
}
}Put your own values in place of
<CHECKMK_SERVER_URL> (CheckMK server URL, e.g. https://monitoring.example.com), <CHECKMK_SITE> (CheckMK site name, e.g. cmk), <CHECKMK_USERNAME> (CheckMK automation user), <CHECKMK_PASSWORD> (Automation secret of that user).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
CHECKMK_VERIFY_SSL (Verify the server's TLS certificate), NEVER_ACTIVATE_CHANGES (Never activate configuration changes in CheckMK), VIBEMK_READ_ONLY (Offer only the tools that read and refuse every write).
Alternatives to vibeMK
same job, measured the same wayopenITCOCKPIT monitoring: host and service state, history, downtimes, acknowledgements, patches
Monitor uptime, manage incidents, configure alerting, and query dependency status via DevHelm
Ecosystem monitoring: service status and x402 activity metrics
Connect AI assistants to Xitoring monitoring: servers, uptime, incidents, metrics, SSL, and alerts.
Set up uptime monitoring from your editor: create checks, alerts, and query uptime. Can sign you up.
MCP for ROS 2 monitoring, debugging, and managing nodes, topics, services, and TF2 frames.
MCP server for LibreNMS network monitoring - query devices, ports, alerts, and manage infrastructure
Redis health, BullMQ queue monitoring, memory analysis, and slow query diagnostics
vibeMK — questions
Answers built from our own checks of this server.