Ext Ops Panel
Open dashboard
Comparison

aChurch.ai vs io.github.hashgraph-online/hashnet

aChurch.ai is an MCP server published by a-church-ai. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.hashgraph-online/hashnet is an MCP server published by hashgraph-online. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. 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
MarketplaceaChurch.aiio.github.hashgraph-online/hashnet
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: 1.0.24
Downloads/month (npm): 230
Downloads/week (npm): 70
Forks (GitHub): 4
Stars (GitHub): 13
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

aChurch.ai vs io.github.hashgraph-online/hashnet
FactaChurch.aiio.github.hashgraph-online/hashnet
Marketplaces that list it11
Stars (GitHub) (differs)23 (better)13 (worse)
Forks (GitHub) (differs)2 (worse)4 (better)
Last release (differs)2026-10-22Not published
Where it runs (differs)Remote server (achurch.ai/mcp)On your machine (@hol-org/hashnet-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 01, secrets among them: 1
Licence (differs)CC-BY-4.0Not stated
Repository (differs)github.com/a-church-ai/churchgithub.com/hashgraph-online/hashnet-mcp-js
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 19 h agono 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

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.

io.github.hashgraph-online/hashnet

In its own words, on Official MCP Registry:

Universal AI Agent Discovery - search 59,000+ agents across MCP, NANDA, A2A, OpenRouter

How to run each

aChurch.ai As a remote MCP server

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

io.github.hashgraph-online/hashnet As a local MCP server: npm package

Claude Code
claude mcp add --env "REGISTRY_BROKER_API_KEY=<YOUR_REGISTRY_BROKER_API_KEY>" --transport stdio hashnet -- npx -y @hol-org/hashnet-mcp

Requires: REGISTRY_BROKER_API_KEY (secret)

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

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 io.github.hashgraph-online/hashnet asks for

  • REGISTRY_BROKER_API_KEY (secret)

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

What it can do: aChurch.ai · What it can do: io.github.hashgraph-online/hashnet · 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.

Where the data comes from: how the catalog is built