原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

McpStamp Zip Archives

作者:theluckystrike版本 0.23.0i★ 2 (整个仓库的星标)i电脑或云端官方网站 ↗
注册名称io.github.theluckystrike/zip-archive-create-extract-bomb-guard

安装方法

What it does

Create zip archives, list their contents with safety flags, and extract without unsafe entries.

  • Connects 电脑或云端
  • Account or key No key needed
  • Category 其他

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应8/8上次检查时云端端点有响应
使用分20/100

质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

用一句话让 AI 帮你安装

请帮我安装 McpStamp Zip Archives。按照 https://mcp.popnx.com/i/theluckystrike-zip-archive-create-extract-bomb-guard.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp.zovo.one) · ✓ 命令已检查 2026年11月13日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称McpStamp Zip Archives
    Remote MCP server URL · 地址https://mcp.zovo.one/mcp/zip

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  3. 在聊天中开启

    +ConnectorsMcpStamp Zip Archives

  4. 试一试

    用 McpStamp Zip Archives 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 McpStamp Zip Archives,或回答中出现 McpStamp Zip Archives 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称McpStamp Zip Archives
    Connection · 地址https://mcp.zovo.one/mcp/zip
  3. 在聊天中选择 McpStamp Zip Archives

    开启新聊天,输入前先从插件列表中选择 McpStamp Zip Archives

  4. 试一试

    用 McpStamp Zip Archives 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 McpStamp Zip Archives,或回答中出现 McpStamp Zip Archives 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user zip-archive-create-extract-bomb-guard https://mcp.zovo.one/mcp/zip
  3. 在 Claude Code 中输入 /mcp

    应能看到 McpStamp Zip Archives 在列表中并显示已连接

  4. 试一试

    用 McpStamp Zip Archives 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 McpStamp Zip Archives,或回答中出现 McpStamp Zip Archives 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 McpStamp Zip Archives 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 McpStamp Zip Archives,或回答中出现 McpStamp Zip Archives 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 McpStamp Zip Archives 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 McpStamp Zip Archives,或回答中出现 McpStamp Zip Archives 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://mcp.zovo.one/mcp/zip

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 McpStamp Zip Archives 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user zip-archive-create-extract-bomb-guard https://mcp.zovo.one/mcp/zip

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "zip-archive-create-extract-bomb-guard": {
      "url": "https://mcp.zovo.one/mcp/zip"
    }
  }
}

VS Code (mcp.json)

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

需要你填写的值

  • MCP_LICENSE_KEY 机密 env
    可选的 Pro 许可证密钥(MCPL1....)。离线验证
    查看英文原文Optional Pro license key (MCPL1....). Verified offline.

说明为自动翻译,变量名保持原样;不确定时请查看原文。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

GitHub 星标i
2 (整个仓库的星标)
该仓库包含多个 MCP 条目,星标在排名中只计算一次
每周下载量i
不在 npm/PyPI 上
连接方式
电脑或云端
传输方式
stdio, streamable-http
最新版本i
0.23.0
分类i
其他
发布到注册中心i
2026年11月2日
代码最后更新i
2026年11月18日
最近检查
2026年11月17日
作者
theluckystrike
软件包
mcpb: …/zip.mcpb
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

在你的电脑上运行,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月17日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • 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

    Turn Pro on for this connection with key, an MCPL1. . 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.

  • zip_upload

    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

  • zip_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

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

  • zip_create

    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.

  • zip_list

    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.

  • zip_extract

    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.

  • zip_add

    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.

  • zip_extract_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.

  • zip_bundle_month

    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

  • zip_history

    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.

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 theluckystrike 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于昨天

  • ✓ 通过

    有许可证

    使用 MIT

  • ✓ 通过

    端点有响应

    在 963 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 12 个工具描述,未发现针对 AI 的隐藏指令

已公开的漏洞(OSV.dev)

未检查:只能检查标明版本的 npm 和 PyPI 包

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/theluckystrike-zip-archive-create-extract-bomb-guard.svg)](https://mcp.popnx.com/en/servers/theluckystrike-zip-archive-create-extract-bomb-guard)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 20693 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 20693 个服务器的 72% 更新
  • 基础检查结果等于或优于此分类中其他 20693 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

McpStamp Zip Archives 安全吗?

它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

两种方式都可以:安装在你的电脑上,或者连接云端版本。

它还在维护吗?

GitHub 仓库最后更新于昨天,最新版本(0.23.0)于17天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

作者:koala73广泛使用★ 9.1万3天前更新

在云端运行✓ 服务方 · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

作者:openstatusHQ广泛使用★ 92742个月前更新

在云端运行✓ 服务方 · openstatus.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

作者:Klavis-AI正在增长★ 582514个月前更新

在云端运行仓库已归档✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

作者:jitsucom广泛使用★ 51364个月前更新

在云端运行✓ 服务方 · jitsu.com
与相似项目对比
本项
McpStamp Zip Archives
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
运行位置云端或安装在电脑上都可以在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否否否否
基础检查5/54/44/44/41/44/4
许可证MITAGPL-3.0AGPL-3.0MITApache-2.0MIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

mcp-zip

Make a zip, look inside one, and unpack one, in the conversation you are already in. Pack a folder with a glob (**/*.csv, everything except node_modules). Read the one README out of an archive without unpacking it. Ask what is inside a zip somebody sent you and be told before you open it: absolute paths, .., symlinks, duplicate names, and the entry that claims to be 200 MB inside a 199 KB file. Bundle a month of invoices, quotes and exports into one file to send to an accountant. Everything runs on your machine: no upload, no account, no API key, and no network call of any kind.

In the [official MCP Registry](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.theluckystrike%2Fzip-archive-create-extract-bomb-guard/versions/latest) (io.github.theluckystrike/zip-archive-create-extract-bomb-guard).

npm publish for @theluckystrike/mcp-zip is pending, so npx -y @theluckystrike/mcp-zip returns 404 today. Until then, the .mcpb one-click bundle or a clone+build is the working path.

Install

Claude Desktop, ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{

"mcpServers": { "zip": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-zip"] } } }

Claude Code:

claude mcp add zip -- npx -y @theluckystrike/mcp-zip

Cursor, .cursor/mcp.json:

{

"mcpServers": { "zip": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-zip"] } } }

Tools

toolwhat it does
zip_createPack files, or a directory tree with glob patterns, into a new .zip
zip_listEvery entry with its size, compressed size and ratio, and everything dangerous in it, flagged
zip_extractUnpack into a directory, with traversal, symlink and zip-bomb guards and a dry_run
zip_addAdd files to an archive that already exists
zip_extract_textRead one text entry inline, without unpacking anything
zip_bundle_monthOne month of invoices, quotes and exports from the sibling servers, in one file
zip_historyWhat you have created, and how much of this month's free allowance is left
license_status, license_activateFree or Pro, and activating a key

Free vs Pro

FreePro
Archives per calendar month20Unlimited
Archive sizeUp to 25 MBUnlimited
Entries per archiveUp to 200Unlimited
Reading: zip_list, zip_extract, zip_extract_textUnlimitedUnlimited
Bomb, traversal and symlink guardsYesYes

Reading is never metered. The free tier is a limit on what you *write*, because an archive somebody sent you is exactly the one you most need to inspect before opening, and a paywall in front of that would be a paywall in front of the safety check.

Get Pro: https://mcp.zovo.one/buy/zip - $19 one time, or $39 for every server in the suite, lifetime. Keys verify offline; nothing is sent anywhere.

Why fflate and not a hand-written writer

The choice was fflate (pure JS, 0 dependencies, synchronous zipSync/inflateSync) against writing a STORE/DEFLATE writer on node:zlib, which is available with no dependency at all.

The container format is written here either way. This server reads the central directory itself, in src/zipfile.ts, roughly 200 lines: sizes, names, methods, CRCs, external attributes. It has to, because every guard in the server is a decision made from those headers *before* anything is inflated, and a library that hands back {name: bytes} has already decompressed the bomb by the time you can look at it. So the argument for a library was never "it saves me the format".

What is left is the compressor, and that is the part not to write. node:zlib would do it, but its raw-deflate calls are async-first, they carry a thread-pool round trip per call, and the sync ones each build a native stream; packing 200 small files is 200 of those. fflate's deflateSync is a pure-JS implementation with no native handle, it packs 200 files in 74 ms (measured below), and it means the package still has no native build step, which is the rule for this whole suite: npx has to work everywhere.

The trade is stated plainly: fflate builds the archive in one buffer, so this server refuses inputs over 512 MB rather than pretending to stream, and it does not read ZIP64 (over 4 GB or over 65,535 entries), which is refused by name rather than misread.

Measured: the file type does not predict the compression ratio, repetition does

Every file below was zipped at level 6 on this machine. The "type" column is what a person would call the file; the ratio is what actually happened.

filetypebyteszippedratio
a 12-page invoice from mcp-pdfPDF15,12514,1181.07x
a 400-paragraph contract from mcp-docxDOCX9,8977,3111.35x
4,000 rows of billing CSV, varied valuesCSV321,329134,0492.40x
this server's own index.tssource39,49811,9383.31x
package-lock.jsonJSON138,83533,2234.18x
20,000 lines of an app loglog1,603,390106,26115.09x
4,000 rows of billing CSV, 40 repeated clientsCSV338,5494,09482.69x
50 MB of zero bytesbomb52,428,80051,2941022x

PDF and DOCX barely move, and that is not a surprise once you look inside them: both are already deflate containers, so zipping them again is packaging, not compression. Bundling a month of invoices is worth doing for the one file, not for the space.

The two CSV rows are the interesting pair. Same tool, same shape, same size, 34x apart: the one with forty repeated client names compresses 82.69x, the one with unique values 2.40x. Nothing about "it is a CSV" predicts which one you have.

Measured: why the bomb ceiling is 100x and not 50x

A compression bomb is refused by ratio, and the obvious instinct is to set that ceiling low, well under the 1022x a zeros file reaches. The table above says why that is wrong: a real CSV export, of the kind zip_bundle_month collects from the expense tracker, reached 82.69x, which is 83% of the way to a 100x ceiling and well past a 50x one. A ceiling tuned to be comfortably below a bomb would refuse a real monthly export, and the person on the other end would learn to pass max_ratio on everything, which turns the guard off permanently.

So the ratio is the *second* guard, not the first. The first is the total: the selected entries' declared uncompressed sizes are added up and compared against a ceiling (1 GB by default, max_total_mb to change it), because 200 MB out of a 199 KB file is a decision you can make about the archive as a whole without judging any entry. Both are read from the central directory, so refusing a bomb costs no decompression at all:

refuse a 500 MB bomb (497.8 KB on disk)   3 ms, nothing inflated, out_dir not even created

Measured: a bounded output buffer is not a bomb guard

fflate.inflateSync(data, { out: new Uint8Array(n) }) looks like the whole answer: cap the buffer, cap the damage. It is not, and the way it fails is quiet. A 100,000-byte entry inflated into a 10-byte buffer returns 10 bytes and throws nothing. An archive whose header declares 10 bytes for a 100 KB entry would extract as a 10-byte file, reported as a success, with the truncation invisible.

So the buffer bounds the memory and the CRC-32 in the central directory proves the bytes. Every entry this server writes out is checksummed against the header before it reaches the disk, and a mismatch refuses the entry by name. That is the check that turns a lying header from silent data loss into a sentence.

Timings

M-series laptop, over stdio, per call, cold store:

operationmeasured
zip_create, 200 files, 4.0 MB74 ms
zip_list, 200 entries2 ms
zip_extract, 200 entries47 ms
zip_extract_text, one entry1 ms
refuse a 500 MB bomb3 ms
whole test suite, 38 tests, five files3.9 s

Privacy

Everything stays on your machine. There is no network code in this server at all: no fetch, no HTTP client, no telemetry. Archives are written where you say, and a small register of what was created lives under ~/.local/share/mcp-servers/zip/ (or $XDG_DATA_HOME). License keys verify offline with a public key.

Zip passwords are not supported, and passing one is refused rather than ignored: the classic zip cipher is broken and AES zip encryption is a vendor extension no two tools agree on, so a "password protected" archive from here would be a false promise.

Built by theluckystrike. Support: support@zovo.one

Use these docs as an MCP server

Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install:

  • Docs MCP URL: https://gitmcp.io/theluckystrike/mcp-zip