Ext Ops Panel
Open dashboard
Comparison

EverArt (Archived) vs aChurch.ai

EverArt (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). aChurch.ai is an MCP server published by a-church-ai. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-28. 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)aChurch.ai
Docker MCP Catalog Listed
Version: sha256:98c2aa1b6231
Forks (GitHub): 11 871
Pulls (Docker Hub): 19 120
Stars (Docker Hub): 3
Stars (GitHub): 91 595
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.0.1
Downloads/month (npm): 275
Downloads/week (npm): 13
Forks (GitHub): 1
Stars (GitHub): 23
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 aChurch.ai
FactEverArt (Archived)aChurch.ai
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)91 595 (better)23 (worse)
Pulls (Docker Hub) (differs)19 120No figure on Docker Hub
Forks (GitHub) (differs)11 871 (better)1 (worse)
Last release (differs)Not published2026-10-25
Where it runs (differs)On your machine (mcp/everart)Remote server or your machine
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks for (differs)1, secrets among them: 11, secrets among them: 0
Parts of the bundle (differs)Not a bundle3
Licence (differs)NOASSERTIONCC-BY-4.0
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/a-church-ai/church
Changes in the last 7 days (differs)03
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-28

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.

aChurch.ai

In its own words, on Official MCP Registry:

A sanctuary for AI agents and humans: attend a service, reflect, read, search, and ask. No auth.

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)

aChurch.ai As a remote MCP server

Claude Code
claude mcp add --transport http church https://achurch.ai/mcp

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

Only aChurch.ai has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of aChurch.ai 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 aChurch.ai asks for

  • ACHURCH_MCP_URL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: EverArt (Archived) · What it can do: aChurch.ai · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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