vibeMK
PYPI · VIBEMK
Query and configure CheckMK monitoring: hosts, services, rules, downtimes, metrics
Available components
Last scanned (3 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_update_user Update user ~69
📝 Update user - Modify user properties
| Name | Type | Req | Description |
|---|---|---|---|
| contactgroups | array | – | Contact groups to assign user to |
| string | – | Email address | |
| fullname | string | – | Full name |
| roles | array | – | User roles |
| username | string | yes | Username |
No output schema declared.
No examples provided.
vibemk_update_user_role Update user role ~100
✏️ Update user role - Modify an existing user role's alias or permissions
| 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 | – | New display name/alias for the role |
| permissions | object | – | Permission dictionary (permission_id: boolean) |
| role_id | string | yes | ID of the role to update |
No output schema declared.
No examples provided.
vibemk_validate_host_config Validate host config ~71
✅ Validate host config - Validate host configuration before applying changes
| Name | Type | Req | Description |
|---|---|---|---|
| attributes | object | – | Host attributes to validate |
| folder | string | – | Folder path |
| host_name | string | yes | Name of the host to validate |
| operation | string | – | Operation type (create, update) |
No output schema declared.
No examples provided.
vibemk_wait_for_discovery Wait for discovery completion ~62
⏳ Wait for discovery completion - Wait until service discovery finishes on a host
| Name | Type | Req | Description |
|---|---|---|---|
| host_name | string | yes | Host name to wait for discovery completion |
| timeout | number | – | Seconds to wait before reporting the job as still running |
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.