Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.daedalus/mcp-zabbix

PYPI · MCP-ZABBIX · SCANNED SEP 21

MCP server for Zabbix API - exposes all Zabbix API functionality via MCP

Available components

+16 this week 79 Trust /100
Trust breakdown (7 categories)

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 hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 1 of 21 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability69
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 6626 tokens (~25/item across 263 items; 262 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 52 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "zabbix_action_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 263 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
Install

How do I install the io.github.daedalus/mcp-zabbix server?

io.github.daedalus/mcp-zabbix runs locally as a PyPI package, launched with uvx mcp-zabbix. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-zabbix

# add to Claude Code
claude mcp add daedalus-mcp-zabbix -- uvx mcp-zabbix
// .cursor/mcp.json
{
  "mcpServers": {
    "daedalus-mcp-zabbix": {
      "command": "uvx",
      "args": [
        "mcp-zabbix"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "daedalus-mcp-zabbix": {
      "command": "uvx",
      "args": [
        "mcp-zabbix"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add daedalus-mcp-zabbix -- uvx mcp-zabbix
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "daedalus-mcp-zabbix": {
      "type": "local",
      "command": [
        "uvx",
        "mcp-zabbix"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add daedalus-mcp-zabbix --command uvx --arg mcp-zabbix
# ~/.hermes/config.yaml
mcp_servers:
  daedalus-mcp-zabbix:
    command: "uvx"
    args: ["mcp-zabbix"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "daedalus-mcp-zabbix": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcp-zabbix"
      ]
    }
  }
}
# add to Vellum
assistant mcp add daedalus-mcp-zabbix -t stdio -c uvx -a mcp-zabbix
// mcp.json
{
  "mcpServers": {
    "daedalus-mcp-zabbix": {
      "command": "uvx",
      "args": [
        "mcp-zabbix"
      ]
    }
  }
}
Changelog

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.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −3
    • Stability: pass → 0.83 functional
  • 17 Sept 26 +1
    • Stability: 0.97 → pass security
  • 15 Sept 26 +16
    • Malware scan: unverified → pass security
  • 14 Sept 26 −15
    • Malware scan: pass → unverified security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 −3
    • Stability: pass → 0.80 functional
Diagnostics

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 21 Sept 2026 · Analysed pypi/mcp-zabbix@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 21 packages
Packages resolved 21
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 262 exposed · ~6,614 tokens

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 →

Tool Tokens
zabbix_sla_delete_schedule ~27

Zabbix API sla.delete_schedule method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_sla_exists ~25

Zabbix API sla.exists method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_sla_get ~25

Zabbix API sla.get method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_sla_get_schedule ~27

Zabbix API sla.get_schedule method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_sla_get_sla ~29

Zabbix API sla.get_sla method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_sla_update ~25

Zabbix API sla.update method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_sla_update_schedule ~27

Zabbix API sla.update_schedule method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_template_create ~24

Zabbix API template.create method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_template_delete ~24

Zabbix API template.delete method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_template_exists ~24

Zabbix API template.exists method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_template_get ~24

Zabbix API template.get method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_template_update ~24

Zabbix API template.update method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_templategroup_create ~29

Zabbix API templategroup.create method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_templategroup_delete ~29

Zabbix API templategroup.delete method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_templategroup_exists ~29

Zabbix API templategroup.exists method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_templategroup_get ~29

Zabbix API templategroup.get method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_templategroup_update ~29

Zabbix API templategroup.update method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_trend_create ~25

Zabbix API trend.create method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_trend_delete ~25

Zabbix API trend.delete method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_trend_get ~25

Zabbix API trend.get method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_trend_update ~25

Zabbix API trend.update method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_trigger_create ~24

Zabbix API trigger.create method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_trigger_delete ~24

Zabbix API trigger.delete method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_trigger_exists ~24

Zabbix API trigger.exists method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_trigger_get ~24

Zabbix API trigger.get method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_trigger_update ~24

Zabbix API trigger.update method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_triggerprototype_create ~26

Zabbix API triggerprototype.create method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_triggerprototype_delete ~26

Zabbix API triggerprototype.delete method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_triggerprototype_exists ~26

Zabbix API triggerprototype.exists method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_triggerprototype_get ~26

Zabbix API triggerprototype.get method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_triggerprototype_update ~26

Zabbix API triggerprototype.update method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_user_changepassword ~28

Zabbix API user.changepassword method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_user_checkAuthentication ~26

Zabbix API user.checkAuthentication method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_user_create ~24

Zabbix API user.create method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_user_delete ~24

Zabbix API user.delete method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_user_exists ~24

Zabbix API user.exists method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_user_get ~24

Zabbix API user.get method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_user_login ~24

Zabbix API user.login method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_user_logout ~24

Zabbix API user.logout method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_user_resetpassword ~26

Zabbix API user.resetpassword method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_user_update ~24

Zabbix API user.update method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_user_updateprofile ~26

Zabbix API user.updateprofile method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_usergroup_create ~26

Zabbix API usergroup.create method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_usergroup_delete ~26

Zabbix API usergroup.delete method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_usergroup_exists ~26

Zabbix API usergroup.exists method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_usergroup_get ~26

Zabbix API usergroup.get method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_usergroup_update ~26

Zabbix API usergroup.update method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_valuemap_create ~27

Zabbix API valuemap.create method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_valuemap_delete ~27

Zabbix API valuemap.delete method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_valuemap_exists ~27

Zabbix API valuemap.exists method

NameTypeReqDescription
params

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the io.github.daedalus/mcp-zabbix server?

io.github.daedalus/mcp-zabbix is listed in the public MCP registry as io.github.daedalus/mcp-zabbix. MCP server for Zabbix API - exposes all Zabbix API functionality via MCP. This page covers its PyPI package (mcp-zabbix).

Is the io.github.daedalus/mcp-zabbix server safe to use?

io.github.daedalus/mcp-zabbix scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. 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 io.github.daedalus/mcp-zabbix server expose?

io.github.daedalus/mcp-zabbix exposes 262 tools: zabbix_action_create, zabbix_action_get, zabbix_action_update, zabbix_action_delete, zabbix_action_exists, and 257 more. Their descriptions and schemas cost roughly 6,614 tokens of context every time the server is loaded.

Is the io.github.daedalus/mcp-zabbix server still maintained?

io.github.daedalus/mcp-zabbix is still listed as active in the MCP registry. We last reached this channel on 21 September 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 io.github.daedalus/mcp-zabbix server under?

io.github.daedalus/mcp-zabbix declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.