Ext Ops Panel
Open dashboard
Comparison

EverArt (Archived) vs Execute depth-map-estimator-mcp

EverArt (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Execute depth-map-estimator-mcp is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
MarketplaceEverArt (Archived)Execute depth-map-estimator-mcp
Docker MCP Catalog Listed
Version: sha256:98c2aa1b6231
Forks (GitHub): 11 793
Pulls (Docker Hub): 18 833
Stars (Docker Hub): 3
Stars (GitHub): 91 324
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.0.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

EverArt (Archived) vs Execute depth-map-estimator-mcp
FactEverArt (Archived)Execute depth-map-estimator-mcp
Marketplaces that list it11
Stars (GitHub) (differs)91 324No figure on GitHub
Pulls (Docker Hub) (differs)18 833No figure on Docker Hub
Forks (GitHub) (differs)11 793No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/everart)Remote server (api.m2mcent.com/depth-map-estimator-mcp/sse)
Transport (differs)stdioSSE
Tools it declares (differs)1Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 402 (less than an hour 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

EverArt (Archived)

In its own words, on Docker MCP Catalog:

Image generation server using EverArt's API.

Execute depth-map-estimator-mcp

In its own words, on Official MCP Registry:

Premium agentic endpoint for depth-map-estimator-mcp.

How to run each

EverArt (Archived) As a local MCP server: Docker image

Claude Code
claude mcp add --env "EVERART_API_KEY=<YOUR_EVERART_API_KEY>" --transport stdio everart -- docker run -i --rm -e EVERART_API_KEY mcp/everart

Requires: EVERART_API_KEY (secret)

Execute depth-map-estimator-mcp As a remote MCP server

Claude Code
claude mcp add --transport sse depth-map-estimator-mcp https://api.m2mcent.com/depth-map-estimator-mcp/sse --header "Payment-Signature: <YOUR_PAYMENT_SIGNATURE>"

Requires: Payment-Signature header

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

Only Execute depth-map-estimator-mcp has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Execute depth-map-estimator-mcp publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Execute depth-map-estimator-mcp publish no settings it asks for, so we do not compare settings.

What it can do: EverArt (Archived) · What it can do: Execute depth-map-estimator-mcp · 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