Tigris Data vs io.github.pixelvault-dev/pixelvault
Tigris Data is an MCP server published by tigrisdata. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.pixelvault-dev/pixelvault is an MCP server published by pixelvault-dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
| Marketplace |  Tigris Data | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:8d17f6d61ec9 Forks (GitHub): 2 Pulls (Docker Hub): 34 114 Stars (Docker Hub): 0 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.0 No figure published 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
| Fact | Tigris Data | io.github.pixelvault-dev/pixelvault |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 4 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 34 114 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 2 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/tigris) | Remote server (mcp.pixelvault.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 10 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/tigrisdata/tigris-mcp-server | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
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.pixelvault-dev/pixelvault
Agent-first image hosting — upload images and get instant CDN URLs.
How to run each
Tigris Data As a local MCP server: Docker image
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/tigrisRequires: AWS_SECRET_ACCESS_KEY (secret)
io.github.pixelvault-dev/pixelvault As a remote MCP server
claude mcp add --transport http pixelvault https://mcp.pixelvault.dev/mcp --header "Authorization: Bearer <YOUR_PIXELVAULT_API_KEY>"Requires: Authorization header
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.pixelvault-dev/pixelvault publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of io.github.pixelvault-dev/pixelvault publish no settings it asks for, so we do not compare settings.
What it can do: Tigris Data · What it can do: io.github.pixelvault-dev/pixelvault · 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.