Ext Ops Panel
Open dashboard
Comparison

qwen-mm-plugins-mhs vs GemsMakers Precision Scientific & Engineering Simulators

qwen-mm-plugins-mhs is a plugin bundle for AI coding tools published by QwenLM. Marketplaces we read that list it: 1 (Community GitHub marketplaces). GemsMakers Precision Scientific & Engineering Simulators is an MCP server published by gemsmakers. Marketplaces we read that list it: 1 (Official MCP Registry). 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
Marketplaceqwen-mm-plugins-mhsGemsMakers Precision Scientific & Engineering Simulators
Community marketplace qwenlm/qwen-mm-plugins Listed
Version: 1.2.0
Forks (GitHub): 224
Stars (GitHub): 3 190
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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

qwen-mm-plugins-mhs vs GemsMakers Precision Scientific & Engineering Simulators
Factqwen-mm-plugins-mhsGemsMakers Precision Scientific & Engineering Simulators
Marketplaces that list it11
Stars (GitHub) (differs)3 190 (better)0 (worse)
Forks (GitHub) (differs)224 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (gemsmakers-mcp-server)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/qwenlm/qwen-mm-pluginsgithub.com/gemsmakers/gemsmakers-mcp-server
Changes in the last 7 days22
First seen (differs)2026-11-022026-11-05

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

qwen-mm-plugins-mhs

In its own words, on Community GitHub marketplaces:

Operate physical hardware through Model Hardware Standard adapters: discover devices, read sensors and camera frames, send commands with host-side safety-limit enforcement, check health, and emergency-stop — as MCP tools. Adapters are run by the hardware's owner.

GemsMakers Precision Scientific & Engineering Simulators

In its own words, on Official MCP Registry:

MCP server for GemsMakers precision scientific, horology, and engineering calculators.

How to run each

qwen-mm-plugins-mhs As a Claude Code plugin

Claude Code
/plugin marketplace add qwenlm/qwen-mm-plugins
/plugin install qwen-mm-plugins-mhs@qwen-mm-plugins

GemsMakers Precision Scientific & Engineering Simulators As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio gemsmakers-precision-scientific-engineer -- npx -y gemsmakers-mcp-server

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

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: qwen-mm-plugins-mhs · What it can do: GemsMakers Precision Scientific & Engineering Simulators · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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