SnapDoczilla
PYPI · SNAPDOCZILLA-MCP
Offline docs-as-code for any backend and frontend: a MkDocs site in your repo, by your AI agent.
Available components
Last scanned (3 hours ago)
Scores higher than 64% of PyPI servers
Category Developer Tools
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 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability47
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
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.
- 14 Oct 26 +26
- 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). security
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 0 ▲ functional
- 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 functional
- 12 Oct 26 39
First indexed and scored.
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 17 Oct 2026 · Analysed pypi/snapdoczilla-mcp@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
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 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
snapdoczilla_build_html ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | Absolute path of the git repository (any folder inside it works). |
Structured output declared, but exposes no named fields.
No examples provided.
snapdoczilla_changes_since_sync ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | yes | Area name from documentation/areas.conf, e.g. 'back' or 'front'. |
| repo | string | yes | Absolute path of the git repository (any folder inside it works). |
Structured output declared, but exposes no named fields.
No examples provided.
snapdoczilla_get_rules ~70
Return the rules the documentation must follow (language, tone, page layout, no invention).
| Name | Type | Req | Description |
|---|---|---|---|
| area | – | – | Also return this area's AGENT-RULES-<area>.md when it exists. |
| repo | string | yes | Absolute path of the git repository (any folder inside it works). |
Structured output declared, but exposes no named fields.
No examples provided.
snapdoczilla_install ~163
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Human name shown as the site title. |
| repo | string | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
snapdoczilla_mark_synced ~77
Record the current HEAD as the last documented commit of an area. Call it after the area's pages are updated.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | yes | Area name from documentation/areas.conf, e.g. 'back' or 'front'. |
| repo | string | yes | Absolute path of the git repository (any folder inside it works). |
Structured output declared, but exposes no named fields.
No examples provided.
snapdoczilla_status ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | Absolute path of the git repository (any folder inside it works). |
Structured output declared, but exposes no named fields.
No examples provided.
snapdoczilla_write_page ~127
Create or overwrite one Markdown page. Writes are confined to documentation/source/.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | 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 | yes | Path inside documentation/source/, e.g. 'architecture.md' or 'adr/0002-use-queue.md'. |
| repo | string | yes | Absolute path of the git repository (any folder inside it works). |
Structured output declared, but exposes no named fields.
No examples provided.
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.
pypi · snapdoczilla-mcp
claude mcp add julvc-snapdoczilla -- uvx snapdoczilla-mcp
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.