zipnative-mcp
Related Servers
Alternatives to zipnative-mcp
- AlicenseAqualityBmaintenanceEnterprise-grade PDF engine for AI agents. Pure TypeScript, zero-dependency, sandboxed, and local-first. Exposes 28 tools to generate ISO-compliant PDF/A documents, inspect layouts, extract text, handle digital signatures (PKCS#7), and render high-performance tables (10,000+ rows/s).28391 npm2MIT
Related Servers
- AlicenseBqualityFmaintenanceProvides tools for AI assistants to compress, decompress, and manage ZIP archives including metadata retrieval. It supports directory compression, password protection, and configurable extraction options.410 npmISC
- AlicenseNot gradedqualityCmaintenanceEnables secure extraction, creation, and inspection of ZIP archives and media files, with anti Zip-Slip protections, Windows long-path support, and dependency-free binary image dimension inspection.MIT
- AlicenseNot gradedqualityDmaintenanceA powerful ZIP file processing tool that enables creating, extracting, listing, adding, deleting, viewing, and verifying ZIP files through MCP protocol integration with AI development environments.53 npmMIT
- AlicenseNot gradedqualityBmaintenance29 local file tools for AI assistants: compress, merge and split PDFs, convert and resize images, zip files, shrink and convert video. Runs on your machine, reads only folders you allow, and costs about 700 tokens up front. MIT, no account.4 npm1AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to perform everyday developer chores as MCP tools — organizing and batch-renaming files, searching contents, hashing, converting timestamps, encoding/decoding, converting CSV and JSON, OCR, clipboard and screenshot access, zipping, running allowlisted commands, and managing processes. Destructive actions default to dry-run previews, and commands, renames, and process kills are constrained by allowlists and PID-plus-name matching so agents stay safe.4MIT
- AlicenseNot gradedqualityDmaintenanceProvides deterministic, verifiable text/code/measurement utilities for AI agents, enabling tasks like unit conversion, citation formatting, diffing, proofreading, readability scoring, and syntax checking with re-executable proof.MIT
TDQS
Scored across 15 tools
Most tools target clearly distinct operations (create/modify/canonicalize/merge/extract/inflate/CRC), and descriptions explicitly cross-reference when to prefer one over another. The one soft spot is the read-only inspection cluster — inspect_zip, list_zip_entries, verify_zip and scan_zip_forward all report on an archive, and inspect_zip already performs eager structural validation that overlaps conceptually with verify_zip, so selection requires careful reading rather than being instantly obvious.
Every name is snake_case with a leading verb and an object noun: inspect_zip, list_zip_entries, read_zip_entry, verify_zip, extract_zip, create_zip, modify_zip, canonicalize_zip, merge_zip, compute_crc32, sanitize_entry_paths, describe_engine, draft_governance_issue. The pattern is predictable and the verb choice telegraphs the action.
15 tools sits at the top of the well-scoped band and each one covers a genuinely different lifecycle stage (inspect, list, read, verify, extract, create, modify, canonicalize, merge, plus utilities). Nothing looks redundant or padded; even the odd-seeming draft_governance_issue is a deliberate, documented HITL workflow.
Coverage is unusually thorough: full read/write lifecycle, compaction, determinism rewriting, merging, path sanitization, CRC utilities and engine introspection, with removal reachable via modify_zip. The notable gap is encryption — encrypted entries are explicitly refused rather than decrypted — and there is no tool to list or delete files already written to the sandbox output directory.