zapi-mcpSAFE
MCP server for the Zabbix API — daily brief, problems, hosts, items
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
English | 日本語
MCP (Model Context Protocol) server for the Zabbix API.
Built for network operations: a single daily_brief call summarizes active problems plus site-specific categories (DHCP pool usage, SNAT session usage, core-network problems, ...), and individual tools query problems, hosts, and item values. Organization-specific tags live in a config file, not the code, so the server stays generic.
Version-adaptive auth: works against Zabbix 6.0 LTS (user + auth field) and forward-compatible with 6.4 / 7.0 (username + Authorization: Bearer).
Documentation:
Features
Setup
# uv uv pip install zapi-mcp # pip pip install zapi-mcp
Or from source:
git clone https://github.com/shigechika/zapi-mcp.git cd zapi-mcp # uv uv sync # pip p
345a9ae2f20eOBSERVED · 2026-10-12Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add zapi-mcp -- None zapi-mcp==0.12.0
Exposed tools (8)
6 read · 2 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
acknowledge_problem | write | Acknowledge Zabbix problems and add a message (does not close them). |
daily_brief | read | Morning patrol summary. |
get_host_items | read | Get current item values for a host. |
get_hosts | read | List Zabbix hosts filtered by tag or group. |
get_maintenance_windows | read | List Zabbix maintenance windows -- the read counterpart to set_maintenance. |
get_problems | read | Get active Zabbix problems, newest first. |
health_check | read | Report server version, Zabbix connectivity, and configured categories. |
set_maintenance | write | Create a Zabbix maintenance window, selecting hosts by location tag OR |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (2)
.release-please-manifest.json
probes_module = importlib.import_module(args.probes)
Gates applied: no_behavioural_pass.
345a9ae2f20efull audit observations/trust-audit/mcp-server/shigechika__zapi-mcp.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-12 | 345a9ae2f20e | SAFE | B | 89 | first audit |
Questions
What is the zapi-mcp MCP server?
MCP server for the Zabbix API — daily brief, problems, hosts, items
What tools does zapi-mcp expose?
8 in total: 6 read-only, 2 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is zapi-mcp safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does zapi-mcp need?
It reads ZABBIX_PASSWORD from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does zapi-mcp run?
It speaks stdio, so it runs as a local process your client starts. It is published on PyPI as zapi-mcp.
How current is this page?
The grade is for one exact copy of the source (345a9ae2f20e), read on 2026-10-12. The repository is watched and re-audited when it changes.