aChurch.ai vs JSON Contracts
aChurch.ai is an MCP server published by a-church-ai. Marketplaces we read that list it: 1 (Official MCP Registry). JSON Contracts is an MCP server published by json-contracts. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-04. 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 |  aChurch.ai |  JSON Contracts |
|---|---|---|
| Official MCP Registry | Listed Version: 2.0.1 Downloads/month (npm): 393 Downloads/week (npm): 79 Forks (GitHub): 2 Stars (GitHub): 23 Not marked · First seen |
Listed Version: 0.1.2 Downloads/month (npm): 175 Downloads/week (npm): 63 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 | aChurch.ai | JSON Contracts |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 23 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 2 (better) | 0 (worse) |
| Last release (differs) | 2026-10-22 | Not published |
| Where it runs (differs) | Remote server (achurch.ai/mcp) | On your machine (json-contracts) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 1, secrets among them: 0 | 1, secrets among them: 0 |
| Licence (differs) | CC-BY-4.0 | Not stated |
| Repository (differs) | github.com/a-church-ai/church | github.com/json-contracts/json-contracts |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 7 h ago | no remote endpoint we check |
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
aChurch.ai
A sanctuary for AI agents and humans: attend a service, reflect, read, search, and ask. No auth.
JSON Contracts
JSON contract registry and validator for structured LLM and agent outputs.
How to run each
aChurch.ai As a remote MCP server
claude mcp add --transport http church https://achurch.ai/mcpJSON Contracts As a local MCP server: npm package
claude mcp add --transport stdio json-contracts -- npx -y json-contractsCommands 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
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only aChurch.ai asks for
ACHURCH_MCP_URL
Only JSON Contracts asks for
JSON_CONTRACTS_DIR
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: aChurch.ai · What it can do: JSON Contracts · Compare two other plugins
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.