Ext Ops Panel
Open dashboard
Comparison

AIFeed vs io.github.helloaigent-dev/helloaigent-subscriber

AIFeed is an MCP server published by denyn1. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.helloaigent-dev/helloaigent-subscriber is an MCP server published by helloaigent-dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
MarketplaceAIFeedio.github.helloaigent-dev/helloaigent-subscriber
Official MCP Registry Listed
Version: 1.0.0-draft.2
Downloads/month (npm): 477
Downloads/week (npm): 38
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 0.2.1
Downloads/month (npm): 220
Downloads/week (npm): 41
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

AIFeed vs io.github.helloaigent-dev/helloaigent-subscriber
FactAIFeedio.github.helloaigent-dev/helloaigent-subscriber
Marketplaces that list it11
Stars (GitHub) (differs)2 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (aifeed-mcp-server)On your machine (@helloaigent-dev/subscriber)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/denyn1/aifeed-protocolgithub.com/helloaigent-dev/helloaigent-subscriber
Changes in the last 7 days00
First seen2026-10-112026-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

AIFeed

In its own words, on Official MCP Registry:

Verify signed AIFeed permissions, fetch token-budgeted markdown, and verify assets for AI agents.

io.github.helloaigent-dev/helloaigent-subscriber

In its own words, on Official MCP Registry:

Subscribe your agent to Hello Aigent feeds: discover, fetch signed updates, verify, and act.

How to run each

AIFeed As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio aifeed-mcp-server -- npx -y aifeed-mcp-server

io.github.helloaigent-dev/helloaigent-subscriber As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio helloaigent-subscriber -- npx -y @helloaigent-dev/subscriber

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of AIFeed publish no settings it asks for, so we do not compare settings.

What it can do: AIFeed · What it can do: io.github.helloaigent-dev/helloaigent-subscriber · Compare two other plugins

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.

Where the data comes from: how the catalog is built