Ext Ops Panel
Open dashboard
Comparison

Package Pricing Lab vs cloud-tools

Package Pricing Lab is an MCP server published by modernmustardseed.com. Marketplaces we read that list it: 1 (Official MCP Registry). cloud-tools is an MCP server published by munhq. Marketplaces we read that list it: 1 (Official MCP Registry). 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
MarketplacePackage Pricing Labcloud-tools
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.2.0
Downloads/month (npm): 154
Downloads/week (npm): 24
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

Package Pricing Lab vs cloud-tools
FactPackage Pricing Labcloud-tools
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.modernmustardseed.com/pricing-lab)On your machine (@munhq/cloud-tools)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/munhq/cloud-tools
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)Responded 6 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

Package Pricing Lab

In its own words, on Official MCP Registry:

Builds fixed-price service packages from costs and capacity, with margin and capacity math.

cloud-tools

In its own words, on Official MCP Registry:

Multi-cloud cost, inventory and waste analysis over MCP: AWS, GCP, Cloudflare and OVH.

How to run each

Package Pricing Lab As a remote MCP server

Claude Code
claude mcp add --transport http pricing-lab https://mcp.modernmustardseed.com/pricing-lab

cloud-tools As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio cloud-tools -- npx -y @munhq/cloud-tools

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

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

What it can do: Package Pricing Lab · What it can do: cloud-tools · 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