Ext Ops Panel
Open dashboard
Comparison

Filesystem (Reference) vs io.github.theluckystrike/pdf-split-merge-compress

Filesystem (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.theluckystrike/pdf-split-merge-compress 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-17. 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
MarketplaceFilesystem (Reference)io.github.theluckystrike/pdf-split-merge-compress
Docker MCP Catalog Listed
Version: sha256:35fcf0217ca0
Forks (GitHub): 11 793
Pulls (Docker Hub): 292 894
Stars (Docker Hub): 28
Stars (GitHub): 91 324
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.23.2
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

Filesystem (Reference) vs io.github.theluckystrike/pdf-split-merge-compress
FactFilesystem (Reference)io.github.theluckystrike/pdf-split-merge-compress
Marketplaces that list it11
Stars (GitHub) (differs)91 324 (better)2 (worse)
Pulls (Docker Hub) (differs)292 894No figure on Docker Hub
Forks (GitHub) (differs)11 793 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/filesystem)Remote server (mcp.zovo.one/mcp/pdf-split-merge-compress)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)11Not published
Environment variables it asks forNot publishedNot published
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/theluckystrike/mcp-servers
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 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

Filesystem (Reference)

In its own words, on Docker MCP Catalog:

Local filesystem access with configurable allowed paths.

io.github.theluckystrike/pdf-split-merge-compress

In its own words, on Official MCP Registry:

Split, merge and compress PDF files locally - private by design, no uploads.

How to run each

Filesystem (Reference) As a local MCP server: Docker image

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

io.github.theluckystrike/pdf-split-merge-compress As a remote MCP server

Claude Code
claude mcp add --transport http pdf-split-merge-compress https://mcp.zovo.one/mcp/pdf-split-merge-compress --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only io.github.theluckystrike/pdf-split-merge-compress has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of io.github.theluckystrike/pdf-split-merge-compress publish no list of tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Filesystem (Reference) · What it can do: io.github.theluckystrike/pdf-split-merge-compress · 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