Ext Ops Panel
Open dashboard
Comparison

io.github.AzielEliab/trades-runtime vs io.github.xmpuspus/cloudwright

io.github.AzielEliab/trades-runtime is an MCP server published by AzielEliab. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.xmpuspus/cloudwright is an MCP server published by xmpuspus. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-24. 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.AzielEliab/trades-runtimeio.github.xmpuspus/cloudwright
Official MCP Registry Listed
Version: 1.0.0-local
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.10.0
Downloads/month (PyPI): 274
Downloads/week (PyPI): 123
Forks (GitHub): 2
Stars (GitHub): 33
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 1.10.0
Downloads/month (PyPI): 274
Downloads/week (PyPI): 123
Forks (GitHub): 2
Stars (GitHub): 33
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.AzielEliab/trades-runtime vs io.github.xmpuspus/cloudwright
Factio.github.AzielEliab/trades-runtimeio.github.xmpuspus/cloudwright
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)1 (worse)33 (better)
Forks (GitHub) (differs)0 (worse)2 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (trades-runtime.vibelock.workers.dev/mcp)On your machine (cloudwright-ai-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedMIT
Repository (differs)github.com/azieleliab/trades-runtimegithub.com/xmpuspus/cloudwright
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)Responded 4 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

io.github.AzielEliab/trades-runtime

In its own words, on Official MCP Registry:

Local shadow MCP for HVAC, plumbing, electrical, and sewer. Read-only. Not a hosted OS.

io.github.xmpuspus/cloudwright

In its own words, on Official MCP Registry:

Cloud architecture and migration planning with costs, controls, evidence, and deployable IaC.

How to run each

io.github.AzielEliab/trades-runtime As a remote MCP server

Claude Code
claude mcp add --transport http trades-runtime https://trades-runtime.vibelock.workers.dev/mcp

io.github.xmpuspus/cloudwright As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio cloudwright -- uvx cloudwright-ai-mcp

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

Only io.github.AzielEliab/trades-runtime 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

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

What it can do: io.github.AzielEliab/trades-runtime · What it can do: io.github.xmpuspus/cloudwright · 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