Ext Ops Panel
Open dashboard
Comparison

host0 vs io.github.Abktya/universal-host-manager-mcp

host0 is an MCP server published by host0.ai. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.Abktya/universal-host-manager-mcp is an MCP server published by Abktya. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-09. 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
Marketplacehost0io.github.Abktya/universal-host-manager-mcp
Official MCP Registry Listed
Version: 0.1.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.15
Downloads/month (PyPI): 2 194
Downloads/week (PyPI): 41
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 0.1.15
Downloads/month (PyPI): 2 194
Downloads/week (PyPI): 41
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

host0 vs io.github.Abktya/universal-host-manager-mcp
Facthost0io.github.Abktya/universal-host-manager-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub)00
Last release (differs)2026-11-06Not published
Where it runs (differs)Remote server (mcp.host0.ai/mcp)On your machine (universal-host-manager-mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published8, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/host0-ai/skillsgithub.com/abktya/universal-host-manager-mcp
Changes in the last 7 days (differs)30
First seen (differs)2026-11-052026-10-11
Endpoint at the last check (differs)Status out of date: last check 2 days ago returned HTTP 401no 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

host0

In its own words, on Official MCP Registry:

Manage apps your agent published to host0: sharing, versions, analytics and shared data.

io.github.Abktya/universal-host-manager-mcp

In its own words, on Official MCP Registry:

Cross-platform FastMCP server for authenticated remote Linux/macOS host administration

How to run each

host0 As a remote MCP server

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

io.github.Abktya/universal-host-manager-mcp

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

Requires: AUTH0_AUDIENCE, AUTH0_CLIENT_ID, AUTH0_CLIENT_SECRET (secret), AUTH0_DOMAIN, MCP_WORKSPACE_DIR

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

Only host0 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 host0 publish no settings it asks for, so we do not compare settings.

What it can do: host0 · What it can do: io.github.Abktya/universal-host-manager-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). 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