Ext Ops Panel
Open dashboard
Comparison

zipnative MCP — ZIP creation, inspection, secure extraction & verification vs RAR.now MCP Server

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). RAR.now MCP Server is an MCP server published by chrisyau83. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
Marketplacezipnative MCP — ZIP creation, inspection, secure extraction & verificationRAR.now MCP Server
Official MCP Registry Listed
Version: 1.1.0
Downloads/month (npm): 216
Downloads/week (npm): 64
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0 (last published figure)
Stars (GitHub): 0 (last published figure)
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

zipnative MCP — ZIP creation, inspection, secure extraction & verification vs RAR.now MCP Server
Factzipnative MCP — ZIP creation, inspection, secure extraction & verificationRAR.now MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)00 (last published figure)
Forks (GitHub) (differs)00 (last published figure)
Last release (differs)2026-10-19Not published
Where it runs (differs)On your machine (zipnative-mcp)Remote server (rar.now/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)8, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/nizoka/zipnative-mcpgithub.com/chrisyau83/rar-now
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-27
Endpoint at the last check (differs)no remote endpoint we checkResponded 21 h ago

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

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

In its own words, on Official MCP Registry:

ZIP MCP server: create, inspect, verify, extract, canonicalize, merge, modify. 15 tools

RAR.now MCP Server

In its own words, on Official MCP Registry:

Convert RAR archives to ZIP, 7Z and TAR through MCP-compatible AI clients.

How to run each

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)

RAR.now MCP Server As a remote MCP server

Claude Code
claude mcp add --transport http rar-now https://rar.now/mcp --header "X-API-Key: <YOUR_X_API_KEY>"

Requires: X-API-Key header

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

Only RAR.now MCP Server has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of RAR.now MCP Server publish no settings it asks for, so we do not compare settings.

What it can do: zipnative MCP — ZIP creation, inspection, secure extraction & verification · What it can do: RAR.now MCP Server · Compare two other plugins

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