vibeMK
PYPI · VIBEMK
Query and configure CheckMK monitoring: hosts, services, rules, downtimes, metrics
Available components
Last scanned (1 hour ago)
Scores higher than 91% of PyPI servers
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to chexma/vibeMK). View diagnostics → Pass
- Clear OSI-approved license (GPL-3.0-or-later).Pass
- Actively maintained (last published 14 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 14466 tokens (~93/item across 154 items; 154 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (7% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 21 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 154 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 16 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +3
No change was recorded against any check on this day. Stability & Change Management went from 17 to 33. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 17. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 3 Oct 26 0
- Tool coverage: 2% → 7% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.6.3 → 0.6.4 functional
- 2 Oct 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Analysed pypi/vibemk@0.6.4
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | chexma/vibeMK |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/chexma/vibeMK/.github/workflows/release.yml@refs/tags/v0.6.4 |
| Rekor log index | 3064699377 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:3e648baab119ca9fa16a0acf1c8f33b76b158f1badbda232b8fcf9da7fbb73e3 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
vibemk_acknowledge_event Acknowledge an Event Console event. ~65
✅ Acknowledge an Event Console event.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Comment recorded with the acknowledgement |
| event_id | integer | yes | Event ID |
| site_id | string | – | Site the event lives on (optional, defaults to the connected site) |
No output schema declared.
No examples provided.
vibemk_acknowledge_host_problem Acknowledge host problem ~134
✅ Acknowledge host problem - Suppress notifications for a DOWN/UNREACHABLE host
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Why the problem is being acknowledged |
| expire_on | string | – | Optional expiry as ISO-8601, e.g. 2026-12-24T22:00:00Z |
| host_name | string | yes | Host name |
| notify | boolean | – | Send notifications to the configured contacts |
| persistent | boolean | – | Keep the comment after the acknowledgement is removed |
| sticky | boolean | – | Hold the acknowledgement until the host returns to UP |
No output schema declared.
No examples provided.
vibemk_acknowledge_problem Acknowledge problem ~123
✅ Acknowledge problem - Acknowledge host or service problem
| Name | Type | Req | Description |
|---|---|---|---|
| acknowledge_type | string | yes | Type: host or service |
| comment | string | yes | Acknowledgment comment |
| host_name | string | yes | Name of the host |
| notify | boolean | – | Send notifications to the configured contacts |
| persistent | boolean | – | Keep the comment after the acknowledgement is removed |
| service_description | string | – | Service description (for service ack) |
| sticky | boolean | – | Hold the acknowledgement until the object returns to UP/OK |
No output schema declared.
No examples provided.
vibemk_acknowledge_service_problem Acknowledge service problem ~157
✅ Acknowledge service problem - Suppress notifications for a WARN/CRIT/UNKNOWN service
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Why the problem is being acknowledged |
| expire_on | string | – | Optional expiry as ISO-8601, e.g. 2026-12-24T22:00:00Z |
| host_name | string | yes | Host name |
| notify | boolean | – | Send notifications to the configured contacts |
| persistent | boolean | – | Keep the comment after the acknowledgement is removed |
| service_description | string | yes | Service name exactly as CheckMK shows it, e.g. 'CPU utilization' |
| sticky | boolean | – | Hold the acknowledgement until the service returns to OK |
No output schema declared.
No examples provided.
vibemk_activate_changes Activate changes ~82
🔄 Activate changes - Deploy pending configuration changes. INTERNAL: vibeMK reads the ETag from pending_changes itself, so there is no manual ETag handling to do. After activating, wait for the next check cycle before results become visible.
| Name | Type | Req | Description |
|---|---|---|---|
| force_foreign_changes | boolean | – | Force activation |
| sites | array | – | List of site names |
No output schema declared.
No examples provided.
vibemk_add_comment Add comment ~77
💬 Add comment - Add comment to host or service
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | yes | Comment text |
| comment_type | string | yes | Type: host or service |
| host_name | string | yes | Host name |
| persistent | boolean | – | Persistent comment |
| service_description | string | – | Service (for service comments) |
No output schema declared.
No examples provided.
vibemk_add_user_to_group Add user to contact group ~46
👥 Add user to contact group - Assign user to contact group
| Name | Type | Req | Description |
|---|---|---|---|
| group_name | string | yes | Contact group name |
| username | string | yes | Username |
No output schema declared.
No examples provided.
vibemk_bake_agents Bake agents ~30
🍞 Bake agents - Trigger agent package baking for all hosts (CEE/Cloud only)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vibemk_baking_status Baking status ~40
🍞 Baking status - Get current agent baking status Enterprise/Cloud only: a Raw site does not serve this endpoint and answers 404.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vibemk_bulk_create_hosts Bulk create hosts ~86
➕ Bulk create hosts - Create multiple hosts in a single operation
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| bake_agent | boolean | – | Whether to bake agents after creation (CheckMK Enterprise Edition only) |
| entries | array | yes | List of hosts to create |
No output schema declared.
No examples provided.
vibemk_bulk_create_service_groups Bulk create service groups ~68
🔧 Bulk create service groups - Create multiple service groups at once
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| entries | array | yes | List of service groups to create |
No output schema declared.
No examples provided.
vibemk_bulk_delete_service_groups Bulk delete service groups ~71
🗑️ Bulk delete service groups - Delete multiple service groups at once
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| entries | array | yes | List of service group names to delete |
No output schema declared.
No examples provided.
vibemk_bulk_update_hosts Bulk update hosts ~65
🔄 Bulk update hosts - Update multiple hosts at once
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| entries | array | yes | One entry per host to change |
No output schema declared.
No examples provided.
vibemk_bulk_update_service_groups Bulk update service groups ~68
📝 Bulk update service groups - Update multiple service groups at once
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| entries | array | yes | List of service groups to update |
No output schema declared.
No examples provided.
vibemk_change_event_state Change the state of an Event Console event. ~76
🔄 Change the state of an Event Console event.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | integer | yes | Event ID |
| new_state | string | yes | New state: 'ok', 'warning', 'critical', 'unknown' |
| site_id | string | – | Site the event lives on (optional, defaults to the connected site) |
No output schema declared.
No examples provided.
vibemk_check_host_downtime_status Check host downtime status ~50
🔍 Check host downtime status - Distinguish between host-level and service-level downtimes
| Name | Type | Req | Description |
|---|---|---|---|
| host_name | string | yes | Host name to check downtime status for |
No output schema declared.
No examples provided.
vibemk_checkmk_rules_guide CheckMK Rules Guide ~50
📖 CheckMK Rules Guide - Returns the complete guide for rule management, ordering pitfalls, and API tricks. Call this BEFORE creating/modifying rules when unsure about the correct approach.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vibemk_clone_host Clone a host ~137
🔁 Clone a host - copies the folder, tags and labels of a source host onto a new target host. A different IP address can optionally be given.
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| ip_address | string | – | Optional IP address for the new host. Without it, the source host's IP is copied. |
| source_hostname | string | yes | Source host name, e.g. 'web01.example.com' |
| target_hostname | string | yes | New host name, e.g. 'web02.example.com' |
No output schema declared.
No examples provided.
vibemk_compare_host_states Compare host states ~48
🔄 Compare host states - Compare current vs desired host configuration
| Name | Type | Req | Description |
|---|---|---|---|
| desired_attributes | object | yes | Desired host attributes |
| host_name | string | yes | Name of the host |
No output schema declared.
No examples provided.
vibemk_create_aux_tag Create a new auxiliary tag. ~113
🏷️ Create a new auxiliary tag.
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| help | string | – | Help text |
| tag_id | string | yes | Unique tag ID, e.g. 'sys-linux' |
| title | string | yes | Display name, e.g. 'Linux System' |
| topic | string | – | Topic the tag is grouped under, e.g. 'Operating System' |
No output schema declared.
No examples provided.
vibemk_create_cluster_host Create cluster host ~102
🏢 Create cluster host - Create a cluster host with multiple nodes
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| attributes | object | – | Additional host attributes |
| folder | string | – | Folder path |
| host_name | string | yes | Name of the cluster host |
| nodes | array | yes | List of node hostnames for the cluster |
No output schema declared.
No examples provided.
vibemk_create_contact_group Create contact group ~78
➕ Create contact group - Add new contact group
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| alias | string | yes | Display alias |
| members | array | – | Group members |
| name | string | yes | Group name |
No output schema declared.
No examples provided.
vibemk_create_custom_check Create a custom Nagios plugin check for a host. Runs any Nagios-compatible plugin. ~166
🔧 Create a custom Nagios plugin check for a host. Runs any Nagios-compatible plugin.
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| command_line | string | yes | Plugin command line, e.g. '$USER1$/check_smtp -H $HOSTNAME$ -t 5' |
| command_name | string | – | Optional internal name for the command |
| description | string | – | Rule description, shown in WATO. Pick one that says what the rule is for. |
| folder | string | – | Checkmk folder (default: '~') |
| hostname | string | yes | Hostname |
| service_description | string | yes | Service name in the monitoring |
No output schema declared.
No examples provided.
vibemk_create_dns_check Create a DNS check for a host. Tests whether a name resolves and whether the answer arrives in time. ~229
🔎 Create a DNS check for a host. Tests whether a name resolves and whether the answer arrives in time.
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| description | string | – | Rule description shown in WATO. Pick one that says what the rule is for. |
| dns_server | string | – | DNS server IP (optional, defaults to the system resolver) |
| expect_all_addresses | boolean | – | Require every expected_addresses entry to be returned (default: false) |
| expected_addresses | string | – | Expected IP address or addresses, one or a comma-separated list (optional) |
| folder | string | – | Checkmk folder (optional) |
| hostname | string | yes | Host the rule applies to |
| lookup_hostname | string | – | Name to resolve (defaults to hostname) |
| response_time_crit | number | – | CRIT threshold in seconds (default: 0.3) |
| response_time_warn | number | – | WARN threshold in seconds (default: 0.2) |
No output schema declared.
No examples provided.
vibemk_create_folder Create folder ~79
➕ Create folder - Add new folder to the structure
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| folder | string | yes | Folder path |
| parent | string | – | Parent folder path |
| title | string | yes | Display title |
No output schema declared.
No examples provided.
vibemk_create_ftp_check Create an FTP check for a host. Tests whether an FTP port is reachable. ~158
📁 Create an FTP check for a host. Tests whether an FTP port is reachable.
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| description | string | – | Rule description shown in WATO. Pick one that says what the rule is for. |
| folder | string | – | Checkmk folder (optional) |
| hostname | string | yes | Hostname |
| port | integer | – | FTP port (default: 21) |
| refuse_state | string | – | State when the connection is refused: 'crit', 'warn', 'ok' (default: 'crit') |
| timeout | integer | – | Timeout in seconds (optional) |
No output schema declared.
No examples provided.
vibemk_create_host Create host(s) ~151
➕ Create host(s) - Add one or multiple hosts to monitoring (automatically uses bulk API for multiple hosts)
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| attributes | object | – | Host attributes - ipaddress, etc. (single host mode) |
| bake_agent | boolean | – | Whether to bake agents after creation (bulk mode only) |
| folder | string | – | Folder path (single host mode) |
| host_name | string | – | Name of the new host (single host mode) |
| hosts | array | – | List of hosts to create (multiple hosts mode - automatically uses bulk API) |
No output schema declared.
No examples provided.
vibemk_create_host_contactgroup_rule Create host contact group rule ~111
📞 Create host contact group rule - Assign contact groups to hosts based on conditions
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| comment | string | – | Rule comment |
| contact_groups | array | yes | List of contact group names to assign |
| folder | string | – | Folder path |
| host_conditions | object | – | Conditions to match hosts (optional, empty = all hosts) |
No output schema declared.
No examples provided.
vibemk_create_host_group Create host group ~69
➕ Create host group - Add new host group
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| alias | string | yes | Display alias |
| name | string | yes | Group name |
No output schema declared.
No examples provided.
vibemk_create_host_hostgroup_rule Create host group rule ~111
🏠 Create host group rule - Assign hosts to host groups based on conditions
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| comment | string | – | Rule comment |
| folder | string | – | Folder path |
| host_conditions | object | – | Conditions to match hosts (optional, empty = all hosts) |
| host_groups | array | yes | List of host group names to assign |
No output schema declared.
No examples provided.
vibemk_create_host_tag Create host tag ~108
🏷️ Create host tag - Add new host tag group
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| help | string | – | Help text |
| tag_id | string | yes | Tag group ID |
| tags | array | yes | List of tags with id and title |
| title | string | yes | Tag group title |
| topic | string | – | Tag topic/category |
No output schema declared.
No examples provided.
vibemk_create_http_check Create an HTTP/HTTPS check for a host (active_checks:http). Supports URL mode (content check, auth, timing) and certificate mode. ~649
🌐 Create an HTTP/HTTPS check for a host (active_checks:http). Supports URL mode (content check, auth, timing) and certificate mode.
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| address_family | string | – | IP version: 'ipv4' or 'ipv6' (optional) |
| auth_password | string | – | HTTP basic auth password (optional) |
| auth_user | string | – | HTTP basic auth user name (optional) |
| cert_days_crit | integer | – | CRIT this many days before the certificate expires (default: 7, cert_mode only) |
| cert_days_warn | integer | – | WARN this many days before the certificate expires (default: 14, cert_mode only) |
| cert_mode | boolean | – | Check certificate expiry instead of the URL (default: false) |
| description | string | – | Rule description shown in WATO. Pick one that says what the rule is for. |
| direct_address | string | – | Address to contact instead of the host name (optional) |
| expect_regex | string | – | Regular expression the response body must match, e.g. '"status":\s*"ok"' |
| expect_response | string | – | Expected HTTP status line, e.g. 'HTTP/1.1 200' or 'HTTP/1.1 404' |
| expect_string | string | – | Literal string the response body must contain, e.g. 'ok' or 'healthy' |
| extended_perfdata | boolean | – | Collect extended performance data such as body and header size (default: false) |
| folder | string | – | Checkmk folder (optional, defaults to the host's own folder) |
| hostname | string | yes | Host the rule applies to (Checkmk host name) |
| method | string | – | HTTP method: GET, POST, HEAD, PUT, DELETE, OPTIONS, CONNECT (default: GET) |
| name | string | – | Service name in the monitoring, e.g. 'HTTP Main' or 'API Health' |
| no_body | boolean | – | Fetch headers only, not the body (default: false) |
| onredirect | string | – | Redirect handling: 'ok', 'warning', 'critical', 'follow', 'sticky', 'stickyport' |
| port | integer | – | HTTP port (default: 80, or 443 with SSL) |
| proxy_address | string | – | HTTP proxy address (optional, e.g. 'proxy.internal') |
| proxy_port | integer | – | HTTP proxy port (default: 80) |
| response_time_crit | number | – | Response time CRIT threshold in seconds, e.g. 5.0 |
| response_time_warn | number | – | Response time WARN threshold in seconds, e.g. 2.0 |
| ssl | boolean | – | Use HTTPS/SSL (default: false) |
| timeout | integer | – | Timeout in seconds (optional) |
| uri | string | – | URL path, or a full URL (default: '/') |
| virt_host | string | – | Virtual host header, when it differs from the host name |
No output schema declared.
No examples provided.
vibemk_create_icmp_check Create an ICMP/PING check for a host. Measures reachability, packet loss and round-trip time. ~284
🏓 Create an ICMP/PING check for a host. Measures reachability, packet loss and round-trip time.
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| description | string | – | Rule description shown in WATO. Pick one that says what the rule is for. |
| explicit_address | string | – | Ping this address instead of the host name (optional) |
| folder | string | – | Checkmk folder (optional) |
| hostname | string | yes | Hostname |
| loss_crit_percent | number | – | Packet loss CRIT threshold in percent, e.g. 100 |
| loss_warn_percent | number | – | Packet loss WARN threshold in percent, e.g. 20 |
| min_pings | integer | – | Minimum number of replies for the result to count (optional) |
| name | string | – | Service name (default: 'PING') |
| packets | integer | – | Number of packets (default: 5) |
| rta_crit_ms | number | – | Round-trip time CRIT threshold in milliseconds, e.g. 500 |
| rta_warn_ms | number | – | Round-trip time WARN threshold in milliseconds, e.g. 200 |
| timeout | number | – | Timeout in seconds (default: 20) |
No output schema declared.
No examples provided.
vibemk_create_inventory_check Create a HW/SW inventory check for a host. Triggers hardware and software inventory and reports changes since the last scan. ~266
🔬 Create a HW/SW inventory check for a host. Triggers hardware and software inventory and reports changes since the last scan.
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| description | string | – | Rule description shown in WATO. Pick one that says what the rule is for. |
| fail_status | integer | – | State when the inventory fails: 0=OK, 1=WARN, 2=CRIT (default: 0) |
| folder | string | – | Checkmk folder (optional) |
| hostname | string | yes | Hostname |
| hw_changes_state | integer | – | State on hardware changes: 0=OK, 1=WARN, 2=CRIT (default: 0) |
| status_data_inventory | boolean | – | Enable status data inventory (default: true) |
| sw_changes_state | integer | – | State on software changes: 0=OK, 1=WARN, 2=CRIT (default: 0) |
| sw_missing_state | integer | – | State when software data is missing: 0=OK, 1=WARN, 2=CRIT (default: 0) |
No output schema declared.
No examples provided.
vibemk_create_ldap_check Create an LDAP check for a host. Tests the LDAP service and its response time. ~250
🗂️ Create an LDAP check for a host. Tests the LDAP service and its response time.
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| attribute | string | – | LDAP attribute or filter string (optional, e.g. '(objectclass=*)') |
| base_dn | string | yes | LDAP base DN, e.g. 'DC=example,DC=com' |
| bind_dn | string | – | Bind DN for authentication (optional) |
| description | string | – | Rule description shown in WATO. Pick one that says what the rule is for. |
| folder | string | – | Checkmk folder (optional) |
| hostname | string | yes | Hostname |
| name | string | – | Service name (default: 'LDAP') |
| password | string | – | LDAP password (optional) |
| port | integer | – | LDAP port (optional, default: 389) |
| response_time_crit_ms | number | – | Response time CRIT threshold in milliseconds (default: 800) |
| response_time_warn_ms | number | – | Response time WARN threshold in milliseconds (default: 500) |
No output schema declared.
No examples provided.
vibemk_create_mkevents_check Create an Event Console check for a host. Reports whether the Checkmk Event Console holds open events for it. ~176
📋 Create an Event Console check for a host. Reports whether the Checkmk Event Console holds open events for it.
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| description | string | – | Rule description shown in WATO. Pick one that says what the rule is for. |
| folder | string | – | Checkmk folder (optional) |
| hostname | string | yes | Hostname |
| ignore_acknowledged | boolean | – | Ignore acknowledged events (default: true) |
| remote_ec_host | string | – | IP or host of an external Event Console (optional) |
| show_last_log | string | – | 'summary' (in the service summary), 'details' or 'no' (default: 'summary') |
No output schema declared.
No examples provided.
vibemk_create_notification_rule Create notification rule ~91
➕ Create notification rule - CheckMK requires the complete rule_config structure (properties, contact selection, conditions and notification_method), and nearly every field is mandatory. Read an existing rule with vibemk_get_notification_rule and adapt its rule_config rather than composing one from scratch. Activate changes afterwards.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_config | object | yes | Complete rule configuration as returned by vibemk_get_notification_rule |
No output schema declared.
No examples provided.
vibemk_create_password Create password ~116
🔐 Create password - Store new password securely
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| comment | string | – | Password description |
| documentation_url | string | – | Documentation URL |
| ident | string | yes | Password identifier |
| owner | string | – | Owner user/group |
| password | string | yes | Password value |
| shared | array | – | Shared with users/groups |
| title | string | – | Password title |
No output schema declared.
No examples provided.
vibemk_create_rule Create rule ~154
➕ Create rule - Add new monitoring rule
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| comment | string | – | Rule comment |
| conditions | object | – | Rule conditions |
| folder | string | – | Target folder |
| position | string | – | Where to place the new rule. Omit to leave placement to CheckMK. The two *_specific_rule values need target_rule_id. |
| rule_config | object | yes | Rule configuration |
| ruleset_name | string | yes | Ruleset name |
| target_rule_id | string | – | Rule to position relative to, for before_specific_rule/after_specific_rule |
No output schema declared.
No examples provided.
vibemk_create_service_group Create service group ~92
🔧 Create service group - Create a new service group for organizing services
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| alias | string | yes | Human-readable description/alias for the service group |
| name | string | yes | Service group name (letters, numbers, hyphens, underscores only) |
No output schema declared.
No examples provided.
vibemk_create_smb_check Create an SMB/CIFS share check for a host. Tests availability and used space of a Windows network share. ~225
🖥️ Create an SMB/CIFS share check for a host. Tests availability and used space of a Windows network share.
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| crit_percent | number | – | Used space CRIT threshold in percent (default: 95) |
| description | string | – | Rule description shown in WATO. Pick one that says what the rule is for. |
| folder | string | – | Checkmk folder (optional) |
| hostname | string | yes | Hostname |
| password | string | – | SMB password (optional) |
| share | string | yes | Share name without backslashes, e.g. 'public' |
| smb_host | string | – | SMB host IP or name (default: 'use_parent_host') |
| username | string | – | SMB user name (optional) |
| warn_percent | number | – | Used space WARN threshold in percent (default: 85) |
| workgroup | string | – | Workgroup or domain (optional) |
No output schema declared.
No examples provided.
vibemk_create_smtp_check Create an SMTP check for a host. Tests the SMTP service, optionally STARTTLS and certificate expiry. ~253
📧 Create an SMTP check for a host. Tests the SMTP service, optionally STARTTLS and certificate expiry.
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| cert_days_crit | integer | – | CRIT this many days before the certificate expires (default: 7, with starttls or check_cert) |
| cert_days_warn | integer | – | WARN this many days before the certificate expires (default: 14, with starttls or check_cert) |
| check_cert | boolean | – | Check the certificate only, without STARTTLS (default: false) |
| description | string | – | Rule description shown in WATO. Pick one that says what the rule is for. |
| folder | string | – | Checkmk folder (optional) |
| hostname | string | yes | Hostname |
| name | string | – | Service name (default: 'SMTP') |
| port | integer | – | SMTP port, e.g. 587 for submission or 465 for SMTPS (default: the check's own, 25) |
| starttls | boolean | – | Use STARTTLS and check the certificate (default: false) |
No output schema declared.
No examples provided.
vibemk_create_tcp_check Create a TCP port check for a host. Tests reachability, optionally the response content, and the SSL certificate. ~321
🔌 Create a TCP port check for a host. Tests reachability, optionally the response content, and the SSL certificate.
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| cert_days_crit | integer | – | CRIT this many days before the certificate expires (ssl=true only) |
| cert_days_warn | integer | – | WARN this many days before the certificate expires (ssl=true only) |
| description | string | – | Rule description shown in WATO. Pick one that says what the rule is for. |
| expect | string | – | String expected in the TCP response, e.g. 'SSH-2.0' or 'Connection refused' |
| folder | string | – | Checkmk folder (optional) |
| hostname | string | yes | Hostname |
| mismatch_state | string | – | State when the expected string does not match: 'ok', 'warn', 'crit' |
| name | string | – | Optional service name |
| port | integer | yes | TCP port, e.g. 8080 |
| refuse_state | string | – | State when the port refuses the connection: 'ok', 'warn', 'crit' (default: 'crit') |
| response_time_crit | number | – | Response time CRIT threshold in seconds |
| response_time_warn | number | – | Response time WARN threshold in seconds |
| ssl | boolean | – | Use SSL/TLS (default: false) |
| timeout | integer | – | Timeout in seconds (optional) |
No output schema declared.
No examples provided.
vibemk_create_timeperiod Create time period ~105
⏰ Create time period - Add new time period
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| active_time_ranges | array | yes | Active time ranges |
| alias | string | – | Time period alias |
| exceptions | array | – | Exception time ranges |
| exclude | array | – | Excluded time periods |
| name | string | yes | Time period name |
No output schema declared.
No examples provided.
vibemk_create_user Create user ~79
👤 Create user - Add new CheckMK user
| Name | Type | Req | Description |
|---|---|---|---|
| contactgroups | array | – | Contact groups to assign user to |
| string | – | Email address | |
| fullname | string | yes | Full name |
| password | string | – | Password |
| roles | array | – | User roles |
| username | string | yes | Username |
No output schema declared.
No examples provided.
vibemk_create_user_role Create user role ~114
➕ Create user role - Clone an existing role to create a new custom role
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| base_role_id | string | yes | Existing role ID to clone from (e.g., 'admin', 'user', 'guest') |
| new_alias | string | – | Display name/alias for the new role |
| new_role_id | string | yes | ID for the new role |
No output schema declared.
No examples provided.
vibemk_debug_api_endpoints Debug API endpoints ~29
🔍 Debug API endpoints - Analyze available CheckMK API endpoints and their structure
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vibemk_debug_checkmk_connection CheckMK connection diagnostics ~27
🔍 CheckMK connection diagnostics - Test server connectivity and API access
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vibemk_debug_permissions Debug permissions ~24
🔐 Debug permissions - Check automation user permissions for API access
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vibemk_debug_url_detection Debug URL detection ~26
🔍 Debug URL detection - Show all tested URL patterns and results
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the vibeMK MCP server?
vibeMK runs locally as a PyPI package, launched with uvx vibemk. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · vibemk
claude mcp add chexma-vibemk -- uvx vibemk
What is the vibeMK MCP server?
vibeMK is an MCP server listed in the public MCP registry as io.github.chexma/vibemk. Query and configure CheckMK monitoring: hosts, services, rules, downtimes, metrics. This page covers its PyPI package (vibemk).
Is the vibeMK MCP server safe to use?
vibeMK scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the vibeMK MCP server expose?
vibeMK exposes 154 tools: vibemk_debug_checkmk_connection, vibemk_debug_url_detection, vibemk_test_direct_url, vibemk_test_all_endpoints, vibemk_get_checkmk_version, and 149 more. Their descriptions and schemas cost roughly 14,466 tokens of context every time the server is loaded.
Is the vibeMK MCP server still maintained?
vibeMK is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the vibeMK MCP server under?
vibeMK declares the GPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.