Ext Ops Panel
Open dashboard
Comparison

Tigris Data vs io.github.ofershap/s3

Tigris Data is an MCP server published by tigrisdata. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.ofershap/s3 is an MCP server published by ofershap. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
MarketplaceTigris Dataio.github.ofershap/s3
Docker MCP Catalog Listed
Version: sha256:8d17f6d61ec9
Forks (GitHub): 2
Pulls (Docker Hub): 34 117
Stars (Docker Hub): 0
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Downloads/month (npm): 335
Downloads/week (npm): 65
Forks (GitHub): 1
Stars (GitHub): 4
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

Tigris Data vs io.github.ofershap/s3
FactTigris Dataio.github.ofershap/s3
Marketplaces that list it11
Stars (GitHub)44
Pulls (Docker Hub) (differs)34 117No figure on Docker Hub
Forks (GitHub) (differs)2 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/tigris)On your machine (mcp-server-s3)
Transportstdiostdio
Tools it declares (differs)10Not published
Environment variables it asks for (differs)3, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/tigrisdata/tigris-mcp-servergithub.com/ofershap/mcp-server-s3
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

Tigris Data

In its own words, on Docker MCP Catalog:

Tigris is a globally distributed S3-compatible object storage service that provides low latency anywhere in the world, enabling developers to store and access any amount of data for a wide range of use cases.

io.github.ofershap/s3

In its own words, on Official MCP Registry:

AWS S3 MCP — list buckets, browse objects, upload/download, presigned URLs.

How to run each

Tigris Data As a local MCP server: Docker image

Claude Code
claude mcp add --env "AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>" --transport stdio tigris -- docker run -i --rm -e AWS_SECRET_ACCESS_KEY mcp/tigris

Requires: AWS_SECRET_ACCESS_KEY (secret)

io.github.ofershap/s3 As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio s3 -- npx -y mcp-server-s3

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

Tools each declares

The marketplaces of io.github.ofershap/s3 publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of io.github.ofershap/s3 publish no settings it asks for, so we do not compare settings.

What it can do: Tigris Data · What it can do: io.github.ofershap/s3 · 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