McpStamp Zip Archives
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS
Create zip archives, list their contents with safety flags, and extract without unsafe entries.
Available components
Last scanned (2 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
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. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2018 tokens (~155/item across 13 items; 12 tools + 1 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 2 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “zip_delete_upload” is now declared destructive security
- Tool “zip_upload” is now declared destructive security
- Destructive annotations: All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- 16 Oct 26 0
- Server version: 0.22.0 → 0.22.6 functional
- 15 Oct 26 +68
- Transport: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 14 Oct 26 −68
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.97 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 8 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 87 to 97. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 5 Nov 2026 · Probed https://mcp.zovo.one/mcp/zip
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 39e1adfa4eb6500e0e3d48868766e3e9 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/zip"
Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/zip"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Document | https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/zip |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.zovo.one/mcp/zip |
| Authorisation server | https://mcp.zovo.one |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/zip | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/zip | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/zip |
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 →
license_activate Activate license ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zip_add Add files to a zip ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Path to the existing .zip file |
| paths | array | yes | 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 |
No output schema declared.
No examples provided.
zip_bundle_month Bundle a month of documents ~199
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
zip_create Create a zip archive ~286
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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) |
No output schema declared.
No examples provided.
zip_delete_upload Delete an uploaded file ~34
Delete one uploaded file stored for your token. The register rows zip_history lists are kept.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
zip_extract Extract a zip archive ~269
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
No output schema declared.
No examples provided.
zip_extract_text Read one entry as text ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entry | string | yes | 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 | yes | Path to the .zip file |
No output schema declared.
No examples provided.
zip_files List uploaded files ~34
List the files stored for your token on this endpoint, with their sizes. These are the names every path argument here resolves against.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zip_history Archives created ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many rows to show, newest first (default 20) |
No output schema declared.
No examples provided.
zip_list List a zip archive ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
No output schema declared.
No examples provided.
zip_upload Upload a file or an archive ~390
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
No output schema declared.
No examples provided.
How do I install the McpStamp Zip Archives MCP server?
McpStamp Zip Archives 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.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-zip-archive-create-extract-bomb-g 'https://mcp.zovo.one/mcp/zip'
What is the McpStamp Zip Archives MCP server?
McpStamp Zip Archives is an MCP server listed in the public MCP registry as io.github.theluckystrike/zip-archive-create-extract-bomb-gu…. Create zip archives, list their contents with safety flags, and extract without unsafe entries. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/zip).
Is the McpStamp Zip Archives MCP server safe to use?
McpStamp Zip Archives scores 94 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 McpStamp Zip Archives MCP server expose?
McpStamp Zip Archives 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 McpStamp Zip Archives MCP server require authentication?
Yes. McpStamp Zip Archives 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 McpStamp Zip Archives MCP server still maintained?
McpStamp Zip Archives 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.