Ext Ops Panel
Open dashboard
Comparison

dev.mcphost/mcphost vs io.github.ANAMIZED/superagenticmcp

dev.mcphost/mcphost is an MCP server published by mcphost.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.ANAMIZED/superagenticmcp is an MCP server published by ANAMIZED. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
Marketplacedev.mcphost/mcphostio.github.ANAMIZED/superagenticmcp
Official MCP Registry Listed
Version: 0.112.38
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.0
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

dev.mcphost/mcphost vs io.github.ANAMIZED/superagenticmcp
Factdev.mcphost/mcphostio.github.ANAMIZED/superagenticmcp
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub)00
Last release (differs)2026-10-21Not published
Where it runs (differs)Remote server (mcphost.dev/mcp)Not stated
Transport (differs)Streamable HTTPNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/j0yen/mcphostgithub.com/anamized/superagenticmcp
Changes in the last 7 days (differs)20 or more0
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 5 days 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

dev.mcphost/mcphost

In its own words, on Official MCP Registry:

Hosted MCP runtime where your agent publishes its own tools by tool call and keeps working.

io.github.ANAMIZED/superagenticmcp

In its own words, on Official MCP Registry:

MCP-native router and multi-agent control plane: plan, route tool calls, stream execution.

How to run each

dev.mcphost/mcphost As a remote MCP server

Claude Code
claude mcp add --transport http mcphost https://mcphost.dev/mcp

io.github.ANAMIZED/superagenticmcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Only dev.mcphost/mcphost has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of io.github.ANAMIZED/superagenticmcp nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: dev.mcphost/mcphost · What it can do: io.github.ANAMIZED/superagenticmcp · 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