io.github.AzielEliab/trades-runtime vs EmbeddedCI BenchPod
io.github.AzielEliab/trades-runtime is an MCP server published by AzielEliab. Marketplaces we read that list it: 1 (Official MCP Registry). EmbeddedCI BenchPod is an MCP server published by embeddedci-com. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-23. 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
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0-local Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 2.13.3 Downloads/month (PyPI): 1 509 Downloads/week (PyPI): 683 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 2.13.3 Downloads/month (PyPI): 1 509 Downloads/week (PyPI): 683 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
| Fact | io.github.AzielEliab/trades-runtime | EmbeddedCI BenchPod |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | Remote server (trades-runtime.vibelock.workers.dev/mcp) | On your machine (embeddedci-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/azieleliab/trades-runtime | github.com/embeddedci-com/embeddedci-python |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days ago | no 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
Local shadow MCP for HVAC, plumbing, electrical, and sewer. Read-only. Not a hosted OS.
EmbeddedCI BenchPod
Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.
How to run each
io.github.AzielEliab/trades-runtime As a remote MCP server
claude mcp add --transport http trades-runtime https://trades-runtime.vibelock.workers.dev/mcp
EmbeddedCI BenchPod As a local MCP server: PyPI package
claude mcp add --env "BENCHPOD_API_KEY=<YOUR_BENCHPOD_API_KEY>" --transport stdio embeddedci-mcp -- uvx embeddedci-mcp
Requires: BENCHPOD_API_KEY (secret)
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
The marketplaces of io.github.AzielEliab/trades-runtime publish no settings it asks for, so we do not compare settings.
What it can do: io.github.AzielEliab/trades-runtime · What it can do: EmbeddedCI BenchPod · 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.