EverArt (Archived) vs Sapiens Sintéticos
EverArt (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Sapiens Sintéticos is an MCP server published by sapiensinteticos.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-29. 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 |  EverArt (Archived) |  Sapiens Sintéticos |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:98c2aa1b6231 Forks (GitHub): 11 874 Pulls (Docker Hub): 19 124 Stars (Docker Hub): 3 Stars (GitHub): 91 633 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.105.3 Downloads/month (npm): 9 109 Downloads/week (npm): 1 445 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.105.3 Downloads/month (npm): 9 109 Downloads/week (npm): 1 445 Forks (GitHub): 0 Stars (GitHub): 1 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 | EverArt (Archived) | Sapiens Sintéticos |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 91 633 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 19 124 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 874 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-29 |
| Where it runs (differs) | On your machine (mcp/everart) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | NOASSERTION | MIT |
| Repository (differs) | github.com/modelcontextprotocol/servers | github.com/inhabitants/sapiens-mcp |
| Changes in the last 7 days (differs) | 0 | 10 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 days ago, requires a key |
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)
Image generation server using EverArt's API.
Sapiens Sintéticos
Operate your Sapiens Sintéticos AI studio: generate image, article, voice, music and video.
How to run each
EverArt (Archived) As a local MCP server: Docker image
claude mcp add --env "EVERART_API_KEY=<YOUR_EVERART_API_KEY>" --transport stdio everart -- docker run -i --rm -e EVERART_API_KEY mcp/everartRequires: EVERART_API_KEY (secret)
Sapiens Sintéticos As a remote MCP server
claude mcp add --transport http sapiens https://www.sapiensinteticos.com/api/mcp/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Sapiens Sintéticos has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Sapiens Sintéticos publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Sapiens Sintéticos publish no settings it asks for, so we do not compare settings.
What it can do: EverArt (Archived) · What it can do: Sapiens Sintéticos · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.