# SnapDoczilla (pypi · snapdoczilla-mcp)

Offline docs-as-code for any backend and frontend: a MkDocs site in your repo, by your AI agent.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- pypi · `snapdoczilla-mcp`: 65/100 (this document), [markdown](https://verifymcp.io/servers/julvc-snapdoczilla/snapdoczilla-mcp.md), [page](https://verifymcp.io/servers/julvc-snapdoczilla/snapdoczilla-mcp)

## Channel facts

- Registry: `pypi`
- Package: `snapdoczilla-mcp`
- Version: `1.0.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-10-17.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 28 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 47/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 906 tokens (~129/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (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 SnapDoczilla MCP server?

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

### Claude

```bash
claude mcp add julvc-snapdoczilla -- uvx snapdoczilla-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "julvc-snapdoczilla": {
      "command": "uvx",
      "args": [
        "snapdoczilla-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "julvc-snapdoczilla": {
      "command": "uvx",
      "args": [
        "snapdoczilla-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add julvc-snapdoczilla -- uvx snapdoczilla-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "julvc-snapdoczilla": {
      "type": "local",
      "command": [
        "uvx",
        "snapdoczilla-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add julvc-snapdoczilla --command uvx --arg snapdoczilla-mcp
```

### Hermes

```yaml
mcp_servers:
  julvc-snapdoczilla:
    command: "uvx"
    args: ["snapdoczilla-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "julvc-snapdoczilla": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "snapdoczilla-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add julvc-snapdoczilla -t stdio -c uvx -a snapdoczilla-mcp
```

### Other

```json
{
  "mcpServers": {
    "julvc-snapdoczilla": {
      "command": "uvx",
      "args": [
        "snapdoczilla-mcp"
      ]
    }
  }
}
```

## 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-10-14 (score 65, +26)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 0
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100
- [functional] First check of Tool coverage: 100

### 2026-10-12 (score 39)

First indexed and scored.

## MCP tools (7)

### `snapdoczilla_status` (~72 tokens)

Report whether SnapDoczilla is installed in the repo, its areas, how many commits each area is
behind its docs, the existing pages, the next ADR number and the suggested next step. Call this first.

Input parameters:

- `repo` (string, required): Absolute path of the git repository (any folder inside it works).

### `snapdoczilla_install` (~163 tokens)

Install the documentation scaffold into documentation/ (templates, update script, pre-push reminder)
and download Mermaid once (needs internet). Refuses to touch an existing documentation/ folder.

Input parameters:

- `areas`: Code areas as {name: path relative to the repo root}, e.g. {'back': 'backend/', 'front': 'frontend/'}. Omit for a single area covering the whole repo.
- `language` (string): Docs language code: 'en', 'es', ...
- `project_name` (string, required): Human name shown as the site title.
- `repo` (string, required): Absolute path of the git repository (any folder inside it works).
- `ui_areas`: Names from `areas` that contain UI components; they get component-page rules.

### `snapdoczilla_get_rules` (~70 tokens)

Return the rules the documentation must follow (language, tone, page layout, no invention).

Input parameters:

- `area`: Also return this area's AGENT-RULES-<area>.md when it exists.
- `repo` (string, required): Absolute path of the git repository (any folder inside it works).

### `snapdoczilla_changes_since_sync` (~93 tokens)

List the files, commits and diffstat of an area since its last documented commit, so only the
affected pages are updated. With no previous sync it says to analyze the whole area.

Input parameters:

- `area` (string, required): Area name from documentation/areas.conf, e.g. 'back' or 'front'.
- `repo` (string, required): Absolute path of the git repository (any folder inside it works).

### `snapdoczilla_write_page` (~127 tokens)

Create or overwrite one Markdown page. Writes are confined to documentation/source/.

Input parameters:

- `content` (string, required): Full Markdown of the page. Embed real code with --8<-- "path/from/repo/root".
- `nav_title`: Menu title. Pass it when creating a page so it is added to nav (the strict build needs that).
- `page` (string, required): Path inside documentation/source/, e.g. 'architecture.md' or 'adr/0002-use-queue.md'.
- `repo` (string, required): Absolute path of the git repository (any folder inside it works).

### `snapdoczilla_build_html` (~79 tokens)

Rebuild documentation/html with a strict MkDocs build (no AI agent is invoked). The first run creates a
local venv and installs MkDocs, which takes a minute or two and needs internet. A failed build keeps the old html.

Input parameters:

- `repo` (string, required): Absolute path of the git repository (any folder inside it works).

### `snapdoczilla_mark_synced` (~77 tokens)

Record the current HEAD as the last documented commit of an area. Call it after the area's pages are updated.

Input parameters:

- `area` (string, required): Area name from documentation/areas.conf, e.g. 'back' or 'front'.
- `repo` (string, required): Absolute path of the git repository (any folder inside it works).

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/julvc-snapdoczilla/snapdoczilla-mcp#diagnostics

## Score history

- 2026-10-17: 65
- 2026-10-16: 65
- 2026-10-15: 65
- 2026-10-14: 65
- 2026-10-13: 39
- 2026-10-12: 39

## Common questions

### What is the SnapDoczilla MCP server?

SnapDoczilla is an MCP server listed in the public MCP registry as io.github.julvc/snapdoczilla. Offline docs-as-code for any backend and frontend: a MkDocs site in your repo, by your AI agent. This page covers its PyPI package (snapdoczilla-mcp).

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

SnapDoczilla scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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 SnapDoczilla MCP server expose?

SnapDoczilla exposes 7 tools: snapdoczilla_status, snapdoczilla_install, snapdoczilla_get_rules, snapdoczilla_changes_since_sync, snapdoczilla_write_page, and 2 more. Their descriptions and schemas cost roughly 681 tokens of context every time the server is loaded.

### Is the SnapDoczilla MCP server still maintained?

SnapDoczilla 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 SnapDoczilla MCP server under?

SnapDoczilla declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/snapdoczilla-mcp/
- Socket report: https://socket.dev/pypi/package/snapdoczilla-mcp
- Repository: https://github.com/julvc/skills
- Changelog RSS feed: https://verifymcp.io/servers/julvc-snapdoczilla/snapdoczilla-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/julvc-snapdoczilla/snapdoczilla-mcp.json
- HTML version of this page: https://verifymcp.io/servers/julvc-snapdoczilla/snapdoczilla-mcp