vibeMK
PYPI · VIBEMK
Query and configure CheckMK monitoring: hosts, services, rules, downtimes, metrics
Available components
Last scanned (2 hours 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_get_rulesets List rulesets ~36
📋 List rulesets - Show available rulesets
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | – | Search term to filter rulesets |
No output schema declared.
No examples provided.
vibemk_get_service_group Get service group details ~40
🔍 Get service group details - Show detailed information about a specific service group
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Service group name to retrieve |
No output schema declared.
No examples provided.
vibemk_get_service_groups List service groups ~23
🔧 List service groups - Show all service groups
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vibemk_get_service_metrics Get service metrics ~132
📊 Get service metrics - Extract service performance data from CheckMK metrics API
| Name | Type | Req | Description |
|---|---|---|---|
| host_name | string | yes | Host name |
| metric_name | string | – | Specific metric ID (e.g., 'if_in_bps', 'cpu_util') |
| reduce | string | – | Aggregation function: 'max', 'min', 'average' |
| service_description | string | yes | Service description |
| site | string | – | CheckMK site name |
| time_range | string | – | Time range: '1h', '4h', '24h', '7d', '30d' |
| Name | Type | Req | Description |
|---|---|---|---|
| available_metrics | array | – | Present when listing: the IDs metric_name accepts |
| end | string|null | – | – |
| host_name | string | yes | – |
| metric_id | string|null | – | null when listing what is available |
| series | array | yes | – |
| service_description | string|null | – | null for a host metric |
| start | string|null | – | Window CheckMK actually used, ISO 8601 |
| step | integer|null | – | Seconds per data point |
| time_range | string | – | – |
No examples provided.
vibemk_get_service_status Get service status ~47
📊 Get service status - Show current status of a service
| Name | Type | Req | Description |
|---|---|---|---|
| host_name | string | yes | Name of the host |
| service_description | string | yes | Service description |
| Name | Type | Req | Description |
|---|---|---|---|
| host_name | string | yes | – |
| is_hard_state | boolean | – | Whether CheckMK considers the state settled |
| last_check | integer|null | – | Unix timestamp, or null when CheckMK reported none |
| last_state_change | integer|null | – | Unix timestamp, or null when CheckMK reported none |
| plugin_output | string | – | What the check itself reported |
| service_description | string | yes | – |
| state | string | yes | Monitoring state; UNAVAILABLE when CheckMK reported none (UNKNOWN is a real state) |
| state_code | integer|null | yes | 0 OK, 1 WARNING, 2 CRITICAL, 3 UNKNOWN |
No examples provided.
vibemk_get_sites List monitoring sites: every configured Checkmk instance in a distributed setup. ~27
🌐 List monitoring sites: every configured Checkmk instance in a distributed setup.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vibemk_get_timeperiods List time periods ~26
⏰ List time periods - Show all configured time periods
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vibemk_get_users List users ~22
👥 List users - Show all CheckMK users
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vibemk_list_acknowledgements List acknowledgements ~29
📋 List acknowledgements - Show all currently acknowledged host and service problems
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vibemk_list_active_checks List active check rules, optionally filtered by host or check type. ~78
🔍 List active check rules, optionally filtered by host or check type.
| Name | Type | Req | Description |
|---|---|---|---|
| check_type | string | – | Type: 'http', 'tcp', 'icmp', 'dns', 'smtp', 'custom' (optional, all types when empty) |
| hostname | string | – | Show only rules for this host name (optional) |
No output schema declared.
No examples provided.
vibemk_list_available_metrics List available metrics ~52
📋 List available metrics - Show all available metrics for host or service
| Name | Type | Req | Description |
|---|---|---|---|
| host_name | string | yes | Host name |
| service_description | string | – | Service description (optional for service metrics) |
| Name | Type | Req | Description |
|---|---|---|---|
| available_metrics | array | yes | – |
| host_name | string | yes | – |
| metric_id | null | – | – |
| series | array | – | – |
| service_description | string|null | – | – |
No examples provided.
vibemk_list_downtimes List downtimes ~83
📋 List downtimes - Show all scheduled downtimes with filtering options
| Name | Type | Req | Description |
|---|---|---|---|
| active_only | boolean | – | Show only active downtimes (default: true) |
| host_name | string | – | Optional: Filter downtimes for specific host |
| service_description | string | – | Optional: Filter downtimes for specific service |
| Name | Type | Req | Description |
|---|---|---|---|
| downtimes | array | yes | – |
| total | integer | yes | – |
No examples provided.
vibemk_list_process_rules List process monitoring rules (inventory_processes_rules): which processes are monitored on which hosts, and at what thresholds. ~68
🔍 List process monitoring rules (inventory_processes_rules): which processes are monitored on which hosts, and at what thresholds.
| Name | Type | Req | Description |
|---|---|---|---|
| hostname | string | – | Show only rules for this host (optional) |
| process_name | string | – | Show only rules for this process (optional) |
No output schema declared.
No examples provided.
vibemk_list_rulesets List all rulesets ~58
📋 List all rulesets - Show all available rulesets with basic information
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of rulesets to return |
| show_deprecated | boolean | – | Include deprecated rulesets in the list |
No output schema declared.
No examples provided.
vibemk_list_service_groups List service groups ~24
📋 List service groups - Show all configured service groups
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vibemk_list_user_roles List user roles ~51
👥 List user roles - Show all available user roles (built-in and custom)
| Name | Type | Req | Description |
|---|---|---|---|
| show_builtin | boolean | – | Include built-in roles (admin, user, guest) in the list |
No output schema declared.
No examples provided.
vibemk_login_site Log in to a remote site (distributed monitoring). ~60
🔑 Log in to a remote site (distributed monitoring).
| Name | Type | Req | Description |
|---|---|---|---|
| password | string | yes | Password |
| site_id | string | yes | Site ID, e.g. 'uel' or 'ham' |
| username | string | yes | User name |
No output schema declared.
No examples provided.
vibemk_logout_site Log out of a remote site. ~30
🚪 Log out of a remote site.
| Name | Type | Req | Description |
|---|---|---|---|
| site_id | string | yes | Site ID |
No output schema declared.
No examples provided.
vibemk_modify_downtime Modify downtime ~138
✏️ Modify downtime - Extend or shorten an active downtime's end time
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | New comment (optional) |
| downtime_id | integer | – | Downtime ID to modify (use vibemk_list_downtimes to find it) |
| end_time | string | yes | New end time in ISO 8601 format, e.g. '2026-06-09T18:00:00Z' |
| host_name | string | – | Host name for query-based modification (alternative to downtime_id) |
| service_description | string | – | Service description (optional, narrows query-based modification) |
No output schema declared.
No examples provided.
vibemk_move_folder Move folder ~72
📁 Move folder - Move folder to different parent
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| destination | string | yes | New parent folder path |
| folder | string | yes | Folder path to move |
No output schema declared.
No examples provided.
vibemk_move_host Move host ~73
📁 Move host - Move host to different folder
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| host_name | string | yes | Name of the host |
| target_folder | string | yes | Target folder path |
No output schema declared.
No examples provided.
vibemk_move_rule Move rule ~107
🔄 Move rule - Change rule position in ruleset
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| position | string | – | Where to move the rule. The two *_specific_rule values need target_rule_id. |
| rule_id | string | yes | Rule ID |
| target_rule_id | string | – | Rule to position relative to, for before_specific_rule/after_specific_rule |
No output schema declared.
No examples provided.
vibemk_remove_acknowledgement Remove acknowledgement ~120
🗑️ Remove acknowledgement - Delete by ID, by host/service, or by comment pattern
| Name | Type | Req | Description |
|---|---|---|---|
| acknowledgement_id | string | – | Acknowledgement ID from list_acknowledgements |
| comment_pattern | string | – | Remove acknowledgements whose comment contains this text |
| delete_all_matching | boolean | – | Remove every match instead of only the first (default: false) |
| host_name | string | – | Remove the acknowledgement on this host |
| service_description | string | – | Restrict removal to this service on the host |
No output schema declared.
No examples provided.
vibemk_remove_user_from_group Remove user from contact group ~46
👥 Remove user from contact group - Remove user from 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_rename_host Rename host ~56
✏️ Rename host - Rename a host in CheckMK (starts a background job)
| Name | Type | Req | Description |
|---|---|---|---|
| host_name | string | yes | Current host name |
| new_name | string | yes | New host name (FQDN) |
No output schema declared.
No examples provided.
vibemk_schedule_downtime Schedule downtime ~102
⏰ Schedule downtime - Schedule maintenance downtime
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | yes | Downtime comment |
| downtime_type | string | yes | Type: host, service, or hostgroup |
| end_time | string | yes | End time (ISO format) |
| host_name | string | – | Name of the host |
| service_description | string | – | Service description (for service downtime) |
| start_time | string | yes | Start time (ISO format) |
No output schema declared.
No examples provided.
vibemk_schedule_host_downtime Schedule host downtime ~273
🔧 Schedule host downtime - Schedule maintenance downtime for a host to suppress alerts
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Comment describing the reason for downtime. Default: 'Scheduled maintenance' |
| duration | integer|string | – | Downtime duration - supports natural language: '2h', '1h30m', '90m' or minutes as integer. Default: 60 |
| end_time | string | – | End time - supports natural language: '23:30 today', 'tomorrow at 16:00', 'monday at 17:00', or relative like '+2h'. Optional if duration specified |
| force | boolean | – | Schedule even if a downtime with the same comment already exists. Default: false |
| host_name | string | yes | Host name to schedule downtime for |
| recur | string | – | Repeat the downtime. Commercial editions only: a Raw/Community site accepts it but schedules the downtime once. Default: once |
| start_time | string | – | Start time - supports natural language: '22:00 today', 'tomorrow at 14:00', 'monday at 09:00', '2024-08-23 at 22:00', 'in 2 hours', 'now', or ISO format. Default: now |
No output schema declared.
No examples provided.
vibemk_schedule_service_downtime Schedule service downtime ~288
🔧 Schedule service downtime - Schedule maintenance downtime for specific services
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Comment describing the reason for downtime. Default: 'Scheduled service maintenance' |
| duration | integer|string | – | Downtime duration - supports natural language: '2h', '1h30m', '90m' or minutes as integer. Default: 60 |
| end_time | string | – | End time - supports natural language: '23:30 today', 'tomorrow at 16:00', 'monday at 17:00', or relative like '+2h'. Optional if duration specified |
| force | boolean | – | Schedule even if a downtime with the same comment already exists. Default: false |
| host_name | string | yes | Host name where services are located |
| recur | string | – | Repeat the downtime. Commercial editions only: a Raw/Community site accepts it but schedules the downtime once. Default: once |
| service_descriptions | array | yes | List of service descriptions to schedule downtime for |
| start_time | string | – | Start time - supports natural language: '22:00 today', 'tomorrow at 14:00', 'monday at 09:00', '2024-08-23 at 22:00', 'in 2 hours', 'now', or ISO format. Default: now |
No output schema declared.
No examples provided.
vibemk_search_metrics Search metrics ~197
🔍 Search metrics - Read one predefined graph (graph_id) or one metric (metric_id) across the hosts and services a filter matches. Exactly one of the two IDs is required; both are shown in the service view once 'Show internal IDs' is enabled in its display options. Enterprise/Cloud only: a Raw site does not serve this endpoint and answers 404.
| Name | Type | Req | Description |
|---|---|---|---|
| graph_id | string | – | ID of a predefined graph, e.g. cmk_cpu_time_by_phase. Exclusive with metric_id |
| host_filter | string | yes | Host filter pattern |
| metric_id | string | – | ID of a single metric, e.g. cmk_time_agent. Exclusive with graph_id |
| reduce | string | – | Aggregation function |
| service_filter | string | – | Service filter pattern (optional) |
| site_filter | string | – | Site filter (optional) |
| time_range | string | – | Time range |
No output schema declared.
No examples provided.
vibemk_search_rulesets Search rulesets ~118
🔍 Search rulesets - Find rulesets with filters (text, folder, name)
| Name | Type | Req | Description |
|---|---|---|---|
| deprecated | boolean | – | Only show deprecated rulesets |
| folder | string | – | The folder in which to search for rules. Path delimiters can be ~, /, or \ |
| fulltext | string | – | Search all keys (name, title, help) for this text. Regex allowed. |
| name | string | – | A regex of the ruleset name |
| used | boolean | – | Only show used rulesets |
No output schema declared.
No examples provided.
vibemk_set_interface_params Override interface parameters for a Checkmk host (checkgroup_parameters:interfaces). Typically used to set the expected speed and clear an 'expected speed' WARN. Example: interface vmbr1 warns becaus… ~286
🌐 Override interface parameters for a Checkmk host (checkgroup_parameters:interfaces). Typically used to set the expected speed and clear an 'expected speed' WARN. Example: interface vmbr1 warns because 10 Gbit/s is expected and 1 Gbit/s is real; expected_speed_mbit=1000 sets the expectation to 1 Gbit/s. RULE ORDER: the new rule is created in the host's own folder, not in root, so that subfolder precedence applies. Only activate_changes is needed, no service discovery.
| 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 (optional) |
| expected_speed_mbit | integer | yes | Expected interface speed in Mbit/s. Typical values: 10, 100, 1000 (1 Gbit/s), 10000 (10 Gbit/s). |
| folder | string | – | Checkmk folder (optional, defaults to the host's own folder) |
| hostname | string | yes | Checkmk host name, e.g. 'web01.example.com' |
| interface_name | string | yes | Interface name, e.g. 'vmbr1', 'eth0' or 'bond0'. A leading 'Interface ' is stripped if present. |
No output schema declared.
No examples provided.
vibemk_set_memory_thresholds Set memory thresholds for a host (checkgroup_parameters:memory_linux), creating a rule for RAM and/or swap usage. IMPORTANT, the memory keys are: RAM = levels_virtual (not 'levels'), swap = levels_sw… ~324
💾 Set memory thresholds for a host (checkgroup_parameters:memory_linux), creating a rule for RAM and/or swap usage. IMPORTANT, the memory keys are: RAM = levels_virtual (not 'levels'), swap = levels_swap, physical RAM = levels_ram, committed = levels_committed. RULE ORDER: the new rule is created in the host's own folder, not in root. Check with vibemk_get_ruleset whether a rule for this host already exists and update it with vibemk_update_rule rather than adding a second one. Only activate_changes is needed.
| 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 (optional) |
| folder | string | – | Checkmk folder (optional, defaults to the host's own folder) |
| hostname | string | yes | Checkmk host name, e.g. 'web01.example.com' |
| ram_crit_percent | number | – | Total virtual memory CRIT in percent (levels_virtual, e.g. 95). Required when ram_warn is set. |
| ram_warn_percent | number | – | Total virtual memory WARN in percent (levels_virtual, e.g. 90). Optional. |
| swap_crit_percent | number | – | Swap usage CRIT threshold in percent (e.g. 50). Required when swap_warn is set. |
| swap_warn_percent | number | – | Swap usage WARN threshold in percent (e.g. 30). Optional. |
No output schema declared.
No examples provided.
vibemk_set_process_thresholds Create process monitoring with thresholds for a host (inventory_processes_rules). The rule defines which processes are watched and how many instances trigger WARN and CRIT. A service discovery runs a… ~538
⚙️ Create process monitoring with thresholds for a host (inventory_processes_rules). The rule defines which processes are watched and how many instances trigger WARN and CRIT. A service discovery runs afterwards so the thresholds take effect immediately. Example: 'Process wnscli.exe' on host X should warn at >=10 instances and go critical at >=12.
| Name | Type | Req | Description |
|---|---|---|---|
| activate_changes | boolean | – | Activate the changes immediately after the operation (default: false). Ask the user first whether they want that. |
| cpu_average_min | integer | – | Average CPU over N minutes instead of using the instantaneous value (optional, e.g. 15) |
| cpu_crit_percent | number | – | Total CPU usage CRIT threshold in percent (optional, e.g. 95) |
| cpu_warn_percent | number | – | Total CPU usage WARN threshold in percent (optional, e.g. 80) |
| crit_max | integer | yes | CRITICAL when more than this many processes run (e.g. 12) |
| crit_min | integer | – | CRITICAL when fewer than this many processes run (default: 1) |
| description | string | – | Rule description shown in WATO. Pick one that says what the rule is for. |
| folder | string | – | Checkmk folder (optional, defaults to the host's own folder) |
| hostname | string | yes | Checkmk host name the rule applies to |
| mem_crit_mb | integer | – | Virtual memory CRIT threshold in MB (optional) |
| mem_warn_mb | integer | – | Virtual memory WARN threshold in MB (optional) |
| process_name | string | yes | Process name, e.g. 'wnscli.exe', 'nginx' or 'java'. Used both as the process match and as the service name. A leading 'Process ' is stripped if present. |
| resident_crit_mb | integer | – | Resident memory (RSS) CRIT threshold in MB (optional) |
| resident_warn_mb | integer | – | Resident memory (RSS) WARN threshold in MB (optional) |
| run_discovery | boolean | – | Run a service discovery after creating the rule (default: true). Set it to false only when creating several rules at once. |
| single_cpu_crit_percent | number | – | Per-process CPU usage CRIT threshold in percent (optional) |
| single_cpu_warn_percent | number | – | Per-process CPU usage WARN threshold in percent (optional) |
| warn_max | integer | yes | WARNING when more than this many processes run (e.g. 10) |
| warn_min | integer | – | WARNING when fewer than this many processes run (default: 1) |
No output schema declared.
No examples provided.
vibemk_show_ruleset Show ruleset details ~53
📋 Show ruleset details - Display detailed information about a specific ruleset
| Name | Type | Req | Description |
|---|---|---|---|
| ruleset_name | string | yes | The name of the ruleset (e.g., host_groups, host_contactgroups) |
No output schema declared.
No examples provided.
vibemk_show_user_role Show user role details ~44
🔍 Show user role details - Display detailed information about a specific user role
| Name | Type | Req | Description |
|---|---|---|---|
| role_id | string | yes | ID of the role to show details for |
No output schema declared.
No examples provided.
vibemk_start_bulk_discovery Start bulk discovery ~89
🔍 Start bulk discovery - Discover services on multiple hosts simultaneously
| Name | Type | Req | Description |
|---|---|---|---|
| bulk_size | integer | – | Number of hosts to process simultaneously |
| do_full_scan | boolean | – | Perform full service scan |
| hostnames | array | yes | List of host names to discover services on |
| ignore_errors | boolean | – | Continue on errors |
| options | object | – | Discovery options |
No output schema declared.
No examples provided.
vibemk_start_service_discovery Start service discovery ~70
🔍 Start service discovery - Automatically detect services on a host
| Name | Type | Req | Description |
|---|---|---|---|
| host_name | string | yes | Host name to discover services on |
| mode | string | – | Discovery mode. 'tabula_rasa' removes every service and rediscovers, so it is the destructive one. |
No output schema declared.
No examples provided.
vibemk_test_all_endpoints Test all API endpoints ~26
🧪 Test all API endpoints - Comprehensive endpoint availability check
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vibemk_test_direct_url Test direct URL ~82
🧪 Test direct URL - Send a GET to a URL under the configured CheckMK API and show the raw response. URLs on other hosts or outside the API path are refused.
| Name | Type | Req | Description |
|---|---|---|---|
| test_url | string | yes | Full URL to test (e.g., http://localhost:8080/cmk/check_mk/api/1.0/version) |
No output schema declared.
No examples provided.
vibemk_update_aux_tag Update an auxiliary tag. ~88
🏷️ Update an 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 | – | New help text |
| tag_id | string | yes | Tag ID |
| title | string | – | New display name |
| topic | string | – | New topic |
No output schema declared.
No examples provided.
vibemk_update_contact_group Update contact group ~78
📝 Update contact group - Modify contact group properties
| 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 | – | Display alias |
| members | array | – | Group members |
| name | string | yes | Group name |
No output schema declared.
No examples provided.
vibemk_update_folder Update folder ~76
📝 Update folder - Modify folder properties
| 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 | – | Folder attributes |
| folder | string | yes | Folder path |
| title | string | – | New display title |
No output schema declared.
No examples provided.
vibemk_update_host Update host ~121
📝 Update host - Modify host configuration with flexible attribute management
| 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 | – | Updated attributes |
| host_name | string | yes | Name of the host |
| remove_attributes | array | – | List of attribute names to remove (used with remove mode) |
| update_mode | string | – | Update mode: 'update' (merge), 'overwrite' (replace), 'remove' (delete attributes) |
No output schema declared.
No examples provided.
vibemk_update_host_group Update host group ~69
📝 Update host group - Modify host group properties
| 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 | – | Display alias |
| name | string | yes | Group name |
No output schema declared.
No examples provided.
vibemk_update_host_tag Update host tag ~115
📝 Update host tag - Modify 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 |
| repair | boolean | – | Repair host assignments |
| tag_id | string | yes | Tag group ID |
| tags | array | – | List of tags with id and title |
| title | string | – | Tag group title |
| topic | string | – | Tag topic/category |
No output schema declared.
No examples provided.
vibemk_update_notification_rule Update notification rule ~75
✏️ Update notification rule - Replaces the rule's configuration. Send the complete rule_config, not just the fields you want changed; read the current one first. Activate changes afterwards.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_config | object | yes | Complete replacement configuration |
| rule_id | string | yes | Rule ID from get_notification_rules |
No output schema declared.
No examples provided.
vibemk_update_password Update password ~115
📝 Update password - Modify stored password
| 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 | – | Password value |
| shared | array | – | Shared with users/groups |
| title | string | – | Password title |
No output schema declared.
No examples provided.
vibemk_update_rule Update rule ~96
📝 Update rule - Modify existing 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 |
| disabled | boolean | – | Disable rule |
| rule_config | object | – | Rule configuration |
| rule_id | string | yes | Rule ID |
No output schema declared.
No examples provided.
vibemk_update_service_group Update service group ~80
📝 Update service group - Modify an existing service group's alias
| 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 | New alias/description for the service group |
| name | string | yes | Service group name to update |
No output schema declared.
No examples provided.
vibemk_update_timeperiod Update time period ~104
📝 Update time period - Modify time period configuration
| 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 | – | 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.
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.