Ext Ops Panel
Open dashboard
Comparison

Moxie Docs vs io.github.puglieseweb/systemdox

Moxie Docs is an MCP server published by Jackalope-Dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.puglieseweb/systemdox is an MCP server published by puglieseweb. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
MarketplaceMoxie Docsio.github.puglieseweb/systemdox
Official MCP Registry Listed
Version: 0.3.0
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 0.1.38
Downloads/month (npm): 1 124
Downloads/week (npm): 289
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

Moxie Docs vs io.github.puglieseweb/systemdox
FactMoxie Docsio.github.puglieseweb/systemdox
Marketplaces that list it11
Stars (GitHub) (differs)2No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (moxiedocs.com/api/mcp)On your machine (@systemdox/mcp-server)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/jackalope-dev/moxie-docs-mcpgithub.com/puglieseweb/product-systemdox
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-21no 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

Moxie Docs

In its own words, on Official MCP Registry:

Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.

io.github.puglieseweb/systemdox

In its own words, on Official MCP Registry:

Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.

How to run each

Moxie Docs As a remote MCP server

Claude Code
claude mcp add --transport http moxie-docs https://moxiedocs.com/api/mcp

io.github.puglieseweb/systemdox As a local MCP server: npm package

Claude Code
claude mcp add --env "SYSTEMDOX_API_KEY=<YOUR_SYSTEMDOX_API_KEY>" --transport stdio systemdox -- npx -y @systemdox/mcp-server

Requires: SYSTEMDOX_API_KEY (secret)

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

Only Moxie Docs 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

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

What it can do: Moxie Docs · What it can do: io.github.puglieseweb/systemdox · 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