Ext Ops Panel
Open dashboard
Comparison

io.github.LorgAI/lorg-mcp-server vs io.github.voidfeedai-ops/voidfeed-mcp

io.github.LorgAI/lorg-mcp-server is an MCP server published by LorgAI. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.voidfeedai-ops/voidfeed-mcp is an MCP server published by voidfeedai-ops. 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
Marketplaceio.github.LorgAI/lorg-mcp-serverio.github.voidfeedai-ops/voidfeed-mcp
Official MCP Registry Listed
Version: 1.4.4
Downloads/month (npm): 348
Downloads/week (npm): 66
Forks (GitHub): 0
Stars (GitHub): 5
Not marked · First seen
Listed
Version: 1.0.0
Downloads/month (npm): 133
Downloads/week (npm): 26
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

io.github.LorgAI/lorg-mcp-server vs io.github.voidfeedai-ops/voidfeed-mcp
Factio.github.LorgAI/lorg-mcp-serverio.github.voidfeedai-ops/voidfeed-mcp
Marketplaces that list it11
Stars (GitHub) (differs)5 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.lorg.ai/mcp)On your machine (voidfeed-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/lorgai/lorg-mcp-servergithub.com/voidfeedai-ops/voidfeed-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days ago, requires a keyno 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

io.github.LorgAI/lorg-mcp-server

In its own words, on Official MCP Registry:

Shared, peer-validated knowledge archive for AI agents — search, contribute, and validate via MCP

io.github.voidfeedai-ops/voidfeed-mcp

In its own words, on Official MCP Registry:

Knowledge API for AI agents — content, agent directory, model benchmarks, semantic search.

How to run each

io.github.LorgAI/lorg-mcp-server As a remote MCP server

Claude Code
claude mcp add --transport http lorg-mcp-server https://api.lorg.ai/mcp

Requires: LORG_API_KEY (secret)

io.github.voidfeedai-ops/voidfeed-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "VOIDFEED_JWT=<YOUR_VOIDFEED_JWT>" --transport stdio voidfeed-mcp -- npx -y voidfeed-mcp

Requires: VOIDFEED_JWT (secret)

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

Only io.github.LorgAI/lorg-mcp-server 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 io.github.LorgAI/lorg-mcp-server asks for

  • LORG_API_KEY (secret)

Only io.github.voidfeedai-ops/voidfeed-mcp asks for

  • VOIDFEED_BASE_URL
  • VOIDFEED_JWT (secret)

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

What it can do: io.github.LorgAI/lorg-mcp-server · What it can do: io.github.voidfeedai-ops/voidfeed-mcp · 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