# zanadir (oci · docker.io/mustachecase/zanadir)

Find what a repository's CI is missing, and which security checks cannot fail the build.

- Trust score: 42/100 (low)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- oci · `docker.io/mustachecase/zanadir`: 42/100 (this document), [markdown](https://verifymcp.io/servers/mustachecase-zanadir/docker-io-mustachecase-zanadir.md), [page](https://verifymcp.io/servers/mustachecase-zanadir/docker-io-mustachecase-zanadir)

## Channel facts

- Registry: `oci`
- Package: `docker.io/mustachecase/zanadir`
- Version: `0.29.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 35/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 554 tokens (~184/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the zanadir MCP server?

zanadir runs locally as a container image, launched with docker run --rm -i -e GITHUB_TOKEN docker.io/mustachecase/zanadir:0.29.0 mcp, plus the required --mount, which you supply. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add mustachecase-zanadir -- docker run --rm -i -e GITHUB_TOKEN docker.io/mustachecase/zanadir:0.29.0 mcp
```

This image reads GITHUB_TOKEN. Set it in your client's env block for this server; docker run -e passes it through to the container. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --mount as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Cursor

```json
{
  "mcpServers": {
    "mustachecase-zanadir": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "GITHUB_TOKEN",
        "docker.io/mustachecase/zanadir:0.29.0",
        "mcp"
      ]
    }
  }
}
```

This image reads GITHUB_TOKEN. Set it in your client's env block for this server; docker run -e passes it through to the container. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --mount as required and gives no value we can show, so it is not in this command. Add it before you run it.

### VS Code

```json
{
  "servers": {
    "mustachecase-zanadir": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "GITHUB_TOKEN",
        "docker.io/mustachecase/zanadir:0.29.0",
        "mcp"
      ]
    }
  }
}
```

This image reads GITHUB_TOKEN. Set it in your client's env block for this server; docker run -e passes it through to the container. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --mount as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Codex

```bash
codex mcp add mustachecase-zanadir -- docker run --rm -i -e GITHUB_TOKEN docker.io/mustachecase/zanadir:0.29.0 mcp
```

This image reads GITHUB_TOKEN. Set it in your client's env block for this server; docker run -e passes it through to the container. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --mount as required and gives no value we can show, so it is not in this command. Add it before you run it.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mustachecase-zanadir": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "GITHUB_TOKEN",
        "docker.io/mustachecase/zanadir:0.29.0",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

This image reads GITHUB_TOKEN. Set it in your client's env block for this server; docker run -e passes it through to the container. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --mount as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Hermes

```yaml
mcp_servers:
  mustachecase-zanadir:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "GITHUB_TOKEN", "docker.io/mustachecase/zanadir:0.29.0", "mcp"]
```

This image reads GITHUB_TOKEN. Set it in your client's env block for this server; docker run -e passes it through to the container. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --mount as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Netclaw

```json
{
  "McpServers": {
    "mustachecase-zanadir": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "GITHUB_TOKEN",
        "docker.io/mustachecase/zanadir:0.29.0",
        "mcp"
      ]
    }
  }
}
```

This image reads GITHUB_TOKEN. Set it in your client's env block for this server; docker run -e passes it through to the container. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --mount as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Other

```json
{
  "mcpServers": {
    "mustachecase-zanadir": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "GITHUB_TOKEN",
        "docker.io/mustachecase/zanadir:0.29.0",
        "mcp"
      ]
    }
  }
}
```

This image reads GITHUB_TOKEN. Set it in your client's env block for this server; docker run -e passes it through to the container. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --mount as required and gives no value we can show, so it is not in this command. Add it before you run it.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 42, −1)

- [security regression] Provenance: pass → unverified
- [functional regression] Schema quality: 360 → 554
- [functional] Package version: 0.28.0 → 0.29.0

### 2026-11-04 (score 43, +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.

### 2026-11-02 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 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.

### 2026-11-01 (score 41, 0)

- [security regression] Stability: 0.27 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.26.1 → 0.28.0
- [functional] Package version: 0.26.1 → 0.27.0

### 2026-10-31 (score 41, +1)

- [functional] Package version: 0.24.2 → 0.26.1
- [functional] Package version: 0.24.2 → 0.26.0
- [functional] Package version: 0.24.2 → 0.25.0

### 2026-10-29 (score 40, +1)

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

### 2026-10-28 (score 39, 0)

- [security regression] Stability: 0.13 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.23.0 → 0.24.2
- [functional] Package version: 0.23.0 → 0.24.1
- [functional] Package version: 0.23.0 → 0.24.0

### 2026-10-27 (score 39, +1)

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

## MCP tools (3)

### `scan` (~247 tokens)

Grade the CI

Reads the repository's CI configuration (GitHub Actions, GitLab CI, CircleCI, Bitbucket Pipelines, Azure Pipelines, Jenkins) and reports, as JSON:
\- score: categories covered out of those that apply;
\- uncovered: categories with no tool at all (SCA, secrets detection, SAST, linting, tests, coverage, licences, end-of-life, IaC, supply chain, workflow security, performance testing), each with tools that fit the repository's languages;
\- weakened: controls that are present but cannot fail a build, graded partial (not on every change), advisory (continue-on-error, || true, --exit-code 0, schedule-only) or unknown (behind a condition);
\- notApplicable and platforms.
Run it before changing CI, and again after, to confirm the change.

Input parameters:

- `dir` (string): path to a local checkout; defaults to the current directory
- `excludedCategories` (array): categories that do not apply to this repository, such as Performance Testing
- `repo` (string): a GitHub repository to read without cloning, as github.com/owner/name or github.com/owner/name@ref; instead of dir

### `fix` (~113 tokens)

CI configuration for the gaps

Prints ready-to-paste CI configuration for each uncovered category, for the CI platform the repository uses. It changes no files: adapt the snippets into the existing workflows.

Input parameters:

- `dir` (string): path to a local checkout; defaults to the current directory
- `excludedCategories` (array): categories that do not apply to this repository, such as Performance Testing
- `repo` (string): a GitHub repository to read without cloning, as github.com/owner/name or github.com/owner/name@ref; instead of dir

### `skills` (~194 tokens)

Check the agent skills

Finds every agent skill (SKILL.md) in the repository and reports, as JSON, the skills found and their problems, each with a rule, file and line:
\- errors: frontmatter that is not valid YAML, links to files that do not exist, characters that hide text from a reviewer;
\- warnings: a missing name or description, a description that never says when to use the skill (it will rarely trigger) or overlaps another skill's, a body too long to load every time, unrestricted Bash, and curl piped into a shell or approvals skipped in what the agent runs.
Run it after writing or changing a skill, and again after fixing it.

Input parameters:

- `dir` (string): path to a local checkout; defaults to the current directory
- `repo` (string): a GitHub repository to read without cloning, as github.com/owner/name or github.com/owner/name@ref; instead of dir

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/mustachecase-zanadir/docker-io-mustachecase-zanadir#diagnostics

## Score history

- 2026-11-05: 42
- 2026-11-04: 43
- 2026-11-03: 42
- 2026-11-02: 42
- 2026-11-01: 41
- 2026-10-31: 41
- 2026-10-30: 40
- 2026-10-29: 40
- 2026-10-28: 39
- 2026-10-27: 39
- 2026-10-26: 38
- 2026-10-25: 38
- 2026-10-24: 37
- 2026-10-23: 37

## Common questions

### What is the zanadir MCP server?

zanadir is an MCP server listed in the public MCP registry as io.github.MustacheCase/zanadir. Find what a repository's CI is missing, and which security checks cannot fail the build. This page covers its container image (docker.io/mustachecase/zanadir).

### Is the zanadir MCP server safe to use?

zanadir scores 42 out of 100 on VerifyMCP. 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 zanadir MCP server expose?

zanadir exposes 3 tools: scan, fix, skills. Their descriptions and schemas cost roughly 554 tokens of context every time the server is loaded.

### Is the zanadir MCP server still maintained?

zanadir 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 did VerifyMCP test on the zanadir MCP server?

VerifyMCP ran 12 checks on zanadir, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about zanadir: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Docker Hub: https://hub.docker.com/r/mustachecase/zanadir
- Repository: https://github.com/MustacheCase/zanadir
- Website: https://mustachecase.github.io/
- Changelog RSS feed: https://verifymcp.io/servers/mustachecase-zanadir/docker-io-mustachecase-zanadir.xml
- Changelog JSON feed: https://verifymcp.io/servers/mustachecase-zanadir/docker-io-mustachecase-zanadir/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mustachecase-zanadir/docker-io-mustachecase-zanadir.json
- HTML version of this page: https://verifymcp.io/servers/mustachecase-zanadir/docker-io-mustachecase-zanadir