EverArt (Archived) vs io.github.smeet666/mcp-rule34
EverArt (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.smeet666/mcp-rule34 is an MCP server published by smeet666. 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
| Marketplace |  EverArt (Archived) |   io.github.smeet666/mcp-rule34 |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:98c2aa1b6231 Forks (GitHub): 11 793 Pulls (Docker Hub): 18 819 Stars (Docker Hub): 3 Stars (GitHub): 91 324 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.0.2 Downloads/month (npm): 240 Downloads/week (npm): 35 Forks (GitHub): 0 Stars (GitHub): 0 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) | io.github.smeet666/mcp-rule34 |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 91 324 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 18 819 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 793 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/everart) | On your machine (mcp-rule34) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 4, secrets among them: 1 |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/modelcontextprotocol/servers | github.com/smeet666/mcp-rule34 |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
EverArt (Archived)
Image generation server using EverArt's API.
io.github.smeet666/mcp-rule34
Search rule34.xxx posts by tag through the site's own API. Needs a rule34.xxx API key.
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)
io.github.smeet666/mcp-rule34 As a local MCP server: npm package
claude mcp add --env "RULE34_API_KEY=<YOUR_RULE34_API_KEY>" --env "RULE34_USER_ID=<YOUR_RULE34_USER_ID>" --transport stdio mcp-rule34 -- npx -y mcp-rule34Requires: RULE34_API_KEY (secret), RULE34_USER_ID
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.smeet666/mcp-rule34 publish no list of tools, so we do not compare tools.
Settings each asks for
Only EverArt (Archived) asks for
EVERART_API_KEY (secret)
Only io.github.smeet666/mcp-rule34 asks for
RULE34_API_KEY (secret)RULE34_LOG_LEVELRULE34_MIN_INTERVAL_MSRULE34_USER_ID
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: EverArt (Archived) · What it can do: io.github.smeet666/mcp-rule34 · 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.