Ext Ops Panel
Open dashboard
Comparison

Rust Filesystem vs zipnative MCP — ZIP creation, inspection, secure extraction & verification

Rust Filesystem is an MCP server published by rust-mcp-stack. Marketplaces we read that list it: 1 (Docker MCP Catalog). zipnative MCP — ZIP creation, inspection, secure extraction & verification is an MCP server published by Nizoka. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceRust Filesystemzipnative MCP — ZIP creation, inspection, secure extraction & verification
Docker MCP Catalog Listed
Version: sha256:0a8d6879a676
Forks (GitHub): 28
Pulls (Docker Hub): 42 633
Stars (Docker Hub): 2
Stars (GitHub): 180
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Downloads/month (npm): 253
Downloads/week (npm): 56
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Rust Filesystem vs zipnative MCP — ZIP creation, inspection, secure extraction & verification
FactRust Filesystemzipnative MCP — ZIP creation, inspection, secure extraction & verification
Marketplaces that list it11
Stars (GitHub) (differs)180 (better)0 (worse)
Pulls (Docker Hub) (differs)42 633No figure on Docker Hub
Forks (GitHub) (differs)28 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/rust-mcp-filesystem)On your machine (zipnative-mcp)
Transportstdiostdio
Tools it declares (differs)24Not published
Environment variables it asks for (differs)2, secrets among them: 07, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/rust-mcp-stack/rust-mcp-filesystemgithub.com/nizoka/zipnative-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Rust Filesystem

In its own words, on Docker MCP Catalog:

The Rust MCP Filesystem is a high-performance, asynchronous, and lightweight Model Context Protocol (MCP) server built in Rust for secure and efficient filesystem operations. Designed with security in mind, it operates in read-only mode by default and restricts clients from updating allowed directories via MCP Roots unless explicitly enabled, ensuring robust protection against unauthorized access. Leveraging asynchronous I/O, it delivers blazingly fast performance with a minimal resource footprint. Optimized for token efficiency, the Rust MCP Filesystem enables large language models (LLMs) to precisely target searches and edits within specific sections of large files and restrict operations by file size range, making it ideal for efficient file exploration, automation, and system integration.

zipnative MCP — ZIP creation, inspection, secure extraction & verification

In its own words, on Official MCP Registry:

ZIP MCP server: create, inspect, verify, extract securely, modify without recompression. 13 tools

How to run each

Rust Filesystem As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio rust-mcp-filesystem -- docker run -i --rm mcp/rust-mcp-filesystem

zipnative MCP — ZIP creation, inspection, secure extraction & verification As a local MCP server: npm package

Claude Code
claude mcp add --env "ZIPNATIVE_MCP_HTTP_TOKEN=<YOUR_ZIPNATIVE_MCP_HTTP_TOKEN>" --transport stdio zipnative-mcp -- npx -y zipnative-mcp zipnative-mcp

Requires: ZIPNATIVE_MCP_HTTP_TOKEN (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of zipnative MCP — ZIP creation, inspection, secure extraction & verification publish no list of tools, so we do not compare tools.

Settings each asks for

Only Rust Filesystem asks for

  • ALLOW_WRITE
  • ENABLE_ROOTS

Only zipnative MCP — ZIP creation, inspection, secure extraction & verification asks for

  • ZIPNATIVE_MCP_CACHE_DIR
  • ZIPNATIVE_MCP_HTTP_TOKEN (secret)
  • ZIPNATIVE_MCP_MAX_ENTRIES
  • ZIPNATIVE_MCP_MAX_UNCOMPRESSED_BYTES
  • ZIPNATIVE_MCP_OUTPUT_DIR
  • ZIPNATIVE_MCP_PORT
  • ZIPNATIVE_MCP_WORKERS

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Rust Filesystem · What it can do: zipnative MCP — ZIP creation, inspection, secure extraction & verification · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built