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

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

Available components

−4 this week 86 Trust /100

Last scanned (4 hours ago)

Scores higher than 89% of PyPI servers

Category Monitoring and Observability

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 build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 21 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency96
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to daedalus/mcp-zabbix). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 220 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management70
  • Stability observed for 21 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
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.

  • 5 Nov 26 +1

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

  • 4 Nov 26 −5
    • Stability: pass → 0.67 functional
  • 1 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 31 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 29 Oct 26 +1
    • Stability: 0.97 → pass security
  • 28 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 27 Oct 26 −16
    • Malware scan: pass → unverified ▼ security
    • Stability: pass → 0.93 functional
  • 22 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
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 5 Nov 2026 · Analysed pypi/mcp-zabbix@0.1.0

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 daedalus/mcp-zabbix
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/daedalus/mcp-zabbix/.github/workflows/pypi-publish.yml@refs/tags/v0.1.0
Rekor log index 1191744297
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:9deb1233e9eef83e2b2d1b650536ebe71393fc48d09135986e93642dd0aaf6ea

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_dcheck_create ~26

Zabbix API dcheck.create method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_dcheck_delete ~26

Zabbix API dcheck.delete method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_dcheck_exists ~26

Zabbix API dcheck.exists method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_dcheck_get ~26

Zabbix API dcheck.get method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_dcheck_update ~26

Zabbix API dcheck.update method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_dhost_create ~26

Zabbix API dhost.create method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_dhost_delete ~26

Zabbix API dhost.delete method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_dhost_get ~26

Zabbix API dhost.get method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_dhost_update ~26

Zabbix API dhost.update method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_drule_create ~26

Zabbix API drule.create method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_drule_delete ~26

Zabbix API drule.delete method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_drule_exists ~26

Zabbix API drule.exists method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_drule_get ~26

Zabbix API drule.get method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_drule_update ~26

Zabbix API drule.update method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_dservice_create ~26

Zabbix API dservice.create method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_dservice_delete ~26

Zabbix API dservice.delete method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_dservice_get ~26

Zabbix API dservice.get method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_dservice_update ~26

Zabbix API dservice.update method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_event_create ~24

Zabbix API event.create method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_event_delete ~24

Zabbix API event.delete method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_event_get ~24

Zabbix API event.get method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_event_update ~24

Zabbix API event.update method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_graph_create ~24

Zabbix API graph.create method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_graph_delete ~24

Zabbix API graph.delete method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_graph_exists ~24

Zabbix API graph.exists method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_graph_get ~24

Zabbix API graph.get method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_graph_update ~24

Zabbix API graph.update method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_graphitem_create ~26

Zabbix API graphitem.create method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_graphitem_delete ~26

Zabbix API graphitem.delete method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_graphitem_get ~26

Zabbix API graphitem.get method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_graphitem_update ~26

Zabbix API graphitem.update method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_graphprototype_create ~26

Zabbix API graphprototype.create method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_graphprototype_delete ~26

Zabbix API graphprototype.delete method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_graphprototype_exists ~26

Zabbix API graphprototype.exists method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_graphprototype_get ~26

Zabbix API graphprototype.get method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_graphprototype_update ~26

Zabbix API graphprototype.update method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_hanode_create ~27

Zabbix API hanode.create method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_hanode_delete ~27

Zabbix API hanode.delete method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_hanode_exists ~27

Zabbix API hanode.exists method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_hanode_get ~27

Zabbix API hanode.get method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_hanode_update ~27

Zabbix API hanode.update method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_host_create ~24

Zabbix API host.create method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_host_delete ~24

Zabbix API host.delete method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_host_exists ~24

Zabbix API host.exists method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_host_get ~24

Zabbix API host.get method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_host_update ~24

Zabbix API host.update method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_hostgroup_create ~26

Zabbix API hostgroup.create method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_hostgroup_delete ~26

Zabbix API hostgroup.delete method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_hostgroup_exists ~26

Zabbix API hostgroup.exists method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

zabbix_hostgroup_get ~26

Zabbix API hostgroup.get method

NameTypeReqDescription
params–––

Structured output declared, but exposes no named fields.

No examples provided.

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
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 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 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 5 November 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.