# io.github.theluckystrike/zip-archive-create-extract-bomb-guard (remote · mcp.zovo.one)

Create, inspect and extract zip archives offline, with traversal, symlink and zip-bomb guards.

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcp.zovo.one`: 83/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-zip-archive-create-extract-bomb-guard/mcp-zip.md), [page](https://verifymcp.io/servers/theluckystrike-zip-archive-create-extract-bomb-guard/mcp-zip)
- mcpb · `zip.mcpb`: 47/100, [markdown](https://verifymcp.io/servers/theluckystrike-zip-archive-create-extract-bomb-guard/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-zip-mcpb.md), [page](https://verifymcp.io/servers/theluckystrike-zip-archive-create-extract-bomb-guard/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-zip-mcpb)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/zip`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-09-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1906 tokens (~146/item across 13 items; 12 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 98% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "zip_upload" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.theluckystrike/zip-archive-create-extract-bomb-gu… MCP server?

io.github.theluckystrike/zip-archive-create-extract-bomb-gu… is a hosted endpoint at https://mcp.zovo.one/mcp/zip, so there is nothing to install locally. 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 --transport http theluckystrike-zip-archive-create-extract-bomb-g 'https://mcp.zovo.one/mcp/zip'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-zip-archive-create-extract-bomb-g": {
      "url": "https://mcp.zovo.one/mcp/zip"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-zip-archive-create-extract-bomb-g": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/zip"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-zip-archive-create-extract-bomb-g]
url = "https://mcp.zovo.one/mcp/zip"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-zip-archive-create-extract-bomb-g": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/zip",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-zip-archive-create-extract-bomb-g --url 'https://mcp.zovo.one/mcp/zip' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-zip-archive-create-extract-bomb-g:
    url: "https://mcp.zovo.one/mcp/zip"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-zip-archive-create-extract-bomb-g": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/zip"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-zip-archive-create-extract-bomb-g -t streamable-http -u 'https://mcp.zovo.one/mcp/zip'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-zip-archive-create-extract-bomb-g": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/zip"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-21 (score 83, +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-09-19 (score 82, +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-09-18 (score 81, +56)

- [security regression] Authorization: unverified → fail
- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [functional improvement] Endpoint reachability: behind authorisation → reachable
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.30
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Tool coverage: unverified → 100
- [functional] Server version: 0.21.0 → 0.22.0

### 2026-09-17 (score 25, −55)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Authorization: fail → unverified
- [security regression] Transport: pass → unverified
- [security regression] Stability: 0.23 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified

### 2026-09-15 (score 80, +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-09-13 (score 79, +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.

### 2026-09-11 (score 78, +2)

- [functional improvement] Schema quality: unverified → 100
- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-10 (score 76, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

## MCP tools (12)

### `license_status` (~55 tokens)

License status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

### `license_activate` (~76 tokens)

Activate license

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

### `zip_upload` (~390 tokens)

Upload a file or an archive

Send a file to this hosted endpoint. There is no filesystem here, so instead of a path you upload the file once with zip_upload and then pass its name wherever a path is asked for: an archive to zip_list, zip_extract, zip_extract_text or zip_add, a plain file to zip_create. Give exactly one of content_base64 (the file's bytes, the only paste form an archive can take), content (text, for a text file to pack) or url. url: fetch a public file instead of pasting base64 (recommended above about 10 KB): the url is fetched here with a 10 second timeout, at most 3 redirects, public http(s) hosts only, and a 1 MB cap, and a name ending .zip is checked for the PK magic before anything is stored. Uploads are kept for your token between calls; zip_files lists them and zip_delete_upload removes one. The request body cap is 256 KB, so the practical ceiling on a paste is about 190 KB of file once it is base64 inside a JSON-RPC envelope.

Input parameters:

- `content` (string): The file as text (a .txt, .csv, .md or source file to pack). Not accepted for a .zip
- `content_base64` (string): The file's bytes, base64-encoded. This is the only paste form an archive can be uploaded in
- `name` (string, required): Name to refer to this file by: 1-64 characters of letters, digits, underscore or dash, with an optional extension. No extension means .zip, e.g. "reports" or "notes.txt"
- `url` (string): url: fetch a public file instead of pasting base64 (recommended above about 10 KB). Public http(s) only; private, link-local and this endpoint's own zone are refused

### `zip_files` (~34 tokens)

List uploaded files

List the files stored for your token on this endpoint, with their sizes. These are the names every path argument here resolves against.

### `zip_delete_upload` (~34 tokens)

Delete an uploaded file

Delete one uploaded file stored for your token. The register rows zip_history lists are kept.

Input parameters:

- `name` (string, required)

### `zip_create` (~286 tokens)

Create a zip archive

Call this tool to pack files uploaded with zip_upload into a new .zip and get a download link valid for one hour. Entry names are always relative, so the archive cannot write outside where it is unpacked.

Input parameters:

- `dir` (string): Not available on this hosted endpoint: there are no directories. Passing it is refused rather than ignored, so nobody believes a tree was packed
- `exclude` (array): Drop entries matching one of these globs, applied after patterns
- `level` (integer): Deflate level 0 to 9, default 6. 0 stores without compressing
- `out_path` (string, required): Name for the archive, e.g. reports. It comes back as a download link valid for one hour; a name already produced in this request is refused without overwrite
- `overwrite` (boolean): Replace out_path if a file is already there. Default false: an existing file is never overwritten
- `password` (string): Not supported. Passing it is refused rather than ignored, so no one believes an archive is encrypted when it is not
- `paths` (array): Names of files uploaded with zip_upload, each packed under that name
- `patterns` (array): Only entries matching one of these globs (* and ? inside a segment, ** across segments; a pattern with no slash also matches the file name at any depth)

### `zip_list` (~144 tokens)

List a zip archive

Call this tool to list an archive's entries with sizes and ratios and flag what is dangerous: absolute paths, .., symlinks, encrypted entries, duplicate names and bombs. Read-only. Run it before zip_extract.

Input parameters:

- `limit` (integer): How many entries to print, largest first (default 50). The totals always cover every entry
- `max_ratio` (number): Flag an entry whose uncompressed/compressed ratio is above this. Default 100
- `path` (string, required): Path to the .zip file. Read-only: the archive is never modified and nothing is extracted
- `patterns` (array): Only entries matching one of these globs

### `zip_extract` (~269 tokens)

Extract a zip archive

Call this tool to unpack an archive; every entry comes back as its own download link valid for one hour. Traversal, absolute-path and symlink entries are refused, a size and ratio cap stops a zip bomb, and dry_run reports exactly what would be written.

Input parameters:

- `dry_run` (boolean): Report what would be written, byte counts included, and write nothing
- `max_ratio` (number): Refuse an entry whose uncompressed/compressed ratio is above this. Default 100
- `max_total_mb` (number): Refuse if the selected entries declare more than this uncompressed. Default 1024
- `out_dir` (string): Ignored on this hosted endpoint: there are no directories, and every extracted entry comes back as its own download link valid for one hour
- `overwrite` (boolean): Replace files that already exist in out_dir. Default false: the whole extraction is refused if any would be replaced
- `path` (string, required): Path to the .zip file
- `patterns` (array): Only entries matching one of these globs (* and ? inside a segment, ** across segments)
- `skip_unsafe` (boolean): Skip the dangerous entries and extract the rest, naming what was skipped. Default false: one bad entry refuses the whole archive

### `zip_add` (~181 tokens)

Add files to a zip

Call this tool to add files to an existing archive under their own names, or under prefix. A name clash is refused unless replace. An archive holding unsafe entries is refused rather than rewritten.

Input parameters:

- `level` (integer): Deflate level 0 to 9 for the new entries, default 6
- `password` (string): Not supported. Passing it is refused rather than ignored
- `path` (string, required): Path to the existing .zip file
- `paths` (array, required): Files to add, each stored under its own file name. A directory contributes its tree under its own name
- `prefix` (string): Put the new entries under this folder inside the archive, for example "invoices"
- `replace` (boolean): Replace an entry whose name is already in the archive. Default false: a name clash is refused and nothing is changed

### `zip_extract_text` (~115 tokens)

Read one entry as text

Call this tool to read one text entry out of an archive without unpacking anything: give the entry name and the text comes back inline. Binary entries are refused by name rather than printed as noise.

Input parameters:

- `entry` (string, required): Exact entry name, as zip_list prints it. A glob is accepted when it matches exactly one entry
- `max_chars` (integer): Stop after this many characters (default 200000). The answer says when it was cut
- `path` (string, required): Path to the .zip file

### `zip_bundle_month` (~199 tokens)

Bundle a month of documents

Local (stdio) install only. On this hosted endpoint /mcp/invoice, /mcp/quotes, /mcp/expense-tracker, /mcp/docx and /mcp/resume return their documents as one-hour download links and keep no output folder to read, so there is nothing for this tool to bundle. Pack the files with zip_upload plus zip_create instead.

Input parameters:

- `dry_run` (boolean): Report what would go in and write nothing
- `month` (string): Month as YYYY-MM. Default: this month. Files are chosen by their modification date
- `out_path` (string): Name for the bundle. Default: the month, e.g. 2026-09
- `overwrite` (boolean): Replace out_path if it exists. Default false
- `servers` (array): Only these sibling servers: invoice, quotes, expense-tracker, docx, resume. Default: all five

### `zip_history` (~73 tokens)

Archives created

List the archives created for your token, newest first, with entry counts, sizes and names, plus how much of the free 20 a month is used. Each download link expires after an hour; the row keeps the name.

Input parameters:

- `limit` (integer): How many rows to show, newest first (default 20)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-zip-archive-create-extract-bomb-guard/mcp-zip#diagnostics

## Score history

- 2026-09-21: 83
- 2026-09-20: 82
- 2026-09-19: 82
- 2026-09-18: 81
- 2026-09-17: 25
- 2026-09-16: 80
- 2026-09-15: 80
- 2026-09-14: 79
- 2026-09-13: 79
- 2026-09-12: 78
- 2026-09-11: 78
- 2026-09-10: 76
- 2026-09-09: 75
- 2026-09-08: 36
- 2026-09-07: 36
- 2026-09-06: 36
- 2026-09-05: 36
- 2026-09-04: 36

## Common questions

### What is the io.github.theluckystrike/zip-archive-create-extract-bomb-gu… MCP server?

io.github.theluckystrike/zip-archive-create-extract-bomb-gu… is an MCP server listed in the public MCP registry as io.github.theluckystrike/zip-archive-create-extract-bomb-gu…. Create, inspect and extract zip archives offline, with traversal, symlink and zip-bomb guards. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/zip).

### Is the io.github.theluckystrike/zip-archive-create-extract-bomb-gu… MCP server safe to use?

io.github.theluckystrike/zip-archive-create-extract-bomb-gu… scores 83 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 io.github.theluckystrike/zip-archive-create-extract-bomb-gu… MCP server expose?

io.github.theluckystrike/zip-archive-create-extract-bomb-gu… exposes 12 tools: license_status, license_activate, zip_upload, zip_files, zip_delete_upload, and 7 more. Their descriptions and schemas cost roughly 1,856 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/zip-archive-create-extract-bomb-gu… MCP server require authentication?

Yes. io.github.theluckystrike/zip-archive-create-extract-bomb-gu… asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.github.theluckystrike/zip-archive-create-extract-bomb-gu… MCP server still maintained?

io.github.theluckystrike/zip-archive-create-extract-bomb-gu… is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/zip
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/zip
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/zip
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-zip-archive-create-extract-bomb-guard/mcp-zip.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-zip-archive-create-extract-bomb-guard/mcp-zip.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-zip-archive-create-extract-bomb-guard/mcp-zip