Ext Ops Panel
Open dashboard
Comparison

Free the Tools vs io.github.theluckystrike/archive

Free the Tools is an MCP server published by sapience-design. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.theluckystrike/archive is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
MarketplaceFree the Toolsio.github.theluckystrike/archive
Official MCP Registry Listed
Version: 0.1.2
Downloads/month (npm): 808
Downloads/week (npm): 743
Forks (GitHub): 1
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.22.5
Forks (GitHub): 0
Stars (GitHub): 2
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

Free the Tools vs io.github.theluckystrike/archive
FactFree the Toolsio.github.theluckystrike/archive
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)2 (better)
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)2026-10-11 (worse)2026-10-14 (better)
Where it runs (differs)On your machine (freethetools)Remote server or your machine
Transport (differs)stdiostdio, Streamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 01, secrets among them: 1
Licence (differs)AGPL-3.0-onlyNot stated
Repository (differs)github.com/sapience-design/freethetoolsgithub.com/theluckystrike/mcp-servers
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days 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

Free the Tools

In its own words, on Official MCP Registry:

Local PDF, image, data and text tools for AI assistants. Files stay on your computer.

io.github.theluckystrike/archive

In its own words, on Official MCP Registry:

Zip and unzip archives from your AI chat: create, list, extract. Offline, with bomb guards.

How to run each

Free the Tools As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio freethetools -- npx -y freethetools mcp

io.github.theluckystrike/archive As a remote MCP server

Claude Code
claude mcp add --transport http zip-archive-create-extract-bomb-guard https://mcp.zovo.one/mcp/zip --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: MCP_LICENSE_KEY (secret), Authorization header

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

Only io.github.theluckystrike/archive 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

Only Free the Tools asks for

  • FREETHETOOLS_LIBRARY

Only io.github.theluckystrike/archive asks for

  • MCP_LICENSE_KEY (secret)

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

What it can do: Free the Tools · What it can do: io.github.theluckystrike/archive · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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